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 accessible HTML plus a rebuilt tagged PDF/UA-aligned output. The rebuilt PDF may change the source layout. If the original appearance must remain unchanged, use manual PDF remediation instead. Verify every formal deliverable with accessibility tools and a screen reader before calling 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 artifacts. 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 the accessible formats. Publish the accessible HTML version and download the rebuilt PDF/UA-aligned tagged PDF when layout can adapt. If the source design must remain unchanged, move the document to manual remediation.

Tools worth knowing

• Adobe Acrobat Pro remains the industry staple for manual remediation. Good fidelity, slow on scale.
• PAC 2026 is a free PDF accessibility checker with PDF/UA and WCAG checks. Treat its output as validation evidence, not a complete manual review.
• DocAccessibleautomates steps 2 through 6 and gives you an HTML version with the same content plus a rebuilt tagged PDF. It does not promise to preserve the source PDF's exact design.
• The Matterhorn Protocol lists failure conditions for PDF/UA-1. Some conditions can be checked by software and others require human judgment. The open source veraPDF validator can provide machine-readable PDF/A and PDF/UA validation results.

Verification 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 publishes the hosted HTML version from a single upload and generates a rebuilt PDF/UA-aligned tagged PDF for offline distribution and manual validation.

When the original PDF design must not change

Exact layout preservation is manual remediation work. A specialist repairs the source PDF's tags, reading order, tables, forms, alt text, and metadata while preserving its pagination and visual design. DocAccessible agency work is $5 per accepted source page for projects above 500 pages, regardless of page complexity, and is billed separately from the software subscription. See the remediation-path decision guide or use the remediation contact form for an assessment.