Website accessibility audit
WCAG 2.2 AA testing with automated scans, keyboard checks and NVDA, JAWS and VoiceOver. Every issue mapped to the criterion and the fix.
ADA · WCAG 2.2 AA · Section 508 · PDF/UA
We audit and fix websites and documents so people using screen readers, keyboards and magnifiers can use them — and so you have written evidence of WCAG conformance if a demand letter or regulator ever arrives.
What we do
One accountable team for your website, your web apps and the thousands of PDFs behind them.
WCAG 2.2 AA testing with automated scans, keyboard checks and NVDA, JAWS and VoiceOver. Every issue mapped to the criterion and the fix.
We fix the code, components and content — or pair with your developers — then retest until every issue is closed.
Tagging, reading order, alt text, tables and fillable forms to PDF/UA and WCAG. Word, PowerPoint and Excel too.
Policy, prioritized roadmap, procurement rules and the documentation that shows good-faith effort to regulators and courts.
Independent Accessibility Conformance Reports for Section 508, WCAG and EN 301 549, written from real test evidence.
Monthly scans, quarterly manual spot-checks and practical training so new pages and PDFs are born accessible.
Why manual testing
Free scanners are a good start, but they can only check what a machine can measure: missing alt attributes, low contrast, empty links. They cannot tell whether alt text is accurate, whether a checkout can be finished with a keyboard, or whether a screen reader reads a PDF table in the right order.
Those are exactly the barriers plaintiffs' testers find. That's why every xsibility audit and remediation ends with a person completing your key tasks using assistive technology:
How it works
Free snapshot of your highest-risk pages and documents, with a fixed-price scope.
Manual and automated WCAG 2.2 AA testing. Every issue logged with severity, location and fix.
We fix it, or coach your team through it. PDFs are rebuilt and tagged by specialists.
Full retest, conformance report or ACR, and an accessibility statement you can publish.
Who we work with
Cities, counties, transit agencies, school districts, community colleges and public universities facing the ADA Title II deadlines — including years of agendas, minutes, budgets and course materials in PDF.
Hospitals, clinics, health plans and anyone receiving HHS funding under the Section 504 rule: patient portals, forms, billing statements and notices.
Retail, hospitality, banking and insurance — the industries most targeted by ADA Title III website lawsuits in New York, Florida and Illinois.
SaaS and IT vendors that need a credible VPAT/ACR to win government and enterprise deals, or to sell into the EU under the European Accessibility Act.
Lessons from the courtroom
Blind shoppers couldn't buy from Target.com. The case established that a website connected to physical stores is covered by the ADA.
After the Supreme Court declined to hear its appeal, Domino's spent three more years in litigation over a pizza-ordering app.
Rather than caption them after a DOJ finding, Berkeley took its free lectures offline — a cautionary tale about deferred accessibility.
Do it yourself
44 checks, in plain English, that you can run yourself this afternoon.
Step by step: from the source Word file to tags, reading order and a PDF/UA check.
A 30-minute NVDA and VoiceOver routine for people who have never used one.
If you are a state or local government, yes: the DOJ’s ADA Title II rule requires WCAG 2.1 Level AA for web content and documents, with deadlines of April 26, 2027 (populations of 50,000+) and April 26, 2028 (smaller entities). If you are a business open to the public, courts in most US circuits treat websites tied to goods and services as covered by ADA Title III, and the DOJ uses WCAG as its benchmark in settlements. Healthcare organizations funded by HHS have their own Section 504 deadlines starting May 11, 2027.
Regulations in the US cite WCAG 2.1 Level AA. We test and remediate to WCAG 2.2 Level AA, which includes all of 2.1 plus six more A/AA criteria (such as focus not obscured and accessible authentication). Meeting 2.2 satisfies 2.1, and it’s the version most procurement teams now ask for.
No. In April 2025 the FTC finalized a $1 million order against accessiBe and barred it from claiming its overlay makes websites WCAG-compliant. Hundreds of websites using overlays have been sued. Compliance comes from fixing your code, content and documents. See our guide, why accessibility overlays fail.
Pricing depends on page count and complexity: a simple text document costs far less per page than a 200-page report with complex tables, forms and charts. We quote per document after reviewing samples, offer volume pricing for large back-catalogues, and help you decide which files to fix, archive or replace with HTML.
A typical website audit covering 15–30 representative page templates takes two to three weeks, including manual testing with screen readers and a written report. A document audit of a PDF sample can be done in one to two weeks.
Send us a few URLs or sample PDFs. Within two business days you get a free, plain-English snapshot of your biggest accessibility risks and what it takes to fix them.