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.
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.
All communication between your application and Nutrient is done via HTTPS to ensure your data is encrypted when it’s sent to us.
All payments are handled by Paddle. Nutrient DWS Processor API never has direct access to any of your payment data.
Optical character recognition and layout models identify structural elements: headings, paragraphs, lists, tables, and artifacts.
Elements are mapped to the PDF structure tree with correct roles (headings, tables, and more) and logical reading order.
Embeds PDF/UA metadata and returns the tagged PDF.
H1–H6 roles, supports multi-column layouts
Ordered and unordered lists
Table, row, and cell tagging with scope attributes
Reflows content for assistive technologies
Moves comments and form widgets into the structure tree
Flags decorative items to skip by screen readers
Create an account to get your API key and start testing accessibility workflows in minutes with cloud-hosted APIs.
Most common next steps
After validating Accessibility API, continue to:
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.
