11 WCAG PDF Accessibility Checks
Every PDF you upload is checked against these 11 WCAG 2.1 AA criteria. Each check is weighted by severity — total: 100 points.
1. Tagged PDF
WCAG 1.3.1 · 15 points
The document must have a proper tag tree that defines the logical structure — headings, paragraphs, lists, tables, and other elements. Without tags, screen readers cannot parse the document at all.
What we fix
Our AI adds structure tags to untagged PDFs, identifying headings, paragraphs, lists, and table structures.
2. Document Title
WCAG 2.4.2 · 8 points
The PDF metadata must include a descriptive title. Screen readers announce this title when the document is opened. Without it, users hear the filename instead.
What we fix
We generate a descriptive title from the document content and set it in the metadata.
3. Document Language
WCAG 3.1.1 · 8 points
The document language must be specified in the metadata so screen readers use the correct pronunciation rules and speech synthesis.
What we fix
We detect the document language and set the appropriate language attribute.
4. Bookmarks
WCAG 2.4.5 · 7 points
Documents longer than a few pages should have bookmarks that mirror the heading structure, providing a navigational outline for all users.
What we fix
We generate bookmarks from the heading tag structure automatically.
5. Heading Hierarchy
WCAG 1.3.1 · 10 points
Headings must follow a logical hierarchy (H1 → H2 → H3) without skipping levels. This gives screen reader users the same structural overview that sighted users get from visual formatting.
What we fix
We analyze and correct heading levels to ensure proper nesting without skipped levels.
6. Image Alt Text
WCAG 1.1.1 · 12 points
Every meaningful image must have alternative text that conveys the same information as the image. Decorative images should be marked as artifacts.
What we fix
Our vision AI generates descriptive alt text for images. Decorative elements are marked as artifacts.
7. Table Headers
WCAG 1.3.1 · 10 points
Data tables must have header cells (TH) properly marked and associated with data cells so screen readers can announce column/row context as users navigate.
What we fix
We identify table header rows and columns and mark them with proper TH tags.
8. Reading Order
WCAG 1.3.2 · 10 points
Content must be read in a meaningful, logical sequence. Multi-column layouts, sidebars, and complex formatting can create reading order problems.
What we fix
We analyze the visual layout and set a logical tag order that matches the intended reading flow.
9. Color Contrast
WCAG 1.4.3 · 8 points
Text must meet minimum contrast ratios: 4.5:1 for normal text and 3:1 for large text (18pt or 14pt bold). Ensures readability for users with low vision.
What we fix
We flag insufficient contrast in the scan report. Color changes require manual review.
10. Font Embedding
WCAG 1.3.1 · 5 points
All fonts must be embedded in the PDF to ensure text renders correctly on any system. Missing fonts can cause text to display incorrectly or become unselectable.
What we fix
We check for embedded fonts and flag any missing ones in the report.
11. Form Field Labels
WCAG 1.3.1 · 7 points
Interactive form fields must have programmatic labels so screen readers can identify what information each field expects.
What we fix
We add labels to unlabeled form fields based on surrounding text context.
How Scoring Works
Each check has a point weight based on its impact on accessibility. Your PDF score is the percentage of points earned out of the total100 possible points.
A score of 90-100 means your PDF is largely compliant. 70-89 indicates moderate issues that should be addressed. Below 70 means significant accessibility barriers exist.
Automated checks catch structural and metadata issues effectively, but some criteria (like alt text quality and reading order correctness) benefit from human review after AI remediation.
Upload a PDF to see your results
Free, instant scan across all 11 checks. No account required.
Check Your PDF Now