Free ADA Website Compliance Checker
Is your website ADA compliant? Enter a URL to test it against the WCAG 2.2 Level A and AA rules that software can check. Results arrive in seconds, with no signup. Then use the checklist below for the parts that need a person.
Free, no signup. Built on the open-source axe-core engine. See how CompliaScan tests websites.
What Makes a Website ADA Compliant?
An ADA compliant website is one that people with disabilities can use as fully as anyone else. A blind visitor using a screen reader, someone who cannot use a mouse, and someone with low vision can all find the information, fill in the forms, and finish a purchase or booking. No agency certifies websites as ADA compliant, and no badge or certificate proves it. In practice, compliance is measured against the Web Content Accessibility Guidelines (WCAG) 2.1 or 2.2 at Level AA.
Which rule applies depends on who runs the site:
| Who runs the site | What applies | Technical standard | When |
|---|---|---|---|
| Businesses open to the public (ADA Title III): stores, restaurants, hotels, medical offices, banks and similar | The ADA's general duty of equal access. The DOJ's March 2022 guidance says it covers goods and services offered online. | None set by regulation. The DOJ calls WCAG “helpful guidance”; demand letters and settlements usually measure against WCAG 2.0 or 2.1 Level AA. | Applies now |
| State and local governments serving 50,000 or more people (ADA Title II) | The DOJ's 2024 web and mobile app rule | WCAG 2.1 Level AA | April 26, 2027 |
| Smaller governments and special districts (ADA Title II) | The DOJ's 2024 web and mobile app rule | WCAG 2.1 Level AA | April 26, 2028 |
Businesses: Title III and the DOJ's 2022 guidance
The ADA's original text does not mention websites. In its March 2022 web guidance (opens in new tab), the Department of Justice says the ADA applies to the goods and services businesses offer online. It sets no single technical standard: businesses “have flexibility in how they comply,” and WCAG and the Section 508 Standards “provide helpful guidance.”
Many courts have held that business websites are covered, either on their own or because they connect to a physical location. Courts disagree about businesses that exist only online. Most ADA website lawsuits are brought under Title III, against online stores, restaurants, booking sites and healthcare portals among others.
Governments: the Title II rule
In April 2024, the DOJ finalized a rule requiring the websites and mobile apps of state and local governments to meet WCAG 2.1 Level AA. An April 2026 interim final rule (opens in new tab) moved the dates: April 26, 2027 for governments serving 50,000 or more people, and April 26, 2028 for smaller governments and special districts.
That covers city portals, public universities, county courts and transit agencies. Failure to comply can lead to DOJ enforcement, complaints, and private lawsuits.
Either way, WCAG Level AA is the yardstick. The rest of this page explains what that means, lists the requirements, and shows how to check and fix your own site. For the full legal background and a compliance plan, read the ADA website compliance guide.
What WCAG 2.1 and 2.2 Level AA Mean in Practice
WCAG is a W3C standard made of testable success criteria, grouped under four principles. Each criterion has a level: A (the minimum), AA, or AAA. “Level AA” means a page meets every Level A and Level AA criterion. The W3C does not recommend requiring AAA for entire sites, because some content cannot meet it.
Perceivable
People can take in the content in some form: text alternatives for images, captions for video, enough color contrast.
Operable
Everything works from a keyboard, focus is visible, and nothing moves or times out before people can use it.
Understandable
Labels, instructions and error messages are clear, and pages behave in predictable ways.
Robust
The code works with assistive technology, so a screen reader gets the right name, role and state for every control.
WCAG 2.1 Level AA has 50 success criteria (30 at Level A and 20 at Level AA). It is the version the Title II rule names.
WCAG 2.2, published in October 2023, adds nine criteria, six of them at Level A or AA: focus not hidden behind sticky content, no dragging-only controls, 24 by 24 pixel targets, consistent help, no retyping of information already given, and sign-in without memory or puzzle tests. It also removes the obsolete 4.1.1 Parsing. That makes 55 criteria at Level AA (31 at A and 24 at AA). WCAG 2.2 is also an international standard, ISO/IEC 40500:2025.
The WCAG 2.2 Recommendation (opens in new tab) states that content conforming to 2.2 also conforms to 2.1 and 2.0, and the W3C recommends 2.2 as the target even where an obligation names an older version. That is why CompliaScan tests against WCAG 2.2 Level A and AA. For what changed in each new criterion, see WCAG 2.2 explained.
ADA Website Compliance Checklist: What to Check and How
These are the WCAG 2.2 Level A and AA requirements that most often decide whether a site is usable, grouped by area. The DOJ's 2022 guidance names several of them as common barriers: poor color contrast, color used alone to give information, missing alt text, videos without captions, inaccessible forms, and mouse-only navigation. The last column says whether a scan can find the problem, whether it needs a person, or both. Percentages are the share of the top million home pages with that failure in the WebAIM Million 2026 (opens in new tab) report.
Images, video and audio
| Requirement | WCAG | How to check |
|---|---|---|
| Informative images have alt text that says what they show or do; decorative images have empty alt | 1.1.1 | Scan, then by hand. A scan finds missing alt text (on 53.1% of home pages). Only a person can judge whether the text is accurate. |
| Prerecorded video with speech has accurate captions | 1.2.2 | By hand. Play each video with captions on and compare them with the audio. |
| Video whose visuals carry meaning has audio description or a text alternative | 1.2.3, 1.2.5 | By hand. Ask whether someone who cannot see the video would miss information. |
| Audio that plays on its own for more than 3 seconds can be paused or muted | 1.4.2 | By hand. Load the page with sound on and listen. |
Color, text and layout
| Requirement | WCAG | How to check |
|---|---|---|
| Text has a contrast ratio of at least 4.5:1 (3:1 for large text) | 1.4.3 | Scan, then by hand. Low contrast text is the most common failure, found on 83.9% of home pages. Check text placed over images by hand. |
| Color is not the only way information is shown, such as required fields, errors or links inside text | 1.4.1 | By hand. View the page in grayscale and note anything you can no longer tell apart. |
| Icons, form field borders and focus indicators have at least 3:1 contrast | 1.4.11 | By hand. Measure each control's colors, including hover and focus states, with a contrast checker. |
| Text zooms to 200%, and content reflows at 320 CSS pixels wide without sideways scrolling | 1.4.4, 1.4.10 | By hand. Zoom to 200%, then to 400% in a 1280-pixel-wide window, which equals 320 CSS pixels. |
Keyboard and focus
| Requirement | WCAG | How to check |
|---|---|---|
| Every link, button, menu and form control works with the keyboard alone | 2.1.1 | By hand. Tab through the page and operate each control with Enter, Space and the arrow keys. |
| Keyboard focus never gets stuck in a dialog, video player, chat widget or embed | 2.1.2 | By hand. Tab into and back out of every widget on the page. |
| The focused element is always visible and not hidden behind sticky headers or cookie banners | 2.4.7, 2.4.11 | By hand. Watch the focus indicator as you Tab, especially near fixed bars. |
| A skip link, headings or landmarks let people bypass repeated navigation | 2.4.1 | Scan, then by hand. A scan flags pages with no way to bypass repeated blocks. Press Tab once after the page loads to confirm a skip link works. |
Forms and sign-in
| Requirement | WCAG | How to check |
|---|---|---|
| Every form field has a label or instructions that assistive technology can read | 1.3.1, 3.3.2, 4.1.2 | Scan. A scan finds fields with no accessible label. Missing labels show up on 51% of home pages. |
| Errors are described in text, with a suggestion for fixing them | 3.3.1, 3.3.3 | By hand. Submit each form with mistakes and read the messages. |
| Sign-in does not require a memory or puzzle test unless there is an alternative, such as allowing paste or a password manager | 3.3.8 | By hand. Try signing in with a password manager and with pasted text. |
| Information already entered in a process is filled in or offered again, not retyped | 3.3.7 | By hand. Walk through checkout or sign-up and note any repeated questions. |
Structure, links and buttons
| Requirement | WCAG | How to check |
|---|---|---|
| Each page has a descriptive title and declares its language | 2.4.2, 3.1.1 | Scan, then by hand. A missing page language shows up on 13.5% of home pages. Read the titles to check they describe each page. |
| Headings, lists and tables use real markup, in a logical order | 1.3.1, 2.4.6 | Scan, then by hand. A scan catches some structure errors. Review the heading outline to see that it makes sense. |
| Links and buttons have text that says what they do | 2.4.4, 4.1.2 | Scan, then by hand. A scan finds empty links (46.3% of home pages) and empty buttons (30.6%). Judge vague text like “click here” by hand. |
| Navigation and help options appear in the same order on every page | 3.2.3, 3.2.6 | By hand. Compare the header, footer and help links across a few page types. |
| Touch targets are at least 24 by 24 CSS pixels, or have enough space around them | 2.5.8 | Scan, then by hand. A scan flags small, crowded targets. Try the icon buttons on a phone. |
Screen readers and moving content
| Requirement | WCAG | How to check |
|---|---|---|
| Custom controls such as menus, tabs, dialogs and carousels expose a name, role and state | 4.1.2 | Scan, then by hand. A scan catches many ARIA errors. A screen reader shows whether the control actually works. |
| Status messages such as “added to cart” are announced without moving focus | 4.1.3 | By hand. Trigger each message with a screen reader running. |
| Moving or auto-updating content can be paused, and nothing flashes more than three times a second | 2.2.2, 2.3.1 | By hand. Look for carousels, tickers and animations without a pause control. |
Measure colors with the free color contrast checker, and track every Level A and AA criterion, not just these, in the interactive WCAG 2.2 checklist. Beyond WCAG, the DOJ's guidance notes that websites which give the public a way to report accessibility problems let their owners fix them. An accessibility statement with a contact method does that, and the free accessibility statement generator writes one for you.
How to Check if Your Website Is ADA Compliant
A useful check combines an automated scan with a short round of manual testing on the pages that matter most. You do not need paid software.
- Pick the pages that matter. Your home page, a main product or service page, your contact or booking form, and the checkout or sign-up flow. Problems there stop customers from doing business with you.
- Run an automated scan on each one. Use the free ADA compliance checker at the top of this page. Fix what it reports first: missing alt text, low contrast, unlabeled fields and empty buttons are among the most common failures on the web, and most are quick to fix.
- Put the mouse away. Press Tab and Shift+Tab through each page, use Enter and Space on buttons, Escape to close dialogs, and the arrow keys in menus. You should always see where focus is and never get stuck.
- Listen with a screen reader. NVDA is free for Windows; VoiceOver is built into Mac and iPhone; TalkBack is built into Android. Check that the page title, headings, image descriptions, field labels and button names make sense when read aloud.
- Zoom and shrink. Zoom the browser to 200%, then narrow the window to phone width. Nothing should overlap, get cut off, or need sideways scrolling.
- Check media and documents. Turn on captions for each video, and open the PDFs your key pages link to. PDFs need their own accessibility checks.
The self-check below turns steps 3 to 6 into ten pass-or-fail tests. For a full audit method with severity ratings, follow the step-by-step guide to checking website accessibility.
Is My Website ADA Compliant? A 10-Point Self-Check
No certificate or official test makes a website ADA compliant. What you can measure is how close it is to WCAG 2.2 Level AA. The free scan above catches the machine-detectable problems. These ten checks cover common issues a scan cannot fully confirm, and each takes a few minutes by hand.
- 1
Meaningful alt text (SC 1.1.1)
Informative images describe what they show or do, and decorative images use an empty alt; a scanner can see that alt text exists but not whether it is useful.
- 2
Keyboard-only use (SC 2.1.1)
You can reach and operate every link, button, menu, and form field with the keyboard alone.
- 3
Visible focus (SC 2.4.7)
As you press Tab, you can always see which element has focus.
- 4
No keyboard traps (SC 2.1.2)
Focus never gets stuck inside a dialog, video player, chat widget, or embedded form.
- 5
Captions on prerecorded video (SC 1.2.2)
Every video with speech has accurate captions, not auto-generated ones nobody has checked.
- 6
200% zoom and reflow (SC 1.4.4, 1.4.10)
Text enlarges to 200% and the page reflows on a narrow screen without cutting off content or forcing sideways scrolling.
- 7
Errors and labels in text (SC 3.3.1, 3.3.2)
Form fields have labels or instructions, and errors are described in words rather than only with a red border.
- 8
Consistent navigation and help (SC 3.2.3, 3.2.6)
Menus and help options such as contact details, chat, or an FAQ link appear in the same order on every page.
- 9
24px targets (SC 2.5.8)
Buttons and links are at least 24 by 24 CSS pixels, or have enough space around them that they are hard to miss.
- 10
Status messages announced (SC 4.1.3)
Messages such as "added to cart" or "form submitted" are announced to screen readers without moving focus.
Use our WCAG checklist to record results for every Level A and AA criterion as you go.
What an ADA Compliance Checker Can and Cannot Find
Automated checkers test page code against rules with clear pass or fail answers. They are fast and repeatable, and they find the most common failures. They cannot judge meaning or experience. The DOJ's web guidance (opens in new tab) puts it plainly:
A “clean” report does not necessarily mean everything is accessible.
A scan can find
- Images with no alt text
- Text with too little color contrast
- Form fields with no label
- Empty links and empty buttons
- A missing page title or page language
- Invalid or misused ARIA attributes
- Pages with no way to skip repeated navigation
- Touch targets smaller than 24 by 24 pixels
A person has to check
- Whether alt text describes the image accurately
- Whether custom menus, sliders and dialogs work from the keyboard
- Focus order and whether focus stays visible
- Caption accuracy and audio description
- Whether error messages and instructions make sense
- Whether a screen reader user can finish a task, such as checkout
How much does a scan catch?
It depends on how you count. Counted by barrier type, a large share needs a person. In a 2017 test by the UK Government Digital Service (opens in new tab), 10 automated tools were run against a page with 143 deliberate barriers. The best single tool flagged 37% of them through errors and warnings, and 42 barriers (29%) were missed by every tool.
Counted by volume, the share is higher, because common problems like low contrast and missing labels repeat across many pages. Deque, which makes axe-core, analyzed first-time audits (opens in new tab) covering more than 13,000 pages and found that its automated tests identified 57% of the nearly 300,000 issues.
Either way, a scan is the first step, not the last. CompliaScan is built on axe-core, the open-source engine from Deque Systems, and tests against WCAG 2.2 Level A and AA. It adds a small number of checks of its own, flagged with confidence levels so you can tell them apart. Read how CompliaScan tests and scores websites for the details.
How to Fix Issues and Keep Your Website ADA Compliant
- Fix blockers on key tasks first. Anything that stops someone from finding your contact details, filling in a form, or checking out comes before cosmetic issues.
- Fix templates before pages. A missing label in your site header or theme repeats on every page, so one fix in the template clears it everywhere.
- Fix content at the source. Show whoever edits the site how to write alt text, use real headings, and caption videos, so new pages do not add new issues.
- Be careful with overlay widgets. A toolbar script does not change the code underneath. The DOJ's guidance says automated checkers and overlays “need to be used carefully.” See whether accessibility overlays work.
- Re-test after every change. Theme updates, new plugins and redesigns are where fixed issues come back. Scheduled monitoring re-scans for you and flags regressions.
- Keep records and a way to report problems. A dated log of tests and fixes documents your effort if a demand letter arrives. Publish an accessibility statement that tells visitors how to report a barrier.
Need outside help? Compare what audits, remediation and monitoring include and cost in our guide to ADA website compliance services.
ADA Website Lawsuits Rebounded in 2025
Businesses of every size are sued over inaccessible websites. Federal filings rose 27% in 2025 after two years of decline. See the full ADA website lawsuit statistics.
3,117
Federal website accessibility lawsuits in 2025
Seyfarth Shaw counted 3,117 website accessibility lawsuits filed in federal court in 2025, up 27% from 2,452 in 2024. More are filed in New York and California state courts.
36%
Share of federal ADA Title III suits
Website cases made up 36% of the ADA Title III lawsuits filed in federal court in 2025 (3,117 of 8,667), according to Seyfarth Shaw.
95.9%
Home pages with detectable WCAG failures
In WebAIM's February 2026 scan of the top million home pages, 95.9% had automatically detected WCAG failures, with an average of 56.1 errors per page.
Sources: Seyfarth Shaw, ADA Title III blog (2026) (opens in new tab); WebAIM Million (2026) (opens in new tab).
Related Resources
ADA Compliance Guide
In-depth guide to ADA website compliance requirements, legal obligations, and how to build an accessible site from the ground up.
ADA Website Compliance Services
What audits, remediation and monitoring services include, what they cost, and how to choose one.
How CompliaScan Tests
The rules we run, how scores are calculated, and what automated testing can and cannot tell you.
Section 508 Compliance Checker
Selling to government? Test your site against Section 508, the accessibility standard for U.S. federal agencies and their vendors.
WCAG Checker
Scan your site against WCAG 2.2 Level A and AA success criteria, the technical standard that ADA, EAA, and Section 508 work is measured against.
All Features
Explore everything CompliaScan offers: automated scanning, fix suggestions, monitoring, PDF reports, and team dashboards.
View Pricing
Free tier available. Upgrade to Starter for full reports, AI recommendations, and scheduled monitoring starting at $69/mo.
On Shopify? Shopify accessibility checker
Scan your Shopify storefront for WCAG issues and get fixes tailored to Shopify themes and product pages.
On WordPress? WordPress accessibility checker
Check your WordPress theme and plugins for accessibility gaps that show up across every post and page.
On Wix? Wix accessibility checker
Test your Wix site against WCAG 2.2 and see which issues you can fix directly in the Wix editor.
On Squarespace? Squarespace accessibility checker
Scan your Squarespace site for accessibility issues and fix them in your template settings.
On Webflow? Webflow accessibility checker
Check your Webflow project's accessibility before launch and fix issues in the Designer.
Frequently Asked Questions
Is my website ADA compliant?
What makes a website ADA compliant?
Is my website legally required to be ADA compliant?
How do I check if my website is ADA compliant?
Is there an official ADA compliance test or certificate for websites?
If an ADA compliance checker finds no errors, is my website accessible?
Which WCAG version should my website meet: 2.1 or 2.2?
Does passing this scan make me lawsuit-proof?
How often should I check my website for ADA compliance?
How do I fix the issues it finds?
Is the free scan really free?
Check Your Website for ADA Compliance Now
Do not wait for a demand letter. Run a free scan to see where your site stands against WCAG 2.2 Level AA, the practical benchmark for ADA website accessibility. Results in seconds, no signup required.