Is ADA compliance legally required for websites?

For state and local government (Title II), yes: the DOJ's April 2024 rule requires WCAG 2.1 AA. For private businesses (Title III), the ADA has no codified web standard, but US courts have consistently held that websites of public accommodations must be accessible, and WCAG 2.1 AA is the standard applied.

What WCAG level do I need for ADA compliance?

Level AA. Level A is insufficient; Level AAA is not required.

What is the ADA compliance deadline?

Title II: 24 April 2026 (population ≥50,000) and 26 April 2027 (smaller). Title III has no deadline, obligations are already active and enforced through litigation.

How much does ADA compliance cost?

Cost depends on site size and current state of accessibility. Use our accessibility cost calculator for an estimate specific to your site.

Can an automated tool or accessibility widget make my site ADA compliant on its own?

No tool does all of it, ours included. Of the 55 criteria on this page, 20 are at least partly automatable; the remaining 35 need human judgement, including keyboard operability, whether alt text is meaningful, and logical heading structure. Automate what is safe to automate, put people on the rest, and keep a report you can show.

What happens if my website is not ADA compliant?

Demand letters and lawsuits. Federal courts see thousands of website accessibility suits filed every year, and plaintiffs’ firms actively monitor sites for violations.

How do I test my website for ADA compliance?

Automated scan for machine-detectable issues, then a manual keyboard and screen-reader pass.

Does the ADA apply to mobile apps?

Yes; the DOJ Title II rule explicitly covers mobile apps.

Do PDFs need to be ADA compliant?

Yes. Use our PDF accessibility checker to test a document.

What is a VPAT and do I need one?

A VPAT (Voluntary Product Accessibility Template) is a standardized document format for reporting how a product conforms to accessibility standards like WCAG, Section 508, or EN 301 549, criterion by criterion. You need one if you sell to government agencies or enterprise buyers with procurement teams, since VPATs are commonly requested during vendor evaluation.

What's the difference between ADA, Section 508, and WCAG?

ADA is civil-rights law; Section 508 applies to federal agencies; WCAG is the technical standard both rely on.

ADA Compliance Checklist for Websites (2026)

What is ADA compliance for websites?

ADA compliance for websites means your site is usable by people with disabilities. The Americans with Disabilities Act (1990) predates the web and sets no technical standard of its own, so what counts is the standard courts and the DOJ actually apply. That standard is WCAG. For the full picture, see our ADA compliance hub.

Which rules apply to your site?

Comparison of ADA Title II and Title III requirements
Requirement	Title II	Title III
Who	State & local government, public schools, public universities, transit	Private businesses open to the public, such as retail, restaurants, banks, healthcare, ecommerce
Standard	WCAG 2.1 AA (DOJ final rule, April 2024, legally binding)	WCAG 2.1 AA (applied by courts; no codified rule)
Deadline	24 Apr 2026 (population ≥50,000) 26 Apr 2027 (<50,000 & special districts)	No deadline, enforced through litigation
Enforcement	DOJ	Private lawsuits & demand letters
Start here	ADA Title II Compliance Checker	This checklist

Comparison of ADA Title II and Title III requirements
Title II	Title III
Who
State & local government, public schools, public universities, transit	Private businesses open to the public, such as retail, restaurants, banks, healthcare, ecommerce
Standard
WCAG 2.1 AA (DOJ final rule, April 2024, legally binding)	WCAG 2.1 AA (applied by courts; no codified rule)
Deadline
24 Apr 2026 (≥50,000) 26 Apr 2027 (<50,000)	No deadline, enforced through litigation
Enforcement
DOJ	Private lawsuits & demand letters
Start here
ADA Title II Compliance Checker	This checklist

State and local government entities

The first Title II deadline has already passed. Use the Title II checker for a deadline-specific assessment.

Self-assessment

Interactive ADA Compliance Checklist

Use this Comprehensive ADA Compliance Checklist against all 55 WCAG 2.2 Level A/AA criteria, the current W3C standard, backwards-compatible with the WCAG 2.1 AA benchmark the DOJ's April 2024 Title II rule requires. Check off completed items to track your progress and identify areas needing attention.

0%

0 of 55

criteria
complete

You've completed 0 of 55. Of the 55 remaining, 35 need manual remediation, that's the part teams underestimate.

Showing 55 of 55

Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

0/20

1.1.1 · Every meaningful image has alternative text

Why it matters

Screen readers cannot interpret images. Without alt text a blind user hears the filename, or nothing. We find it on roughly a third of the sites we scan.

How to fix

Decorative images get an empty alt attribute; meaningful images describe the content, not the appearance.

How to test

Disable images in the browser. If the page loses information, that image needs alt text. Tools detect missing alt; only a human can judge whether it is meaningful.

Reference

WCAG 1.1.1 - W3C Understanding doc

<img src="q3.png" alt="">                          <!-- decorative: hidden -->
<img src="q3.png" alt="Q3 revenue rose 24% to $1.2M"> <!-- meaningful -->

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this Generate alt text free

1.2.1 · Audio-only and video-only content has a text alternative

Why it matters

A podcast excludes deaf users; a silent product video excludes blind users. Each needs an equivalent in another form.

How to fix

Publish a transcript for audio-only content. For video-only content, provide a transcript or an audio description track.

How to test

List every audio-only and video-only asset. Confirm each has a linked text alternative adjacent to it.

Reference

WCAG 1.2.1 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

1.2.2 · Pre-recorded video has captions

Why it matters

Deaf and hard-of-hearing users cannot access spoken content. Captions also help the majority who watch muted.

How to fix

Upload a .vtt caption file. Never rely on auto-captions alone, because they misrender names, numbers and technical terms.

How to test

Play each video with sound off. Are captions accurate, synchronised, and do they identify speakers?

Reference

WCAG 1.2.2 - W3C Understanding doc

<video controls>
  <source src="demo.mp4" type="video/mp4">
  <track kind="captions" src="demo.vtt" srclang="en" label="English" default>
</video>

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

1.2.3 · Pre-recorded video has audio description or a media alternative

Why it matters

Blind users miss information shown only visually, such as on-screen text, charts and demonstrated actions.

How to fix

Add an audio description track, or publish a full descriptive transcript covering visual content.

How to test

Listen to each video without watching. Is anything essential missing?

Reference

WCAG 1.2.3 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

1.2.4 · Live video has captions

Why it matters

Live webinars and streams are inaccessible to deaf users without real-time captions.

How to fix

Use a live captioning service (CART) or a platform with real-time captioning.

How to test

Attend a live broadcast and confirm captions appear with acceptable latency and accuracy.

Reference

WCAG 1.2.4 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

1.2.5 · Pre-recorded video has audio description

Why it matters

The AA-level requirement: visual-only information must be narrated, not merely transcribed elsewhere.

How to fix

Produce an audio-described version, or design videos to narrate what is shown ("as you can see here, the score is 94").

How to test

Audio-only playback should convey everything a sighted viewer receives.

Reference

WCAG 1.2.5 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

1.3.1 · Structure is conveyed in code, not just visually

Why it matters

A screen reader user navigates by headings, lists and landmarks. Text that merely looks like a heading is just text to them.

How to fix

Use real semantic elements: <ul>/<ol> for lists, <table> with <th> for data, and landmarks (<main>, <nav>, <header>).

How to test

Inspect the heading outline (browser extension or screen-reader heading list). Does it match the visual structure?

Reference

WCAG 1.3.1 - W3C Understanding doc

<div class="h2-style">Pricing</div>   <!-- ❌ looks like a heading -->
<h2>Pricing</h2>                       <!-- ✅ is a heading -->

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

1.3.2 · Reading order makes sense

Why it matters

CSS can reorder content visually while the underlying DOM order stays illogical, producing nonsense for screen readers.

How to fix

Keep DOM order matching the intended reading order; avoid large order/flex-direction: row-reverse reorderings that break sequence.

How to test

Disable CSS. Does the content still read in a sensible order?

Reference

WCAG 1.3.2 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

1.3.3 · Instructions don't rely on shape, size or position alone

Why it matters

"Click the round button on the right" is meaningless to a screen reader user.

How to fix

Reference elements by their accessible name: "Select Continue".

How to test

Search copy for "above", "below", "left", "right", "the red button".

Reference

WCAG 1.3.3 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

1.3.4 · Content works in both portrait and landscape

Why it matters

Users with mounted wheelchairs or fixed devices cannot rotate their screen.

How to fix

Never lock orientation unless essential (e.g. a piano app). Remove orientation locks from CSS and manifests.

How to test

Rotate a phone or tablet on every key page.

Reference

WCAG 1.3.4 - W3C Understanding doc

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

1.3.5 · Common input fields declare their purpose

Why it matters

Autofill and personalised symbol support depend on machine-readable field purpose, which is critical for users with cognitive and motor disabilities.

How to fix

Add autocomplete tokens.

How to test

Inspect every field collecting personal data for a valid autocomplete token.

Reference

WCAG 1.3.5 - W3C Understanding doc

<input type="email" name="email" autocomplete="email">
<input type="tel"   name="phone" autocomplete="tel">

We fix this automatically

Our widget applies the fix at runtime, so there is nothing for your developer to ship.

Fix this automatically

1.4.1 · Colour is not the only way information is conveyed

Why it matters

Colour-blind users cannot distinguish a red "error" field from a green "valid" one if colour is the only difference.

How to fix

Pair colour with text, an icon, or underline. Errors get a message; links in body text get an underline.

How to test

View the page in greyscale. Is any meaning lost?

Reference

WCAG 1.4.1 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help Test for colour-blind safety

1.4.2 · Audio that plays automatically can be stopped

Why it matters

Auto-playing audio masks a screen reader's speech, making the page unusable.

How to fix

Don't autoplay. If you must, keep it under 3 seconds or provide an immediate, keyboard-reachable pause/stop control.

How to test

Load the page. Does anything play? Can you stop it without a mouse?

Reference

WCAG 1.4.2 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

1.4.3 · Text has sufficient colour contrast

Why it matters

Low contrast excludes users with low vision, colour blindness, and anyone on a phone in sunlight. It is the most frequently detected failure in automated scans.

How to fix

Normal text needs 4.5:1 against its background. Large text (18pt / 14pt bold) needs 3:1.

How to test

Use our colour contrast checker. Check hover, focus, visited, and disabled states, which are the states teams forget.

Reference

WCAG 1.4.3 - W3C Understanding doc

/* ❌ 2.8:1 fails */
.muted { color: #9CA3AF; background: #fff; }

/* ✅ 4.6:1 passes AA */
.muted { color: #6B7280; background: #fff; }

We fix this automatically

Our widget applies the fix at runtime, so there is nothing for your developer to ship.

Fix this automatically Check your contrast free

1.4.4 · Text can be resized to 200% without loss

Why it matters

Low-vision users routinely zoom. Fixed-height containers clip text at larger sizes.

How to fix

Use relative units (rem, em) and avoid fixed height on text containers. Never set user-scalable=no.

How to test

Zoom the browser to 200%. Is any text cut off, overlapped or hidden?

Reference

WCAG 1.4.4 - W3C Understanding doc

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

1.4.5 · Real text is used instead of images of text

Why it matters

Text baked into an image cannot be resized, recoloured, translated or read aloud.

How to fix

Use HTML text with CSS. Reserve images of text for logos and cases where presentation is essential.

How to test

Select text with the cursor. If it can't be selected, it's an image.

Reference

WCAG 1.4.5 - W3C Understanding doc

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

1.4.10 · Content reflows to a single column without horizontal scrolling

Why it matters

At 400% zoom, users must not have to scroll in two directions to read a sentence.

How to fix

Responsive layout; no fixed-width containers; avoid white-space: nowrap on long content. Target 320px equivalent width.

How to test

Set the browser to 1280px and zoom to 400% (≈320px viewport). Is there horizontal scrolling?

Reference

WCAG 1.4.10 - W3C Understanding doc

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

1.4.11 · UI components and graphics have 3:1 contrast

Why it matters

A form border, toggle or focus ring that's too faint is invisible to low-vision users, even when the label is legible.

How to fix

Ensure input borders, icons, chart segments and focus indicators reach 3:1 against adjacent colours.

How to test

Sample the border/icon colour against its background in a contrast tool.

Reference

WCAG 1.4.11 - W3C Understanding doc

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this Check your contrast free

1.4.12 · Text remains readable with increased spacing

Why it matters

Users with dyslexia often apply custom spacing stylesheets; rigid layouts break and clip.

How to fix

Avoid fixed heights on text blocks; allow content to grow. Support line-height 1.5×, paragraph spacing 2×, letter 0.12em, word 0.16em.

How to test

Apply a text-spacing bookmarklet. Does anything overlap or truncate?

Reference

WCAG 1.4.12 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

1.4.13 · Hover/focus content is dismissible, hoverable and persistent

Why it matters

Tooltips that vanish when the pointer moves are unusable for magnifier users; ones that can't be dismissed obscure content.

How to fix

Dismiss with Esc, allow the pointer to move onto the tooltip, and keep it visible until dismissed or focus moves.

How to test

Hover a tooltip, move the mouse onto it (should stay), press Esc (should close).

Reference

WCAG 1.4.13 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

13 of these 20 need human judgement, including whether your alt text is actually meaningful.

See how our experts handle Perceivable

Operable

User interface components and navigation must be operable.

0/20

2.1.1 · All functionality works with a keyboard

Why it matters

Users with motor disabilities, screen reader users, and many power users navigate entirely by keyboard. Mouse-only controls exclude them completely. This requires source changes at build time, which is what our MCP produces.

How to fix

Use native elements (<button>, <a>) instead of click-handled <div>s.

How to test

Unplug the mouse. Tab through the page. Can you reach and operate everything?

Reference

WCAG 2.1.1 - W3C Understanding doc

<div class="btn" onclick="submit()">Submit</div> <!-- ❌ not focusable -->
<button type="submit">Submit</button>            <!-- ✅ -->

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.1.2 · Keyboard focus is never trapped

Why it matters

If focus enters a modal or embed and can't leave, the keyboard user is stuck and must reload.

How to fix

In modals, cycle focus within the dialog and close on Esc, returning focus to the trigger.

How to test

Tab into every modal, widget and iframe. Can you always tab back out?

Reference

WCAG 2.1.2 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.1.4 · Single-character shortcuts can be turned off or remapped

Why it matters

Speech-input users trigger single-key shortcuts accidentally while dictating.

How to fix

Require a modifier (Ctrl/Alt), or let users disable or remap shortcuts.

How to test

Press single letters on the page. Does anything activate unexpectedly?

Reference

WCAG 2.1.4 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.2.1 · Time limits can be adjusted

Why it matters

Users with cognitive or motor disabilities need more time; a silent session timeout can destroy their work.

How to fix

Warn before expiry and offer at least 20 seconds to extend, with the option to extend at least ten times.

How to test

Trigger a session or form timeout. Is there a warning and an extend option?

Reference

WCAG 2.2.1 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.2.2 · Moving content can be paused

Why it matters

Carousels, tickers and animation distract users with attention or cognitive disabilities and can move faster than a screen reader can read.

How to fix

Provide a visible pause/stop control for anything moving over 5 seconds. Respect prefers-reduced-motion.

How to test

Find every auto-advancing element. Can it be paused with the keyboard?

Reference

WCAG 2.2.2 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.3.1 · Nothing flashes more than three times per second

Why it matters

Flashing can trigger seizures. This is a safety requirement, not a convenience.

How to fix

Remove rapid flashing; keep any flash under 3Hz.

How to test

Review animations, video and ads for rapid flashing.

Reference

WCAG 2.3.1 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.4.1 · A skip link bypasses repeated navigation

Why it matters

Without it, keyboard users tab through dozens of nav links on every page.

How to fix

The link may be visually hidden but must become visible on focus.

How to test

Load the page and press Tab once. Does a visible skip link appear and work?

Reference

WCAG 2.4.1 - W3C Understanding doc

<a class="skip" href="#main">Skip to main content</a>
...
<main id="main" tabindex="-1">…</main>

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

2.4.2 · Every page has a descriptive, unique title

Why it matters

The title is the first thing announced and how users distinguish tabs.

How to fix

Page topic | Site name. Unique on every URL.

How to test

Crawl for duplicate or missing <title>.

Reference

WCAG 2.4.2 - W3C Understanding doc

We fix this automatically

Our widget applies the fix at runtime, so there is nothing for your developer to ship.

Fix this automatically

2.4.3 · Focus order is logical

Why it matters

Focus jumping around the page is disorienting and can hide content entirely.

How to fix

Match DOM order to visual order; avoid positive tabindex values (tabindex="5").

How to test

Tab through the page and watch the focus ring. Does it move predictably?

Reference

WCAG 2.4.3 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.4.4 · Link purpose is clear

Why it matters

Screen reader users often browse a list of links out of context. Twenty links reading "Read more" are useless.

How to fix

Keep visible text short and extend it accessibly for screen readers.

How to test

Pull the page's link list. Does each make sense alone?

Reference

WCAG 2.4.4 - W3C Understanding doc

<a href="/ada">Read more<span class="sr-only"> about ADA compliance</span></a>

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

2.4.5 · There is more than one way to find a page

Why it matters

Users navigate differently; some browse menus, others search or use a sitemap.

How to fix

Provide at least two of: navigation menu, search, sitemap, breadcrumbs.

How to test

Can a page be reached both by menu and by search/sitemap?

Reference

WCAG 2.4.5 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.4.6 · Headings and labels are descriptive

Why it matters

Users skim by headings. "Overview" or "More" tells them nothing.

How to fix

Write specific headings; label fields by what they collect, not their format.

How to test

Read only the headings. Do they summarise the page?

Reference

WCAG 2.4.6 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.4.7 · Keyboard focus is always visible

Why it matters

Removing the focus ring makes keyboard navigation impossible because you can't see where you are. Extremely common and easily avoided.

How to fix

Never remove the default outline without replacing it with a visible focus-visible style.

How to test

Tab through every page. Is the focused element always obvious?

Reference

WCAG 2.4.7 - W3C Understanding doc

*:focus { outline: none; }              /* ❌ never do this alone */
:focus-visible { outline: 3px solid #0052CC; outline-offset: 2px; } /* ✅ */

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

2.4.11 · Focused elements are not hidden

Why it matters

Sticky headers, cookie banners and chat widgets often cover the focused control. New in WCAG 2.2.

How to fix

Add scroll-margin equal to sticky header height.

How to test

Tab through a page with a sticky header. Does focus ever disappear behind it?

Reference

WCAG 2.4.11 - W3C Understanding doc

:target, :focus-visible { scroll-margin-top: 6rem; }

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.5.1 · Multipoint and path-based gestures have a simple alternative

Why it matters

Pinch, swipe-path and two-finger gestures are impossible for users with tremors or a single switch.

How to fix

Every gesture needs a single-pointer alternative, such as buttons alongside a swipe carousel, or +/− beside pinch-zoom.

How to test

Operate the page with one finger and single taps only.

Reference

WCAG 2.5.1 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.5.2 · Actions complete on release, not press

Why it matters

Users with tremors need to slide off a control to cancel an accidental press.

How to fix

Trigger on click/pointerup, not pointerdown, or provide undo.

How to test

Press a control, move away, release. It should not activate.

Reference

WCAG 2.5.2 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.5.3 · Visible label text matches the accessible name

Why it matters

Speech users say "click Submit". If the button's visible text is "Submit" but its aria-label is "Send form", the command fails.

How to fix

Ensure aria-label contains (ideally starts with) the visible text, or omit it and let the visible text be the name.

How to test

Compare each control's visible text with its accessible name in devtools.

Reference

WCAG 2.5.3 - W3C Understanding doc

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

2.5.4 · Motion-triggered functions have a button alternative

Why it matters

Shake-to-undo excludes users who cannot move the device, and misfires for users with tremors.

How to fix

Provide an equivalent control and allow motion actuation to be disabled.

How to test

Can every motion-triggered feature be performed by a control?

Reference

WCAG 2.5.4 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.5.7 · Dragging has a single-pointer alternative

Why it matters

Drag-and-drop reorderers, sliders and kanban boards are unusable without fine motor control. New in WCAG 2.2.

How to fix

Add click-based alternatives: "move up / move down" buttons, or a numeric input beside a slider.

How to test

Complete every drag interaction using only clicks or taps.

Reference

WCAG 2.5.7 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

2.5.8 · Touch targets are at least 24×24 CSS pixels

Why it matters

Small targets are unusable for users with tremors or large fingers. New in WCAG 2.2.

How to fix

Minimum 24×24px, or adequate spacing between smaller targets. 44×44px is the better practical target.

How to test

Measure icon buttons, close "×" controls, and inline links in dense lists.

Reference

WCAG 2.5.8 - W3C Understanding doc

.icon-btn { min-width: 24px; min-height: 24px; }

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

Keyboard access requires source-level changes. Our MCP generates framework-aware fixes your developer commits; our experts handle the rest.

Get a keyboard accessibility audit

Understandable

Information and the operation of the user interface must be understandable.

0/13

3.1.1 · The page declares its language

Why it matters

Without it, screen readers may read English with a French voice, which is often unintelligible.

How to fix

Set the lang attribute.

How to test

View source and check the lang attribute on every template.

Reference

WCAG 3.1.1 - W3C Understanding doc

<html lang="en">

We fix this automatically

Our widget applies the fix at runtime, so there is nothing for your developer to ship.

Fix this automatically

3.1.2 · Passages in another language are marked

Why it matters

Mixed-language content is mispronounced without markup.

How to fix

Wrap foreign phrases with a lang attribute.

How to test

Find foreign-language phrases and confirm each has a lang attribute.

Reference

WCAG 3.1.2 - W3C Understanding doc

<span lang="fr">joie de vivre</span>

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

3.2.1 · Focus alone doesn't cause a change of context

Why it matters

If tabbing into a field submits a form or opens a dialog, keyboard users lose control of the page.

How to fix

Never trigger navigation, submission or popups on focus.

How to test

Tab through all controls without pressing Enter. Does anything change unexpectedly?

Reference

WCAG 3.2.1 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

3.2.2 · Changing a setting doesn't auto-submit

Why it matters

A <select> that navigates on change traps keyboard users, who pass through every option while choosing.

How to fix

Require an explicit "Apply"/"Go" button, or warn in advance.

How to test

Change every dropdown, radio and checkbox with the keyboard. Does anything submit or navigate?

Reference

WCAG 3.2.2 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

3.2.3 · Navigation is consistent across pages

Why it matters

Users who navigate by memory or magnification rely on stable placement and order.

How to fix

Keep nav order and location consistent sitewide.

How to test

Compare the header/footer across templates.

Reference

WCAG 3.2.3 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

3.2.4 · Identical components are named consistently

Why it matters

Calling the same action "Search" here and "Find" there forces users to relearn each page.

How to fix

Standardise labels, icons and alt text for repeated components.

How to test

Audit repeated buttons and icons for naming drift.

Reference

WCAG 3.2.4 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

3.2.6 · Help is in a consistent place

Why it matters

Users with cognitive disabilities need help where they expect it. New in WCAG 2.2.

How to fix

Keep contact/help links in the same relative position on every page.

How to test

Check that the help link stays put across templates.

Reference

WCAG 3.2.6 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

3.3.1 · Errors are identified in text

Why it matters

A red border alone is invisible to screen reader and colour-blind users; they can't tell what failed.

How to fix

Associate an error message with the field.

How to test

Submit a form with errors using a screen reader. Is each error announced and identified?

Reference

WCAG 3.3.1 - W3C Understanding doc

<input id="email" aria-describedby="email-err" aria-invalid="true">
<p id="email-err" role="alert">Enter a valid email address, e.g. [email protected]</p>

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

3.3.2 · Every input has a visible label

Why it matters

Placeholder-only fields lose their label on typing and are poorly announced. A very common failure.

How to fix

Use a real label element.

How to test

Click each label; focus should move to its field. Scan for inputs without an associated <label>.

Reference

WCAG 3.3.2 - W3C Understanding doc

<input placeholder="Email">                 <!-- ❌ -->
<label for="email">Email</label>            <!-- ✅ -->
<input id="email" type="email">

We fix this automatically

Our widget applies the fix at runtime, so there is nothing for your developer to ship.

Fix this automatically

3.3.3 · Error messages suggest a correction

Why it matters

"Invalid input" tells the user nothing about how to proceed.

How to fix

Say what's wrong and how to fix it: "Date must be in DD/MM/YYYY format."

How to test

Trigger each validation error. Does the message explain the fix?

Reference

WCAG 3.3.3 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

3.3.4 · Legal, financial and data submissions are reversible or confirmed

Why it matters

Users who make input errors need a way to catch them before a binding commitment.

How to fix

Provide a review step, a confirmation, or the ability to reverse.

How to test

Walk through checkout, booking and account-deletion flows for a review or undo step.

Reference

WCAG 3.3.4 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

3.3.7 · Users don't have to re-enter the same information

Why it matters

Re-typing an address in a multi-step form burdens users with cognitive and motor disabilities. New in WCAG 2.2.

How to fix

Auto-populate previously entered data, or offer a "same as billing" checkbox.

How to test

Complete a multi-step form. Are you asked for anything twice?

Reference

WCAG 3.3.7 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

3.3.8 · Login doesn't require a cognitive test

Why it matters

Puzzle CAPTCHAs and "remember your password" tests exclude users with cognitive disabilities. New in WCAG 2.2.

How to fix

Allow password managers to paste and autofill, support email links or passkeys, and avoid puzzle-based CAPTCHA as the only route.

How to test

Attempt login using a password manager and paste. Is either blocked?

Reference

WCAG 3.3.8 - W3C Understanding doc

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

Error messages and form labels are where most lawsuits start.

Get your forms reviewed

Robust

Content must be robust enough to work with current and future assistive technology.

0/2

4.1.2 · Custom components expose name, role and value

Why it matters

A <div> styled as a toggle is announced as nothing. Screen reader users can't tell what it is or whether it's on.

How to fix

Prefer native elements. For custom widgets, supply role, accessible name and state.

How to test

Inspect each custom component in the accessibility tree. Does it report a sensible role, name and state?

Reference

WCAG 4.1.2 - W3C Understanding doc

<div class="toggle" onclick="…">Dark mode</div>                  <!-- ❌ -->
<button role="switch" aria-checked="false">Dark mode</button>     <!-- ✅ -->

We find every instance, our experts confirm the fix

Our scanner flags all occurrences. A machine can't judge whether the result is meaningful, so a certified specialist reviews it.

Scan my site for this

4.1.3 · Status messages are announced without moving focus

Why it matters

"3 results found" or "Saved" appearing silently leaves screen reader users unaware anything happened.

How to fix

Use role="alert" for errors requiring immediate attention.

How to test

Trigger search results, form success and cart updates with a screen reader running. Is each announced?

Reference

WCAG 4.1.3 - W3C Understanding doc

<div role="status" aria-live="polite">Your changes were saved.</div>

This one needs human judgement

No scanner can verify this criterion. A certified specialist tests it manually and documents the result for your file.

Get expert help

Custom components are the most common screen-reader failure.

Get your components audited

Automation Limits

What automated tools can and cannot fix

Can be automated

Colour contrast detection
Missing alt attributes
Missing form labels
Missing page language
ARIA syntax errors

Needs human judgement

Whether alt text is meaningful
Logical heading hierarchy
Keyboard operability of custom widgets
Screen-reader announcement quality
Whether error messages are helpful

Automated testing reliably detects roughly 30–40% of WCAG issues. Of the 55 criteria on this page, only 5 are fully automatable and 15 partially, 36% in total. No tool, including ours, can find them all. Any vendor claiming 100% automated compliance is overstating what is technically possible. WebAbility combines automated fixes with IAAP-certified expert remediation for this reason.

Benchmark data

The 10 failures we find most often

We scanned 1,777 websites with the WebAbility scanner between June 2025 and August 2026. These were the most common WCAG Level A and AA failures, with the share of sites affected by each.

WCAG 1.4.3
0% of sites affected
Text contrast below 4.5:1
WCAG 2.4.7
0% of sites affected
No visible keyboard focus indicator
WCAG 1.3.1
0% of sites affected
Structure not conveyed in markup
WCAG 4.1.2
0% of sites affected
Custom controls missing name, role or value
WCAG 1.1.1
0% of sites affected
Images missing alt text
WCAG 2.1.1
0% of sites affected
Functionality not reachable by keyboard
WCAG 2.4.4
0% of sites affected
Empty or ambiguous link text
WCAG 1.4.11
0% of sites affected
UI component contrast below 3:1
WCAG 1.3.2
0% of sites affected
Reading order does not match visual order
WCAG 2.4.6
0% of sites affected
Unhelpful headings or labels

Methodology

1,777 sites, June 2025 to August 2026, automated + manual verification. Cite as: WebAbility, "State of ADA Compliance 2026."

Standards Covered

Standards This Checklist Covers

Every one of these laws points back to the same technical standard: WCAG 2.1/2.2 AA. Meet this checklist and you satisfy ADA, Section 508, EAA, AODA, and EN 301 549 at once.

Frequently asked questions

Everything you need to know about ADA compliance

Keep going

Free tools, compliance guides and reference material for working through what this checklist flagged.