A practical review workflow
PDF accessibility checklist
Start with automated checks, then review the content a machine cannot judge. Use this checklist to keep track of your review—not to certify a document as accessible.
The checker examines eight basic signals in your browser without uploading your document. This broader checklist includes manual tasks beyond those signals. It is a starting workflow, not an exhaustive WCAG, Section 508 or PDF/UA audit.
Before you start
Keep the source document and its latest PDF export together. If a web page would meet the reader’s needs better, consider publishing accessible HTML alongside or instead of the PDF. Use the official Section508.gov testing resources when you need their full testing process.
0 of 10 review steps marked complete. This is review progress, not an accessibility score.
Your selections stay in this tab and are cleared when this page is reloaded. No document details are collected here.
Basic signal + manual review
Try selecting and searching for a sentence. For a scanned page, run OCR in an appropriate editor, then check the recognized text against the original. Extractable text alone does not establish accessibility.
Basic signal + manual review
Check that the document title is meaningful and the default language matches the content. Review passages in other languages separately.
Basic signal + manual review
Inspect the tag tree against the visible content. Use semantic headings, paragraphs and lists; verify that meaningful content is included. A tagging flag and a structure tree are independent signals.
Manual review
Follow the document with a screen reader, especially columns and sidebars. Tab through links and form fields. The sequence should preserve meaning and be usable from the keyboard.
Manual review
Check every meaningful image in context. Its alternative text should convey its purpose; decorative content should not interrupt reading. Our checker cannot find every untagged image or judge description quality.
Manual review
Inspect each data table and its header relationships. Confirm that a reader can identify which row and column a value belongs to. A header tag alone does not validate a complex table.
Manual review
Use meaningful link text, check destinations and complete forms with the keyboard. Verify field labels, required fields and useful error messages. These checks are outside our automated first pass.
Manual review
Review text and meaningful graphics with suitable contrast tools. Confirm that instructions or categories do not rely on color alone. Our checker does not measure visual contrast.
Basic signal + manual review
Compare headings with the document’s organization. Check bookmarks where they help navigate a longer document, and make sure their destinations and labels are useful.
Manual review
Correct the authoring file when possible, export again, rerun automated checks and repeat manual tests. Record unresolved issues before sharing the file.
What should I fix first?
If text cannot be read or structure is missing, investigate those foundations first. Then review sequence and meaning. For example, a two-column page may expose text yet read across both columns in the wrong order. A populated tag tree does not settle that question.
Compare tagged and untagged examples, then use the checker’s sample files to learn how its signals differ. After repairs, review the exported file rather than assuming the source fixes carried through.
Does completing the list mean my PDF passes?
No. Checking a box records your review step; it does not test the file or establish conformance. Complex documents can require further checks, dedicated validators and specialist review. Keep unresolved findings in your review notes and use the requirements that apply to your document.
Optional analytics
Help us measure visits. Your choice does not affect access to this guide or the checker. How measurement works.