How to make a PDF accessible in 2026

The short answer

Run the PDF through a tool that does five things: tags the structure, adds alt text, fixes reading order, sets metadata, and produces a tagged PDF/UA output plus an accessible HTML version. Verify with a screen reader on one sample page before you call it done.

The six steps in detail

1. Step 1. Audit the source. Open the PDF in a checker (PAC, Acrobat's Accessibility Checker, or DocAccessible itself). You are looking for the structural gaps: missing tags, missing language, images without alt text, and tables without headers.
2. Step 2. Tag the structure. Every paragraph, heading, list, table, and figure needs a corresponding tag. DocAccessible generates these automatically by re-parsing the layout; in Acrobat, you can also use 'Autotag' and then correct the output.
3. Step 3. Add alt text to every image. Describe the image factually in one short sentence. Mark genuinely decorative images as artefact. Avoid 'image of' or 'picture of' prefixes.
4. Step 4. Fix the reading order. Verify that tags follow the visual reading order, especially on multi-column layouts. The DocAccessible editor lets you drag blocks; in Acrobat, use the Content pane.
5. Step 5. Set document metadata. Give the document a meaningful title and declare its language. Both are trivial changes that screen readers rely on heavily.
6. Step 6. Publish both formats. Export the tagged PDF for download and an accessible HTML version for the web. Hosted HTML is easier to maintain, indexes better in search, and is often what users actually want.

Tools worth knowing

• Adobe Acrobat Pro remains the industry staple for manual remediation. Good fidelity, slow on scale.
• PAC 2024 (PDF Accessibility Checker) remains the reference validator for PDF/UA-1 in 2026. Free.
• DocAccessible automates steps 2 through 6 and gives you an HTML version with the same content, so web visitors get a better experience than opening a PDF.
• PAX and the Matterhorn protocol are the formal machine-readable test suites for PDF/UA. If you need auditor-grade evidence, run them.

Verification: one minute with a screen reader

Automated scores catch structural problems. Nothing replaces five minutes with VoiceOver (macOS) or NVDA (Windows). Open the remediated page, turn the screen reader on, and navigate using the heading shortcut (H in NVDA, rotor in VoiceOver). If you can form a mental outline of the document from headings alone, you have done your job.

A note on HTML versus PDF

A tagged PDF can be accessible, but it is a heavier lift for assistive tech than a well-structured web page. Whenever possible, publish the HTML version as the primary format and link the PDF as a download for users who need it. DocAccessible produces both from a single upload.