Are custom plans available?

Yes. For high-volume usage or enterprise needs, we offer custom plans with tailored quotas, dedicated support, and flexible pricing. Contact our sales team to discuss a custom plan that fits your requirements.

Which programming languages are supported?

You can call the DWS API from any language that can make HTTP requests. We provide quickstart guides for Java, C#, JavaScript, Python, and PHP to help you get started faster.

What if my language isn’t listed?

No problem. The API is language-independent. As long as your HTTP client can send standard multipart/form-data requests, you can use the API from any language.

Is communication secure?

Yes. All requests must go over HTTPS. Any account, usage, or billing data we do collect is stored in encrypted databases.

What about payment data?

We don’t touch it. Payments are processed entirely by Paddle, which handles all payment information and compliance.

What does PDF/UA accessibility auto-tagging do?

It analyzes your PDF and generates a tagged PDF with semantic structure for assistive technologies. This includes tagging common elements like headings, paragraphs, lists, tables, and reading order so screen readers can interpret the document correctly.

What files can I send, and what do I get back?

The accessibility auto-tagging workflow takes a PDF file as input and returns a tagged PDF file as output. On the overview page, you can use the interactive playground with the provided sample PDF or upload your own document.

Is auto-tagging enough to guarantee full compliance?

Auto-tagging significantly reduces manual work, but accessibility compliance still depends on document quality and content semantics. We recommend validating outputs in your QA process, especially for legally sensitive or high-stakes documents.

How does pricing work for the Accessibility API?

Pricing is quota-based and billed monthly. Each plan includes a monthly quota for auto-tagged pages and a separate monthly quota for PDF/UA validations.

Do you offer a validation-only plan?

Not currently. All plans include both auto-tagged pages and validation quotas.

What happens when I reach my quota?

If you reach your monthly quota for auto-tagged pages or validations, additional requests in that category are blocked until the next quota period starts or you move to a larger plan.

Do unused monthly quotas roll over?

No. Unused auto-tagging pages and validation quotas reset at the start of each monthly period and do not roll over.

Does the Accessibility API store my files?

No. Input files are deleted as soon as processing finishes. Output files are deleted as soon as you download them. We only retain minimal metadata required for operations and billing.

DWS Accessibility API

Make every PDF more accessible with automated PDF/UA workflows

DWS Accessibility API helps your team scale document accessibility by auto-tagging PDFs and validating conformance in the cloud. Reduce manual remediation work and deliver inclusive experiences faster.

Start for free

Security is our top priority

No document storage

No input or resulting documents are stored on our infrastructure. All files are deleted as soon as a request finishes. Alternatively, check out our self-hosted product.

HTTPS encryption

All communication between your application and Nutrient is done via HTTPS to ensure your data is encrypted when it’s sent to us.

Safe payment processing

All payments are handled by Paddle. Nutrient DWS Processor API never has direct access to any of your payment data.

How it works

Layout analysis

Optical character recognition and layout models identify structural elements: headings, paragraphs, lists, tables, and artifacts.

Semantic tagging

Elements are mapped to the PDF structure tree with correct roles (headings, tables, and more) and logical reading order.

Output

Embeds PDF/UA metadata and returns the tagged PDF.

Key capabilities

Heading detection

H1–H6 roles, supports multi-column layouts

Lists semantics

Ordered and unordered lists

Table structure

Table, row, and cell tagging with scope attributes

Reading order

Reflows content for assistive technologies

Annotation handling

Moves comments and form widgets into the structure tree

Artifact cleanup

Flags decorative items to skip by screen readers

Ready to improve PDF accessibility at scale?

Create an account and start testing accessibility workflows in minutes with cloud-hosted APIs.

Get started See pricing

Frequently asked questions

Haven't found what you're looking for? contact us.

: Yes. For high-volume usage or enterprise needs, we offer custom plans with tailored quotas, dedicated support, and flexible pricing. Contact our sales team to discuss a custom plan that fits your requirements.
: You can call the DWS API from any language that can make HTTP requests. We provide quickstart guides for Java, C#, JavaScript, Python, and PHP to help you get started faster.
: No problem. The API is language-independent. As long as your HTTP client can send standard multipart/form-data requests, you can use the API from any language.
: Yes. All requests must go over HTTPS. Any account, usage, or billing data we do collect is stored in encrypted databases.
: We don’t touch it. Payments are processed entirely by Paddle, which handles all payment information and compliance.
: It analyzes your PDF and generates a tagged PDF with semantic structure for assistive technologies. This includes tagging common elements like headings, paragraphs, lists, tables, and reading order so screen readers can interpret the document correctly.
: The accessibility auto-tagging workflow takes a PDF file as input and returns a tagged PDF file as output. On the overview page, you can use the interactive playground with the provided sample PDF or upload your own document.
: Auto-tagging significantly reduces manual work, but accessibility compliance still depends on document quality and content semantics. We recommend validating outputs in your QA process, especially for legally sensitive or high-stakes documents.
: Pricing is quota-based and billed monthly. Each plan includes a monthly quota for auto-tagged pages and a separate monthly quota for PDF/UA validations.
: Not currently. All plans include both auto-tagged pages and validation quotas.
: If you reach your monthly quota for auto-tagged pages or validations, additional requests in that category are blocked until the next quota period starts or you move to a larger plan.
: No. Unused auto-tagging pages and validation quotas reset at the start of each monthly period and do not roll over.
: No. Input files are deleted as soon as processing finishes. Output files are deleted as soon as you download them. We only retain minimal metadata required for operations and billing.