Our Accessibility Standards

Our commitment to true accessibility—not just compliance checkboxes, but documents that work for everyone.

Standards We Work To

PDF AA Compliance remediated documents meet or exceed these internationally recognised accessibility standards.

WCAG 2.1 AA

Web Content Accessibility Guidelines—the global standard for digital accessibility, referenced by regulations worldwide.

  • Perceivable content
  • Operable navigation
  • Understandable structure
  • Robust compatibility

PDF/UA-1

ISO 14289-1—the international standard specifically for accessible PDF documents and assistive technology compatibility.

  • Tagged PDF structure
  • Marked content sequences
  • Logical reading order
  • Alternative descriptions

Section 508 / ADA

U.S. regulatory requirements for federal agencies and organisations, including ADA Title II web accessibility deadlines.

  • Federal compliance
  • ADA Title II ready
  • State & local support
  • Audit documentation

WCAG 2.1 Criteria We Address

Our remediation process specifically targets these accessibility requirements.

1.1.1

Non-text Content

All images receive AI-generated alternative text that describes their content and purpose within the document context—not generic descriptions like "image" or "photo".

1.3.1

Info and Relationships

Document structure is programmatically determined through proper semantic tags: headings (H1-H6), paragraphs, lists, tables, and figures—all correctly nested and related.

1.3.2

Meaningful Sequence

Reading order is determined by visual position on the page—top to bottom, left to right—ensuring content is read in the order the author intended.

2.4.1

Bypass Blocks

Heading structure enables users to navigate between sections quickly, bypassing repetitive content and jumping directly to the information they need.

2.4.2

Page Titled

Documents include descriptive titles in metadata, displayed in the document viewer title bar so users immediately know what document they're viewing.

2.4.6

Headings and Labels

Headings are detected based on visual styling (font size, weight) and properly tagged with correct hierarchy (H1, H2, H3...) to describe the content that follows.

3.1.1

Language of Page

Document language is specified in metadata, enabling screen readers to use the correct pronunciation rules and language-specific processing.

4.1.2

Name, Role, Value

All document components have programmatically determinable names and roles that assistive technology can identify and communicate to users.

Our Technical Approach

True accessibility requires understanding how screen readers actually navigate PDF documents.

Semantic Structure Tree

We build a complete structure tree that defines the logical organisation of your document. This tree is what screen readers traverse to present content in the correct order.

Document
├── H1 "Title"
├── Figure [alt: "..."]
├── H2 "Section 1"
├── P "Content..."
└── Table [headers]

Visual Reading Order

Reading order is determined by where content appears on the page—not by how the PDF file was constructed. Images, text, and other elements are ordered top-to-bottom, left-to-right, as a sighted reader would naturally read the page.

1
Header image and title
2
Section headings
3
Body text and inline figures
4
Footer content

Meaningful Alt Text

Every image receives alternative text that describes not just what's shown, but why it matters in context. Our AI understands the document type and generates descriptions that convey the intended information.

Generic:

"image"

Descriptive:

"Bar chart showing quarterly revenue growth: Q1 $2.1M, Q2 $2.4M, Q3 $2.8M, Q4 $3.2M"

Screen Reader Tested

We test with real screen readers—not just validation tools. Compliance checkers can pass documents that fail for actual users. Our goal is true accessibility, not just checkbox compliance.

NVDA

Windows

JAWS

Windows

VO

macOS/iOS

Our Commitment

Accessibility isn't just about compliance—it's about ensuring that everyone can access the information they need. We're committed to producing remediated documents that work with real assistive technology, for real users.

Continuous Improvement

We continuously update our remediation engine based on the latest standards and real-world screen reader testing.

Transparency

We're clear about what we can and can't remediate. Some documents may require manual review for complex elements.

User-Focused

Our measure of success isn't just passing a validator—it's whether a screen reader user can actually use the document.

Ready to Make Your Documents Accessible?

Upload a PDF and see the difference standards-compliant remediation makes.

PDF/UA-1

ISO 14289-1

WCAG 2.1 AA

Level AA

Section 508

Revised

ADA

2027 / 2028