How to make a PDF accessible
An accessible PDF needs logical structure, correct reading order, language, alternative text and understandable form fields. A visually tidy page is not accessible by itself.
When to use it
An accessible PDF needs logical structure, correct reading order, language, alternative text and understandable form fields. A visually tidy page is not accessible by itself. The situations below show when this guide can help you choose the right workflow and avoid unnecessary processing.
- A document is published for a broad audience or must work with assistive technologies.
- The PDF contains forms, tables, columns or images that are important for understanding the content.
How it works
This guide divides the topic into three consecutive stages: inspect structure, describe elements, test. Follow them in order to understand the result and the points that require manual review.
- 01Inspect structureIdentify document language, existing tags, heading sequence and logical reading order for text, columns and tables.
- 02Describe elementsAdd alternative text to meaningful images, clear field names, instructions and a logical keyboard tab order.
- 03TestRun an accessibility check, navigate by keyboard and review critical pages with a screen reader.
What changes
Before starting, identify which parts of the document will change and which will remain intact. The list below describes changes in the output copy rather than hidden modifications to the source file.
- The document receives logical tags, a language and a testable reading order.
- Meaningful images and form fields receive text descriptions.
- Accessibility issues are recorded and corrected before publication.
What can be lost
Some operations affect more than the visible page and can change text layers, forms, links or signatures. This list helps you decide whether the separate output copy is suitable for the next stage of your work.
- Converting an accessible PDF into page images removes tags and reading order.
- Incorrect merging or flattening can lose descriptions attached to interactive fields.
Limitations
Limitations describe the current implementation boundary and the cases that require additional review. Check them before uploading, especially when a document is complex, protected or contains important structure.
- Automatic tagging does not always understand complex columns, tables and decorative elements.
- OCR adds text but does not automatically create correct heading and table structure.
- The current service does not claim automatic PDF/UA conformance.
Related tools
Related tools let you move directly from the explanation to the appropriate action. Each tool uses its own workflow and shows its specific limits before processing starts.