DOCUMENT ACCESSIBILITY

Important documents.
More accessible
experiences.

Help people read, navigate, and use the information inside your files.

EqualAccess. identifies and remediates accessibility barriers in PDFs and Office documents—from structure and reading order to images and forms. Human experts make the changes, retest the files, and document the work.

Manual remediation Assistive-technology testing
WCAG & PDF/UA targets defined for your project

Visual demonstration only. Human experts perform the work, supported by testing tools. Scope and results vary by document.
PDFsWord documentsPowerPoint presentationsExcel spreadsheets

THE CONTEXT

A file can look clear.
Its structure can tell another story.

A report might look organized on screen while its headings, tables, and instructions are difficult to navigate with assistive technology. Accessibility depends on how the content is structured and how it behaves in use.

We help make that information understandable: meaningful headings, logical reading order, useful image descriptions, and forms people can complete.

A PRACTICAL EXAMPLE

In a product manual, a setup diagram needs an equivalent explanation. The instructions also need a sensible reading sequence and headings readers can navigate.

Technical references: W3C PDF techniques and PDF Association’s PDF/UA guidance.

WHAT WE FIX

The details that make
a document usable.

Automated analysis helps locate detectable issues. Expert review determines the corrections that fit the document and its purpose.

Tags & structure

Identify headings, paragraphs, lists, tables, figures, and links with the appropriate document structure. Check table headers and relationships as well as the presence of tags.

Reading & tab order

Arrange content into a meaningful reading sequence. Review complex layouts and check the keyboard order of links and form fields in the agreed reading environment.

Images & graphics

Write text alternatives that convey the purpose of meaningful images. Provide fuller explanations for complex charts, and mark purely decorative content appropriately.

Forms & controls

Give interactive PDF fields meaningful accessible names, instructions, and an appropriate tab order. Review required-field information, errors, and completion behavior where applicable.

Contrast & color

Review text, essential graphics, and information conveyed by color. Correct presentation or add clear labels and other cues, with your approval where design changes are needed.

Language & metadata

Set useful document titles and language information, including language changes where supported. Review links, bookmarks, and navigation appropriate to the file.

Scanned documents may also require OCR, text correction, and rebuilding before structural remediation.

OUR FIVE-STEP PROCESS

From the first file
to a documented handover.

A clear sequence for understanding the collection, correcting barriers, and checking the results.

01 / Assess

Understand the document collection.

Review representative files, source formats, page counts, audiences, and publishing needs. Agree the accessibility target and identify priority forms, instructions, and frequently used documents.

02 / Manual Testing

Look beyond the checker results.

Combine automated analysis with expert inspection of tags, reading order, tables, visuals, and interactive fields. Investigate how the files work in the agreed reader and assistive-technology environment, then prioritize the findings.

03 / Code-Level Remediation

Repair the underlying structure.

Correct the document’s tags, content, properties, and form fields. Where editable sources are available, improve the source file and export settings before checking the resulting PDF. For this service, code-level work means the document’s underlying structure—not HTML overlays.

04 / Retest & Verify

Check the finished experience.

Repeat automated checks and manually verify the affected content. Review reading order, heading navigation, tables, and forms with appropriate assistive technology. Record the tested environment and resolve or document remaining limitations.

05 / Documentation

Deliver the files and the record.

Hand over the remediated documents with findings, completed work, test results, and any known limitations. Include authoring guidance and, when separately scoped, an Accessibility Conformance Report.

WHAT YOU RECEIVE

The files. The findings.
The record of what changed.

Deliverables are agreed around your document collection and accessibility target.

ILLUSTRATIVE HANDOVER

A clear record,
file by file.

Remediated filesVersions identified
Verification recordMethods and results
Publishing guidanceNext steps for your team

Known limitations belong in the handover too.

  • Remediated documents

    The agreed PDFs and source documents, with file versions clearly identified.

  • Accessibility findings

    Document and page references, affected content, and relevant criteria.

  • Prioritized remediation record

    A practical account of the planned work and completed corrections.

  • Verification notes

    Methods, reading environments, results, and remaining limitations.

  • VPAT® / ACR, when scoped

    An Accessibility Conformance Report prepared using the appropriate VPAT template—not a certification.

  • Guidance for future publishing

    Recommendations for source files, templates, exports, and author review.

BEFORE & AFTER

See what document
remediation changes.

Illustrative examples of individual barriers. Each document still needs review against the full agreed scope.

Give a heading its meaning.

A larger font does not communicate a heading’s role on its own. In a tagged PDF, we check the structure element and its place in the hierarchy.

BEFORE

A title stored as a paragraph

PProduct installation guide

The visual title lacks the intended heading role.

AFTER

A meaningful heading structure

H1Product installation guide

Verify heading navigation and the hierarchy in the remediated file.

Simplified view of PDF structure tags, not HTML source code.

Keep the sequence meaningful.

Content that sits next to another column should not interrupt a sentence halfway through. The structure must preserve the meaning of the document.

BEFORE

Instructions are interleaved

  1. Prepare the workspace
  2. Care and cleaning
  3. Connect the supplied cable

A separate care section interrupts the setup instructions.

AFTER

Related content stays together

  1. Prepare the workspace
  2. Connect the supplied cable
  3. Care and cleaning

Check the reading sequence manually in the agreed PDF reader.

Illustrative sequence. The correct order depends on the content, not a universal left-to-right rule.

Describe the information that matters.

A useful alternative communicates the purpose or meaning of an image. Complex visuals may need a nearby explanation or a data table as well.

BEFORE

A figure without useful context

FigureNo text alternative

Readers cannot obtain the information represented by the chart.

AFTER

An equivalent explanation

Figure · AltNew accounts increased from 120 in Q1 to 180 in Q2.

Review the description against the actual chart and its context.

Invented example data used only to explain remediation. Decorative graphics are treated differently.

Make the field’s purpose available.

A visible label must also be connected to the field for assistive technology. PDF forms use PDF field properties rather than HTML ARIA attributes.

BEFORE

An internal name without a label

/FT /Tx
/T (zip)

The field needs a meaningful programmatically associated label.

AFTER

A descriptive field tooltip

/FT /Tx
/T (zip)
/TU (ZIP code, 5 digits)

Verify the accessible name, field behavior, and tab order.

Simplified PDF field-dictionary fragments, not a complete form or a complete accessibility fix.

W3C techniques: reading and tab order, text alternatives, and PDF form labels.

PACKAGES & PRICING

Start with the scope
that fits your documents.

A single form and a large document library need different plans. We review complexity, source quality, file volume, and required testing before quoting.

Document accessibility engagement options
EngagementIncludesBest suited toPricing
Accessibility auditA defined assessmentReview representative files or an agreed collection, investigate barriers, and document findings and priorities.Teams establishing the scope of work.Custom quoteQuoted by assessment scope
Remediation projectA planned set of filesRemediate the agreed documents, verify the changes, and deliver files with remediation and testing records.A document collection or a priority backlog.Custom quotePer-page or fixed-project quote
Ongoing supportSupport as content changesReview new or updated files, support authors, and plan recurring checks at an agreed frequency.Teams that publish documents regularly.Custom quoteScoped recurring engagement

A quote based on the actual files.

Tables, forms, scans, complex graphics, and missing source files can change the effort. Deliverables, review rounds, and timing are agreed before the project starts.

Get a Free Review

CLIENTS & USE CASES

For the documents
people depend on.

Public services & regulated content

Forms, notices, instructions, and reports supporting government, education, healthcare, or financial services. Applicable requirements are assessed in context.

Reported accessibility barriers

An audit, complaint, or demand letter identifies inaccessible PDFs or forms. Start with the affected documents and determine the wider technical scope.

Procurement & contracts

A buyer needs documented accessibility testing or an ACR for an agreed product or document set. Confirm the required reporting format early.

Content-rich websites

Product catalogs, installation manuals, policies, statements, and downloadable guides deserve the same attention as the pages linking to them.

Legacy document collections

Prioritize a backlog, review scans and source files, and decide which documents to remediate, recreate, or present in another suitable format.

Ongoing publication

Recurring reports, forms, newsletters, and presentations need repeatable authoring, review, and export checks as the content changes.

Have an accessibility complaint or demand letter?

Get Priority Support

BUILD ACCESSIBILITY INTO PUBLISHING

Make the next document
easier to get right.

Start with better source files and a repeatable review process. We can help your team use templates, heading styles, meaningful descriptions, and appropriate export settings.

Improve the source.

Build structure into the editable document. Recheck the exported PDF, since conversion can introduce or preserve barriers.

Review before release.

Combine author checks with the agreed technical and manual review. Revisit changed files before they are published.

Support your authors.

Give the people producing documents practical guidance for the files and templates they use every day.

COMMON QUESTIONS

Frequently asked questions
about document accessibility.

PDF remediation addresses accessibility barriers in a PDF’s content and underlying structure. It can include repairing tags, reading order, headings, tables, text alternatives, links, and form fields. The file is then evaluated against the agreed accessibility target; remediation alone is not a certification.

WCAG criteria can be applied to documents, with interpretation appropriate to the format and applicable requirements. For example, Revised Section 508 applies WCAG 2.0 Level A and AA to covered electronic content, with specific exceptions and adaptations for non-web documents. A document’s intended use and applicable requirements determine the target.

We agree the standard, version, level, file formats, and testing environment before starting. Work may be evaluated against WCAG 2.1 or 2.2 Level AA, applicable Section 508 criteria, and an appropriate PDF/UA target for PDFs. We do not assume every document is subject to the same legal requirements.

Automated checks help find detectable technical issues, but cannot determine whether every description is meaningful or every reading sequence makes sense. EqualAccess. combines tools with expert inspection, manual remediation, and assistive-technology testing. A passed checker does not establish complete accessibility.

Timing depends on file count, page count, complexity, source-file availability, and review requirements. Scanned pages, complex tables, and interactive forms can require additional work. We establish the scope and schedule after reviewing representative files, and can prioritize critical documents within the agreed plan.

WCAG defines accessibility outcomes across content. PDF/UA is a PDF-specific standard focused on the format’s accessibility features, including its logical structure. They are complementary: PDF/UA conformance alone does not establish that every relevant WCAG requirement, such as color contrast, has been met.

No. Technical remediation does not guarantee a legal outcome or prevent future claims. We focus on addressing identified barriers, verifying the agreed work, and documenting findings and limitations; qualified legal counsel should advise on legal obligations and risk.

Optical character recognition (OCR) can recover text from scanned pages, but the results need review and correction. Structure, reading order, tables, and text alternatives still need attention after OCR. Low-quality originals may need to be replaced or recreated, which we discuss during scoping.

Check new and revised documents before publishing, and retest when edits or exports may affect accessibility. The review schedule for an existing collection depends on how frequently it changes and how it is used. We can support recurring reviews and help your team build accessibility into its publishing workflow.

Additional guidance: Section508.gov document resources · Revised Section 508 content requirements · W3C guidance on scanned PDFs.

LET’S START WITH YOUR DOCUMENTS

A clearer path
to accessible information.

Tell us about the files, how they are used, and what prompted the review. We’ll help define the technical work and the practical next steps.

Opens in a new tab.