PDF Accessibility Compliance Guide — WCAG Checker & Auto-Fix

An inaccessible PDF is invisible to millions of people. Screen readers cannot parse untagged PDFs. Missing alt text means images convey nothing. Poor reading order turns a coherent document into nonsense. For organizations subject to the Americans with Disabilities Act (ADA), Section 508, or the European Accessibility Act, inaccessible PDFs also carry legal risk.

WhiskFile provides two tools to address this: a PDF Accessibility Checker that audits your document against WCAG 2.1 standards, and a PDF Accessibility Fix tool that automatically resolves the most common issues.

Why PDF Accessibility Matters

Legal requirements

Government agencies in the US must comply with Section 508, which requires electronic documents to be accessible. Private businesses that serve the public are subject to ADA requirements — and courts have increasingly applied those to digital documents, including PDFs posted on websites.

In the EU, the European Accessibility Act (effective 2025) extends accessibility requirements to private-sector products and services, including downloadable documents.

Practical impact

Approximately 15% of the world's population lives with some form of disability. For PDF documents specifically, the most affected users include:

• Visually impaired users who rely on screen readers (JAWS, NVDA, VoiceOver)
• Users with motor impairments who navigate with keyboards instead of mice
• Users with cognitive disabilities who benefit from clear structure and reading order
• Users on mobile devices who rely on reflow to read content at larger text sizes

An accessible PDF benefits everyone, not just users with disabilities. Tagged, well-structured PDFs reflow better on small screens, are easier to search, and convert more accurately to other formats.

What Makes a PDF Accessible?

The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA is the standard most organizations target. For PDFs, compliance means:

Tags and structure

Every piece of content in the PDF must be tagged with its semantic role — heading, paragraph, list, table, figure. Tags create a logical reading order that screen readers follow. Without tags, a screen reader reads raw text in the order it appears in the file's internal structure, which rarely matches the visual layout.

Alternative text

Every image, chart, diagram, and decorative element needs an alt text description. Decorative images (borders, background patterns) should be marked as artifacts so screen readers skip them entirely.

Reading order

The logical reading order must match the visual layout. In multi-column documents, the reading order should flow from column to column correctly, not jump between columns mid-sentence.

Document language

The PDF must declare its primary language (English, Spanish, etc.) so screen readers use the correct pronunciation engine.

Bookmarks and navigation

Long documents need bookmarks that mirror the heading structure, allowing keyboard users to jump between sections.

Color contrast

Text must have a minimum contrast ratio of 4.5:1 against its background (3:1 for large text). Information must not be conveyed by color alone.

Tables

Data tables need header cells marked as <TH> elements with proper scope attributes so screen readers can associate data cells with their headers.

Checking Your PDF for Accessibility Issues

Upload your document to the PDF Accessibility Checker. WhiskFile scans the file and reports issues organized by severity:

• Critical — Blocks screen reader access entirely (missing tags, no document language, images without alt text)
• Major — Significantly degrades the experience (incorrect reading order, unmarked table headers, missing bookmarks in long documents)
• Minor — Reduces quality but does not block access (suboptimal contrast ratios, missing metadata fields)

Each issue includes:

• A description of what is wrong
• The page and element where it occurs
• The relevant WCAG success criterion
• A recommendation for how to fix it

Auto-Fixing Common Issues

For the most common problems, the PDF Accessibility Fix tool handles remediation automatically:

1. Upload your PDF (or send it directly from the Checker results)
2. Review the list of fixable issues
3. Click Auto-Fix to apply corrections

What auto-fix handles

• Adding tags — Analyzes the document layout and inserts semantic tags (headings, paragraphs, lists, tables)
• Setting document language — Detects the primary language and sets the metadata
• Generating alt text — Uses AI to describe images and charts (review these for accuracy)
• Fixing reading order — Reorders tagged content to match the visual column layout
• Marking decorative images — Identifies borders, backgrounds, and logos that should be artifacts
• Adding bookmarks — Creates a bookmark tree from heading tags

What requires manual review

• Complex tables — Auto-tagging may not correctly identify merged cells or multi-level headers
• Mathematical content — Equations need MathML markup that requires manual insertion
• Form fields — Labels must be explicitly associated with their input fields
• Color contrast — Fixing contrast requires changing the source design, not just the PDF

After auto-fix, run the Checker again to verify the remaining issues. Address any manual items and re-check until the report is clean.

Best Practices for Creating Accessible PDFs

The most effective approach is to create accessible documents at the source:

• Use heading styles in Word, Google Docs, or your authoring tool — do not fake headings with bold large text
• Add alt text to images before exporting to PDF
• Use real lists (bulleted/numbered) instead of manually typed dashes or numbers
• Use real tables with header rows instead of tab-aligned text
• Set the document language in your authoring tool's properties

When you export to PDF from a properly structured source document, most of the tagging carries over automatically. WhiskFile's Checker and Fix tools are designed to catch what falls through the cracks.

Start by running your most important PDFs through the PDF Accessibility Checker. You may be surprised by how many issues a single scan reveals — and how many the Auto-Fix tool can resolve in one click.