Scanned PDF Accessibility Checklist: Text Layers, Reading Order, Tags, and Forms
PDF accessibilityOCRdigital documentsaccessible formsinclusive design

Scanned PDF Accessibility Checklist: Text Layers, Reading Order, Tags, and Forms

ddocuments.top Editorial Team
2026-11-19
7 min read

Use this scanned PDF accessibility checklist to verify OCR, reading order, tags, tables, forms, keyboard access, and testing before publication.

A scanned PDF is not automatically accessible just because it contains recognizable words. Use this practical checklist to add a reliable text layer, logical reading order, useful tags, accessible forms, and keyboard-friendly navigation before you publish, share, or archive a document.

Overview

Scanning creates an image of a page. Screen readers and other assistive technologies generally need more than that image: they need machine-readable text, a meaningful sequence, document structure, and correctly identified interactive elements. Optical character recognition (OCR) can supply the first layer, but OCR alone does not make a PDF accessible.

The right level of remediation depends on the document. A short contract, a multi-page form, a public-facing record, and a historical archive may require different treatment. The checklist below is designed for business documents and forms that will be read, completed, signed, stored, or reused.

Before starting, keep an untouched source scan. Work on a copy, retain the original for reference, and decide whether the final file must support searching, screen-reader use, keyboard completion, electronic signing, long-term retention, or all of these purposes. If OCR produces poor results, use the troubleshooting steps in this scanned PDF OCR guide before attempting detailed accessibility work.

Checklist by scenario

For a scanned contract or agreement

  • Create a dependable text layer. Run OCR at a quality level appropriate to the scan, then inspect names, dates, amounts, section numbers, and defined terms manually. A single recognition error can change meaning.
  • Set the document language. Apply the primary language in the PDF’s document properties. If a paragraph or clause uses another language, mark that change where your PDF software supports it.
  • Define a logical reading order. Confirm that the title, parties, introductory text, clauses, schedules, signature blocks, and footers are encountered in the intended sequence.
  • Tag headings and lists. Use heading levels to reflect the document hierarchy. Do not label text as a heading simply because it is bold or large.
  • Check signature areas. If the contract will be signed electronically, make sure signature, date, initials, and optional text fields have clear labels and a sensible tab order. For a broader sending checklist, see how to send a document for signature without missing required fields.
  • Preserve evidence of execution separately. Accessibility remediation should not alter signed content or remove relevant completion records. Keep the signing workflow and final-file controls aligned with your recordkeeping process.

For a fillable business form

  • Use real form fields, not drawn boxes. A visible line or rectangle does not tell a screen reader that information is required.
  • Give every field a specific name. “Address,” “invoice date,” and “authorized signer” are more useful than “field 1” or repeated generic labels.
  • Associate instructions and errors with fields. Explain the expected format for dates, phone numbers, or identification numbers, and provide an understandable error message when input is invalid.
  • Set a usable tab order. The keyboard should move through fields from top to bottom and left to right, or follow another clearly intended sequence.
  • Identify required fields visibly and programmatically. Do not rely on color alone or place the only explanation in an image.
  • Test signing and saving. A form may appear accessible in an editor but fail when opened in a different PDF viewer or passed to an electronic signature tool. For workflow considerations, review this paper-to-signed-PDF checklist.

For a public-facing report or record

  • Use a real title and metadata. Include a descriptive title, author or issuing team where appropriate, subject, and language.
  • Build a navigable structure. Tag headings, paragraphs, lists, tables, notes, and page artifacts according to their actual purpose.
  • Review tables carefully. Identify header cells, preserve row and column relationships, and avoid using merged or visually arranged cells when they make the data sequence unclear.
  • Add alternative text where it conveys information. Describe charts, diagrams, seals, or photographs that are necessary to understand the document. Mark decorative images as artifacts rather than adding meaningless descriptions.
  • Check contrast and visual cues. Text, links, instructions, and status indicators should remain understandable without depending on color alone.
  • Offer a better source when possible. For complex data, an accessible HTML page or structured source file may be easier to use than a remediated scan. Keep the PDF when it has archival, legal, or operational value, but do not assume it is the only useful format.

What to double-check

Run the following review before publishing an accessible PDF:

  1. Searchability: Select and copy text from several pages. Check names, numbers, punctuation, superscripts, and symbols against the scan.
  2. Reading order: Use the tag tree or reading-order panel, then listen through representative pages with a screen reader. Watch for columns read across the wrong direction, repeated headers, skipped footnotes, and page numbers inserted in the middle of sentences.
  3. Structure: Confirm one meaningful title, a sensible heading hierarchy, properly tagged lists, and correctly identified tables. A visually polished page can still have a disordered tag tree.
  4. Images: Check that informative graphics have concise alternative text and decorative elements are ignored. Do not duplicate a nearby caption unnecessarily.
  5. Forms: Navigate with the keyboard alone. Verify field labels, required states, radio-button groups, checkboxes, dropdowns, tooltips, and error messages.
  6. Visual presentation: Zoom in, inspect contrast, and confirm that text is not clipped or hidden behind form fields. Do not use scan artifacts, faint text, or background shading that makes content difficult to distinguish.
  7. Security and workflow: Confirm that passwords, permissions, redaction, signatures, and accessibility tools do not conflict. A document that cannot be read, completed, or reviewed because of unnecessary restrictions is not operationally accessible.

Use both automated checking and human review. An accessibility checker can identify missing tags, suspicious reading order, unlabeled fields, or metadata gaps, but it cannot reliably judge whether a clause is read in the right order or whether an image description is meaningful. Test with the PDF viewers, signing tools, and assistive technology your audience is likely to use.

Common mistakes

  • Stopping after OCR: OCR makes text searchable; it does not establish headings, tables, language, alternative text, or form semantics.
  • Tagging by appearance: A large bold line may be a heading, but a large bold line may also be a label or decorative text. Tag according to function.
  • Using a single image for a complete page: One full-page image with a hidden text layer can remain difficult to navigate if the text layer is inaccurate or the page has no meaningful structure.
  • Ignoring tables and columns: A screen reader may announce cells in an order that makes the information misleading. Test representative complex pages rather than assuming the layout is obvious.
  • Leaving form fields unnamed: Repeated labels such as “Text Field” force users to guess what each control does.
  • Testing only with a mouse: Keyboard access is essential for people who cannot use a mouse and is also a quick way to find a broken tab order.
  • Remediating the signed copy: Editing a completed or signed document can affect its integrity. Remediate the source before execution whenever possible, then confirm that the signing process preserves usability.
  • Relying on a pass message: Automated tools report technical conditions, not whether the document makes sense to a real reader.

When to revisit

Review this checklist whenever a new form set, contract template, archive batch, or public document series is introduced. Recheck it after changing OCR software, PDF editors, document-management systems, electronic signature tools, or export settings. A workflow change can remove tags, alter field names, flatten forms, or change reading order without an obvious visual difference.

It is also worth revisiting before seasonal planning cycles, annual form updates, major template revisions, and migrations from paper files to a digital archive. Keep a small test set containing a simple page, a two-column page, a table, an image, and a fillable form. Run that set through the proposed workflow before processing a larger batch.

For each release, record the source file, OCR or conversion step, accessibility review date, tester, known limitations, and final filename. If the document will be retained as a business record, compare accessibility requirements with your retention and archival approach; PDF/A guidance for business records can help frame that separate decision.

Final action: open the final PDF in its intended viewer, navigate without a mouse, listen to representative pages, complete every field, inspect the tags, and compare critical text with the original scan. Fix the source or workflow—not just one exported copy—so the next version starts accessible.

Related Topics

#PDF accessibility#OCR#digital documents#accessible forms#inclusive design
d

documents.top Editorial Team

Senior SEO Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.