Docs-site engineering and accessibility

Docs accessibility audit

This is for SaaS teams whose documentation site or help center has to meet WCAG 2.2 AA, whether because a customer's procurement team asked, because the product sells to the public sector, or because nobody has checked and it is the right thing to do. We audit the docs the way disabled readers use them, then hand your developers a prioritized list of fixes they can act on without having to interpret the standard themselves.

Price

WCAG 2.2 AA audit from $1,900

Response

Reply within 1 business day

After delivery

30-day fix window

Who it's for#who-its-for

Engineering leads who received an accessibility questionnaire or a VPAT request and need to know where the docs site actually stands.
Docs leads running a Docusaurus, MkDocs or GitBook site with a custom theme that nobody has tried with a keyboard or a screen reader.
Heads of support whose help center is the first place customers with disabilities go when something in the product does not work for them.
Revenue and compliance leads at companies selling into enterprise or government accounts, where accessibility conformance comes up during procurement and security review.

In the US this often comes up as ADA compliance. The audit tests against WCAG 2.2 AA, the technical standard those conversations usually point to. The audit also works as a baseline before a redesign or a migration, because fixing templates before content moves is cheaper than fixing them after.

What you get#what-you-get

An audit of the templates your pages are built from and the content patterns that repeat across them, so a fix in one place repairs every page that shares it:

Automated scans across representative pages, with duplicates and false positives filtered out.
Manual testing of each template: keyboard-only navigation, focus order and visibility, screen reader testing with VoiceOver and NVDA, zoom and reflow, and color contrast, including code blocks.
Content checks: heading structure, link text, alt text, tables, and how diagrams and screenshots are described.
Coverage of the criteria added in WCAG 2.2, such as focus hidden behind sticky headers and minimum target size for controls.
A findings report mapped to WCAG success criteria, each finding with a severity, the affected templates, a screenshot and a concrete fix.
A prioritized fix list your developers can turn straight into tickets.

Each finding is written for the person who will fix it: which element, which criterion, what a screen reader announces today and what it should announce instead. Where a fix belongs in a shared component, the report says so, so it is made once rather than on every page.

How it runs#how-it-runs

Scope. You send the URL and any known issues. We pick representative templates and page types together, and we confirm a fixed audit price.
Testing. We run the automated and manual tests and record every issue with evidence and steps to reproduce it. The report lists the browser and assistive technology combinations we used, so your team can reproduce every finding.
Report. You receive the report and the fix list, and we walk your team through the findings on a call.
Remediation, if you want it. We fix the issues ourselves at the docs-engineering rate, or review your team's fixes as they land.
30-day fix window. For 30 days after delivery, we answer questions about findings and re-check fixed issues; if we did the remediation, we fix anything we broke at no charge.

An audit is a snapshot. To keep new pages from reintroducing the same problems, the handbook page on review gates covers the automated checks worth adding to CI after the fixes land.

Pricing#pricing

WCAG 2.2 AA audit: From $1,900; about €1,750
Remediation, hourly: $75 / hour; about €69
Remediation, daily: $560 / day; about €520

The audit starts at $1,900 for a typical docs site built from a small set of templates. The price rises with the number of distinct templates and interactive components, such as API explorers, embedded sandboxes, custom search interfaces and video, and with the number of sites or subdomains in scope. Gated content, such as docs behind a customer login, is in scope if you provide a test account.

If a redesign is already planned, it can make more sense to audit the new templates on staging than the current site. We will tell you which is the better use of the budget before you commit.

Remediation is billed at the docs-engineering rate against an estimate taken from the fix list. Because the audit tests templates rather than individual pages, most fixes are made once in a theme or component, not page by page.

The audit is not a legal opinion or a certification. It tells you where the site stands against the standard and exactly what to fix.

Prices are in US dollars; the euro figures are approximate conversions for reference.

Frequently asked questions#faq

Is an automated scan enough?

No. Automated tools catch a useful share of issues, such as missing alt text and many contrast failures, but they cannot tell whether focus order makes sense, whether alt text is meaningful, or whether a screen reader user can complete a task. The audit uses scans as a starting point, not a verdict.

Does the audit make us ADA compliant?

The audit measures the docs site against WCAG 2.2 AA and tells you what to fix. Whether that satisfies a legal obligation is a question for your counsel; we do not give legal advice.

Is Docusaurus accessible out of the box?

The default theme is a reasonable starting point, with a skip link and semantic landmarks. Most problems come from custom themes, swizzled components, low-contrast syntax highlighting, and content patterns such as skipped heading levels and vague link text.

Do you audit the product as well as the docs?

The service is scoped to documentation sites and help centers. Findings in shared components often apply to the product too, and the report notes where they do.

Can you help with our VPAT?

The findings are mapped to WCAG success criteria, which is the structure a VPAT or accessibility conformance report follows, so your team can use them directly. Writing and signing the conformance statement stays with your company.

Send us what you have

Send a link to your docs, an export, or a few lines on what needs to change. We reply within 1 business day with questions or a quote.

Start a project Email us