Ulrickson VenturesADA document accessibility

Our accessibility checklist (v1.0)

Every PDF document and fillable PDF form we deliver is checked against this list. Each file comes with a conformance report that shows the result of every check: Pass, or "does not apply" with a written reason. The list follows the parts of the web accessibility guidelines (WCAG 2.1 AA) and the PDF accessibility standard (PDF/UA-1) that apply to PDF files.

1. Document setup

  • The file has tags. Tags are the hidden structure screen readers use to read a document. Every PDF we deliver is tagged. (PDF/UA 7.1)
  • Nothing on the page is missed. Everything on every page is either tagged so it gets read, or marked as decoration so it gets skipped. (WCAG 1.3.1)
  • The document has a real title. A meaningful title is saved in the file, and the title shows at the top of the window in place of the file name. (WCAG 2.4.2)
  • The language is set. The main language of the document is set correctly, so screen readers pronounce words properly. Any passage in another language is marked with its own language. (WCAG 3.1.1, 3.1.2)
  • The file is labeled as an accessible PDF. The file carries the standard marker saying it follows the PDF accessibility standard. (PDF/UA 5)
  • The text can be read by computers. All fonts are included in the file, and every letter maps to a real character, so the text can be copied, searched, and read aloud. (WCAG 1.3.1)
  • No pages are just pictures of text. Scanned pages are turned into real text with text recognition (OCR), and a person proofreads that text. (WCAG 1.1.1, 1.4.5)
  • Security settings don't block assistive tools. Password or copy protection never stops a screen reader from reading the content. (WCAG 4.1.2)
  • Long documents have bookmarks. Documents of 10 pages or more have bookmarks (a clickable outline) that match the headings. (WCAG 2.4.5, best practice)

2. Structure and reading order

  • It reads in the right order. A screen reader reads the content in the same order a sighted person would, including pages with columns, sidebars, and call-out boxes. A person does a full reading-order review of any page whose order was changed automatically. (WCAG 1.3.2, 2.4.3)
  • Headings are marked as headings. Headings are tagged at the right level (Heading 1, Heading 2, and so on) on the right text, with no levels skipped. (WCAG 1.3.1, 2.4.6)
  • Paragraphs are clean. Paragraphs are tagged as paragraphs, with no stray fragments or empty tags. (WCAG 1.3.1)
  • Lists are marked as lists. Anything that looks like a list is tagged as a list, so screen readers announce it and count the items. (WCAG 1.3.1)
  • Data tables are set up properly. Tables of data are tagged as tables, header cells are linked to the rows or columns they describe, and merged cells are set up correctly. (WCAG 1.3.1)
  • Tables used only for layout are not treated as data tables. (WCAG 1.3.1)
  • Only standard tags are used. Any custom tag is linked to a standard type that assistive tools understand. (WCAG 4.1.2)
  • Repeated page clutter is skipped, and real content is not. Running headers and footers, page numbers, watermarks, and decorative lines are marked as decoration. Nothing meaningful is hidden that way. (WCAG 1.3.1)
  • Footnotes and references are tagged and placed where they make sense in the reading order. (WCAG 1.3.1)

3. Images, charts, and visual presentation

  • Informative images have alt text. Alt text is a short written description of an image for people who can't see it. It is accurate and concise. Any automatically drafted alt text is reviewed and approved by a person. (WCAG 1.1.1)
  • Decorative images are skipped. Images that are only decoration are marked so screen readers pass over them. (WCAG 1.1.1)
  • Charts, maps, and diagrams are explained. They have alt text summarizing the key information, and the full information is also available as text or as a table. (WCAG 1.1.1, 1.3.1)
  • Pictures of text are avoided, or the text in them is made available as real text. (WCAG 1.4.5)
  • Text is easy to see against its background. Text meets a contrast ratio of at least 4.5 to 1, or 3 to 1 for large text (18 point, or 14 point bold). (WCAG 1.4.3)
  • Important graphics are easy to see. Form field borders, chart elements, and other meaningful graphics have a contrast ratio of at least 3 to 1. (WCAG 1.4.11)
  • Color is never the only signal. For example, "overdue" is not shown only by red text. (WCAG 1.4.1)
  • Instructions don't depend only on shape, size, or position. For example, not just "click the box on the right." (WCAG 1.3.3)

4. Links, comments, and navigation

  • Links are set up properly. Each link is tagged as a link and has a text description screen readers can announce. (WCAG 2.4.4, 4.1.2)
  • Link text makes sense. You can tell where a link goes from its text or the words around it. No bare "click here." (WCAG 2.4.4)
  • Comments and stamps are handled. Other markups, like comments and stamps, are tagged with a description, or removed if they aren't needed. (WCAG 1.1.1)
  • The Tab key follows the structure. On pages with links or form fields, pressing Tab moves through them in the document's reading order. (WCAG 2.4.3)

5. Fillable forms (when the PDF has form fields)

  • Every field has a name a screen reader announces, and it matches or includes the label you see on the page. (WCAG 1.3.1, 2.5.3, 3.3.2, 4.1.2)
  • Every field sits in the right place in the reading order. (WCAG 1.3.1)
  • The Tab key moves through the form in a sensible order that follows how the form looks and reads. (WCAG 2.4.3)
  • Fields behave the way they look. Each field is the right type and announces what it is, its state, and its value. Radio buttons are grouped under a group name, and checkboxes announce "checked" or "unchecked." (WCAG 4.1.2)
  • Required fields and formats are spelled out. Required fields and expected formats (such as MM/DD/YYYY) are stated in the visible text and in what the screen reader announces. (WCAG 3.3.2)
  • Everything works with a keyboard alone. Every field can be reached and filled in without a mouse, and you never get stuck in a field. (WCAG 2.1.1, 2.1.2)
  • Errors are explained. If the form checks your entries or calculates values, errors are announced in text with a suggestion for fixing them. (WCAG 3.3.1, 3.3.3)
  • Signing is accessible. Signature fields and their instructions have names a screen reader announces, and the form states an accessible alternative way to sign or submit. (WCAG 3.3.2, 4.1.2)

6. Items that usually don't apply to PDFs

We still list these in every report so it is complete.

  • Video and audio, time limits, flashing content, screen orientation, and content that changes on its own are marked "does not apply" unless the PDF has embedded media or scripts. (WCAG 1.2, 2.2, 2.3.1, 1.3.4, 3.2)
  • Zooming and reflowing text depend on the PDF reader you use. We record these as met through the reader's zoom, note that reflow depends on the reader, and list this as a limitation, not a Pass. (WCAG 1.4.4, 1.4.10)

How we check

  • Automated checks. Two automated checkers: veraPDF and PAC 2024. Every file must show no failed rules in veraPDF and no failures in PAC 2024.
  • Screen reader and keyboard review. A person spot-checks every file with a screen reader and the keyboard and reviews every item our tools flag, such as reading order, image descriptions, tables and form fields.
  • Human sign-off. A person signs off on every deliverable, and the result of each check is recorded in its conformance report.

What this is not

This checklist describes what we check. It is information only, not legal advice, and not a guarantee that any document meets every legal requirement.

Last updated: October 2026