What makes a PDF usable by a screen reader?

A tagged structure. A screen reader does not "see" the page layout; it reads a hidden structure tree of tags that say "this is a heading, this is a paragraph, this is a list, this image means X, this is a table with these headers." An untagged PDF has no such structure, so a screen reader either guesses (badly) or reads nothing useful — the user gets a jumble or silence. Making a PDF accessible is largely about giving it correct tags, in the right reading order, with text alternatives for non-text content. The visible page can look identical; the difference is the invisible structure underneath that assistive technology relies on.

What is "reading order" and why does it matter so much?

Reading order is the sequence in which the tagged content is read aloud, and it must match the logical order a sighted reader would follow — title, then intro, then section by section. PDF stores content by position, not order, so a document can look correct visually while its underlying order is scrambled (a sidebar read in the middle of a paragraph, a caption before its figure). For a screen-reader user, wrong reading order turns a clear document into nonsense. After tagging, you verify and fix the reading order specifically, because correct tags in the wrong order are still inaccessible. It is one of the most common and most important fixes.

How do I handle images and decorative graphics?

Every meaningful image needs alternative text — a concise description of what it conveys — so a screen reader can speak it; a chart needs its data or conclusion described, not just "chart." Purely decorative images (borders, background flourishes) should be marked as artifacts so the screen reader skips them rather than announcing meaningless content. The judgment is: does this image carry information the reader needs? If yes, describe it; if no, mark it decorative. Missing alt text on an informative image is a hard barrier; verbose alt text on decoration is noise. Audit your images and give each the right treatment.

How should tables and forms be made accessible?

Tables need their structure tagged — header cells identified so a screen reader can say "Revenue, Q3: $40k" by associating each data cell with its row and column headers; a table that is just a visual grid of untagged cells is unreadable non-linearly. Keep tables simple (avoid merged/nested cells where you can) and reserve them for actual tabular data, not layout. Forms need each field to have an accessible label/tooltip, a logical tab order matching the visual order, and clear instructions, so a screen-reader user can complete them. Both come down to making the relationships (cell-to-header, field-to-label) explicit in the structure, not just visually apparent.

What are PDF/UA and WCAG, and do I need to comply?

PDF/UA (ISO 14289) is the technical standard for accessible PDFs — it specifies what a conforming accessible PDF must contain (tags, reading order, alt text, and so on). WCAG (the W3C Web Content Accessibility Guidelines) is the broader accessibility standard often referenced by law, and Section 508 in the US and similar laws elsewhere require accessible documents in many contexts. Whether you must formally comply depends on your jurisdiction and sector (government, education, and large organisations frequently must), but the practical work is the same regardless: tag the document, get reading order right, add alt text, label forms. Aim for the standard even when not strictly mandated — it is simply usable by more people.

How do I verify a PDF is actually accessible?

Combine automated checks with a manual review and, ideally, a real screen-reader test. Automated tools catch missing tags, missing alt text, missing document language, and missing form labels — fix what they flag. But automated checks cannot judge whether reading order is logical or whether alt text is meaningful, so also read the document's tag/reading order and spot-check alt text yourself. The gold standard is to navigate the finished PDF with an actual screen reader and confirm it makes sense heard, not just seen. "Passed the automated checker" is necessary but not sufficient; a human pass catches the things that matter most to real users.

Is it safe to run accessibility checks online?

For confidential documents, prefer tools that process files locally. ScoutMyTool runs checks like image alt-text auditing, font-embedding verification, and form-label association in your browser tab, so the document never leaves your machine. For anything sensitive, confirm the tool does not upload before using it. The accessibility remediation itself (tagging, reading order, alt text) is also best done in tools you trust with the document.

6 min read

How to make a PDF accessible to screen readers: full guide

By ScoutMyTool Editorial Team · Last updated: 2026-05-22

The first time I listened to one of my own “finished” PDFs through a screen reader, it was humbling: it read the footer before the title, announced a decorative line as “image,” skipped a chart entirely, and rendered a table as a meaningless stream of numbers. The document looked perfect and was, to a screen-reader user, nearly unusable. Accessibility is mostly invisible structure — tags, reading order, text alternatives — that assistive technology depends on and sighted authors never see. This is the comprehensive guide: how screen readers consume a PDF, and how to tag, order, and describe your document — images, headings, tables, forms, language — so it works for everyone, plus how to verify it really does.

The accessibility checklist

Element	Requirement
Document tags	Tagged PDF with a proper structure tree
Reading order	Tag order matches the visual/logical order
Headings	Real heading tags (H1, H2…), nested correctly
Images	Alt text on meaningful images; decorative marked artifact
Tables	Header cells marked; simple structure
Links & forms	Descriptive link text; labeled, tab-ordered fields
Language & title	Document language and title set

Step by step — make a PDF screen-reader accessible

Start from real text, not an image. A scanned or image-only PDF has nothing to tag; OCR it first so there is text to make accessible.
Tag the document structure. Ensure it is a tagged PDF with headings, paragraphs, lists, tables, and figures marked — this is the foundation everything else builds on.
Fix the reading order. Verify the tag order matches the logical reading order; correct anything out of sequence (sidebars, captions, footers).
Add alt text; mark decoration. Describe meaningful images and charts; mark decorative graphics as artifacts. Audit with Image Alt-Text Audit.
Make headings, tables, and forms accessible. Real nested heading tags; table header cells marked; form fields labeled and tab-ordered with Form Label Association (see accessible form fields).
Set language, title, and bookmarks. Set the document language and title, and add a bookmark outline for navigation (see bookmarking sections); embed fonts via Font Embedding Check.
Verify — automated and human. Run automated checks (and validate if targeting an archival/UA profile), review reading order and alt text yourself, and ideally navigate it with a real screen reader. See PDF accessibility.

PDF accessibility: the practical overview.
Add fillable form fields: accessible forms.
Bookmark sections: navigable structure.
PDF compatibility: real text and standards.
PDF to interactive HTML: an even more accessible target for some content.
Image Alt-Text Audit: find images missing alt text.
All ScoutMyTool PDF tools: the full toolkit.

FAQ

What makes a PDF usable by a screen reader?: A tagged structure. A screen reader does not "see" the page layout; it reads a hidden structure tree of tags that say "this is a heading, this is a paragraph, this is a list, this image means X, this is a table with these headers." An untagged PDF has no such structure, so a screen reader either guesses (badly) or reads nothing useful — the user gets a jumble or silence. Making a PDF accessible is largely about giving it correct tags, in the right reading order, with text alternatives for non-text content. The visible page can look identical; the difference is the invisible structure underneath that assistive technology relies on.
What is "reading order" and why does it matter so much?: Reading order is the sequence in which the tagged content is read aloud, and it must match the logical order a sighted reader would follow — title, then intro, then section by section. PDF stores content by position, not order, so a document can look correct visually while its underlying order is scrambled (a sidebar read in the middle of a paragraph, a caption before its figure). For a screen-reader user, wrong reading order turns a clear document into nonsense. After tagging, you verify and fix the reading order specifically, because correct tags in the wrong order are still inaccessible. It is one of the most common and most important fixes.
How do I handle images and decorative graphics?: Every meaningful image needs alternative text — a concise description of what it conveys — so a screen reader can speak it; a chart needs its data or conclusion described, not just "chart." Purely decorative images (borders, background flourishes) should be marked as artifacts so the screen reader skips them rather than announcing meaningless content. The judgment is: does this image carry information the reader needs? If yes, describe it; if no, mark it decorative. Missing alt text on an informative image is a hard barrier; verbose alt text on decoration is noise. Audit your images and give each the right treatment.
How should tables and forms be made accessible?: Tables need their structure tagged — header cells identified so a screen reader can say "Revenue, Q3: $40k" by associating each data cell with its row and column headers; a table that is just a visual grid of untagged cells is unreadable non-linearly. Keep tables simple (avoid merged/nested cells where you can) and reserve them for actual tabular data, not layout. Forms need each field to have an accessible label/tooltip, a logical tab order matching the visual order, and clear instructions, so a screen-reader user can complete them. Both come down to making the relationships (cell-to-header, field-to-label) explicit in the structure, not just visually apparent.
What are PDF/UA and WCAG, and do I need to comply?: PDF/UA (ISO 14289) is the technical standard for accessible PDFs — it specifies what a conforming accessible PDF must contain (tags, reading order, alt text, and so on). WCAG (the W3C Web Content Accessibility Guidelines) is the broader accessibility standard often referenced by law, and Section 508 in the US and similar laws elsewhere require accessible documents in many contexts. Whether you must formally comply depends on your jurisdiction and sector (government, education, and large organisations frequently must), but the practical work is the same regardless: tag the document, get reading order right, add alt text, label forms. Aim for the standard even when not strictly mandated — it is simply usable by more people.
How do I verify a PDF is actually accessible?: Combine automated checks with a manual review and, ideally, a real screen-reader test. Automated tools catch missing tags, missing alt text, missing document language, and missing form labels — fix what they flag. But automated checks cannot judge whether reading order is logical or whether alt text is meaningful, so also read the document's tag/reading order and spot-check alt text yourself. The gold standard is to navigate the finished PDF with an actual screen reader and confirm it makes sense heard, not just seen. "Passed the automated checker" is necessary but not sufficient; a human pass catches the things that matter most to real users.
Is it safe to run accessibility checks online?: For confidential documents, prefer tools that process files locally. ScoutMyTool runs checks like image alt-text auditing, font-embedding verification, and form-label association in your browser tab, so the document never leaves your machine. For anything sensitive, confirm the tool does not upload before using it. The accessibility remediation itself (tagging, reading order, alt text) is also best done in tools you trust with the document.

Citations

Wikipedia — “PDF/UA” (ISO 14289), the technical standard for accessible PDFs. en.wikipedia.org/wiki/PDF/UA
W3C — “Web Content Accessibility Guidelines (WCAG),” the broad accessibility standard. w3.org/WAI — WCAG
Section508.gov — guidance on creating accessible PDFs (US federal). section508.gov/create/pdfs

Make your document work for everyone

Audit alt text, check fonts, and verify form labels with ScoutMyTool’s in-browser accessibility tools — your document never leaves your machine.

Open the Alt-Text Audit →