ADA website compliance

ADA website compliance services that find and fix the barriers on your site

We audit your site against WCAG 2.2 level AA with scans, keyboard testing and screen readers, then repair what fails and write down what was tested.

Ask for a written accessibility scope
Trusted by the world's fastest-growing brands

What the work is

An audit against a named standard, then the repairs

ADA website compliance services test a site for the barriers that stop people who use keyboards, screen readers, captions or zoom from finishing a task, and then repair them. The Department of Justice has no regulation setting detailed technical standards for private business websites, so this work measures against WCAG 2.2 level AA and leaves the legal reading to your attorney.

Sample Northfield Outfitters1.1.1Ridgeline 2P tent$2891.4.32.5.8Add to cart1.1.1Product photo has no alt text

A yardstick you can name

WCAG 2.2 is a W3C Recommendation with numbered success criteria. Each failure in the report carries its criterion number, the page it sits on and a fix, so a developer and an attorney read the same line.

Scans plus hands-on testing

An automated scan makes the first pass over the sampled templates. A tester then goes through the site with a keyboard alone, with NVDA on Windows and VoiceOver on iPhone and Mac, and at 400% zoom.

A dated record

The audit results, the fix log and the accessibility statement carry dates and page counts. Your attorney gets a document of what was tested and repaired, and we leave the legal conclusions to them.

Two ways to approach it

Repairing the site itself or adding an overlay

Both are real practices, and a site can use them together. They differ in where the change is made and who maintains it.

Overlay widgetA script added on top of the existing pagesAudit and repairChanges made in the site’s own code and content
Where the change livesIn a script loaded from the vendor, which acts on the page when a visitor opens itIn the templates, the theme, the stylesheets and the content, in a repository you own
What the visitor seesThe same site plus a menu where visitors choose text size, contrast and similar settingsThe same site, with labels, focus order, contrast and text alternatives repaired
Who does the workThe vendor’s software applies adjustments, and the product is configured onceA tester and a developer, with a list of the failures and the fix for each
The record it leavesA subscription and the vendor’s own reportingAn audit report, a fix log and a statement, all dated
Best whenYou want to add display controls for visitors while the site is repairedYou want the site itself to meet the standard and to hold the evidence
What the FTC said about overlay claims

An overlay can give visitors useful display controls. On its own it has not been shown to make a site conform to WCAG, and the FTC announced a $1 million settlement in January 2025 and finalized the order in April 2025 over accessiBe’s claim that its tool could do that. The Department of Justice’s own guidance says overlays can be helpful tools that need to be used carefully. Both sources are cited below.

The rules, as written

Six facts about the law and the standard

What the statute, the Department of Justice, a court and the FTC have said, each stated as far as its source goes. None of it is legal advice.

  1. Title IIIADA statute

    Title III of the ADA bars disability discrimination in the full and equal enjoyment of the goods and services of public accommodations.

    Section 12181(7) lists the private entities it covers, among them clothing and hardware stores, banks, professional offices and other sales or service establishments. The statute does not mention websites. Whether a given site falls under it is a legal question for your attorney.

  2. DOJ guidanceada.gov, 2022

    The Department of Justice lists six common web barriers and warns that a clean automated report does not necessarily mean everything is accessible.

    The barriers are poor color contrast, color used alone to give information, missing text alternatives, missing captions, inaccessible online forms and mouse-only navigation. The guidance also calls automated checkers and overlays helpful tools that need to be used carefully.

  3. Government sitesTitle II rule

    State and local governments must meet WCAG 2.1 level AA, on dates that an April 2026 interim final rule moved to April 26, 2027 and April 26, 2028.

    The final rule was published April 24, 2024. Governments serving 50,000 or more people now have until April 26, 2027, and smaller governments and special districts until April 26, 2028. The rule covers Title II entities. It is a different rule from Title III, which covers private businesses.

  4. A court’s readingNinth Circuit

    In Robles v. Domino’s, the Ninth Circuit applied the ADA to a pizza chain’s website and app because they connected customers to its physical restaurants.

    The court called that connection critical to its analysis and said an order requiring WCAG 2.0 compliance was a possible equitable remedy. It also held that missing Department of Justice regulations did not remove the statutory duty. The decision is binding in the Ninth Circuit only.

  5. Overlay claimsFTC, 2025

    The FTC alleged that accessiBe’s tool did not make all websites WCAG-compliant, and its order bars that claim unless the company has evidence.

    The Commission announced the $1 million settlement on January 3, 2025 and approved the final order 3-0 on April 22, 2025. The order bars claims that its automated products can make any website WCAG-compliant or keep it compliant over time without evidence to support them.

  6. WCAG 2.2W3C

    WCAG 2.2 adds six success criteria at levels A and AA and retires 4.1.1 Parsing.

    The new ones are Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication (Minimum). W3C says content that conforms to 2.2 also conforms to 2.1 and 2.0, so one audit can answer a contract that names an older version.

What the work includes

Six parts of the work, and what each produces

The written scope names the pages and templates in play. Each part below ends in something you can open.

Audit results by template40 failuresHome page1 page6Category listing1 page5Product page1 page9Cart and checkout3 pages11Sign-in and account2 pages4Returns form1 page3Size guide PDF1 PDF2

WCAG 2.2 AA audit

The audit samples each template your visitors use, such as the home page, a product or service page, the forms and the checkout, runs an automated scan and then tests by hand the success criteria a scan cannot judge. The report lists each failure with its criterion number, a screenshot and the element. You receive: the audit report and the page sample list.

Level AAPage templatesScan plus manual
CheckoutKeyboard onlyEmailyou@example.com1Shipping address12 Pine St, Bend2Card number•••• 42423Place order4Cookie settingsTaskBuy a tentStopped atTab stop 42.4.11 Focus

Keyboard and screen reader testing

A tester completes your main tasks, such as buying, booking or sending a form, using only a keyboard, then again with NVDA on Windows and VoiceOver on iPhone and Mac. Zoom to 400% and text spacing changes are tried too. You receive: the task notes, with the point where each task stopped and the recording.

Remediation planFor approval40 failures in 6 groups17 scan · 23 by handForm labels11Error messages5Keyboard, focus7Text alternatives9Contrast, targets6Untagged PDF2Ordered by what blocks a purchase

Remediation plan

Failures are grouped by cause, because one missing label pattern in a template can account for dozens of lines in the report. The plan orders the groups by what blocks a task first and lists the files each one touches. You receive: the plan, with a count of failures in each group, for you to edit and approve.

Fix checkout labelsRetest passsnippets/address-form.liquid1.3.1, 3.3.2−<input placeholder="Email">+<label for="email">Email</label>+<input id="email" type="email">NVDA reads the fieldBeforeEdit text, blankAfterEmail, edit text

Fixes in your site

Developers repair labels, focus order, contrast, text alternatives, error messages and target sizes in your theme, templates and content, working in a branch of the repository you own. The retest results are listed against the criterion each change addresses. You receive: the pull requests, the retest results and a list of any items left open and why.

Size guide PDFTagged1234DocumentH1 Size guide1P Fit notes2Table3TH Chest, waistFigure alt text4

PDFs and downloads

Menus, size guides, price lists, forms and brochures that people open from your site are tested for tags, reading order, text alternatives and form fields, then repaired or replaced with an accessible page. You receive: the document list with a pass or fail for each file and the repaired versions.

Accessibility statement2 open itemsStandard usedWCAG 2.2, level AATested9 web pages, 1 PDFKnown open itemsCarousel arrow keysReview widget buttonsEditor checklistHeadingsLink textImage alt textVideo captionsLast tested Sep 22, 2026Contact a person

Accessibility statement and new content

A plain-language statement says which standard was used, what was tested, when, what is still open and how to reach a person. For the future, a short checklist for editors covers headings, link text, images and video captions. You receive: the statement, ready to publish, and the editor checklist.

How it runs

Audit, plan, fix, publish

You approve each fix before it goes live.

audit-results.csv

Audit results by template

Sample · Sample Northfield Outfitters online store
TemplatePages testedFailures
Home page16
Category listing15
Product page19
Cart and checkout311
Sign-in and account24
Returns form13
Size guide PDF12
10 pages (9 web pages and 1 PDF) and 40 failures. The scan flagged 17 of them. Keyboard and screen reader testing found the other 23.

Our stack

The tools behind the audit and the fixes

What we test with, build in and read results from. Pick one for the detail.

Lighthouse
Why Lighthouse

Lighthouse is Google’s open-source audit that runs inside Chrome, and its accessibility category reports on a short list of automated checks.

How we use it

It gives a quick read on each template before testing starts, and a high score gets no weight in the report, because the hand testing covers criteria a scan cannot see.

Perf auditCWVIn CI
LighthouseYes
PageSpeedNo
GTmetrixPaid
WebPageTestYes

Questions

ADA website compliance services, answered

Start here

Ask for a written accessibility scope

Tell us what the site runs on and what raised the question. We’ll send back a page sample and a written scope.