The standard and version that apply depend on the organisation, jurisdiction, contract, and service. The US DOJ Title II web rule names WCAG 2.1 Level AA for covered state and local government content. WCAG 2.2 is the current W3C Recommendation and a useful broader baseline for new work.
Following the DOJ’s April 2026 extension, the general Title II dates are April 26, 2027 for public entities serving 50,000 or more people and April 26, 2028 for smaller entities and special district governments. Those dates should not be presented as a universal private-business deadline.
This guide gives you a practical review sequence. It is not legal advice and does not replace a complete accessibility evaluation.
Quick Print-Ready Checklist (If You Only Have 10 Minutes)
Print this page or use your browser’s Save as PDF function to keep it offline. These checks address common automated findings, but passing them does not mean the complete user experience has been tested.
| # | Check | Tool | Time to fix |
|---|---|---|---|
| 1 | Every meaningful image has descriptive alt text | axe DevTools, WAVE | 1–2 hr |
| 2 | Body text contrast is at least 4.5:1 against background | WebAIM Contrast Checker | 30 min |
| 3 | Every form field has a <label> element programmatically tied via for/id |
View source / axe | 1 hr |
| 4 | All links and buttons have visible text or aria-label (no empty icon-only ones) |
axe DevTools | 1 hr |
| 5 | <html lang="en"> (or your primary language) is set on every page |
View source | 5 min |
| 6 | Visible :focus outline on every interactive element when keyboarding through the page |
Tab through the page | 30 min |
A focused team can knock these out for a 10–25 page site in a single afternoon. If you do nothing else from this checklist, do these six.
One Checklist, Many Search Queries
Searchers arrive here looking for slightly different things - the ADA compliance website checklist, the website ADA compliance checklist, an ADA compliant website checklist, ADA compliance for websites checklist, the ADA web compliance checklist, an ADA website checklist, or more general phrasing like ADA compliance website, ada accessible website requirements, or a generic accessibility compliance checklist. They are all asking the same thing in different words: what does it take to make a website meet ADA Title III, which the courts measure against WCAG 2.1 Level AA?
This guide is structured to answer that question completely. If you came here researching ADA compliant website requirements or the basic requirements for ADA Title III digital accessibility, the 30-step checklist below is the answer, and the FAQ at the bottom covers the legal and procedural questions everyone asks.
Why This ADA Compliance Checklist Matters in 2026
ADA Title III prohibits discrimination against people with disabilities in places of public accommodation. Federal courts have ruled consistently - across the 1st, 2nd, 3rd, 6th, 9th, and 11th Circuits - that commercial websites qualify. The DOJ’s April 2026 Title II rule formalised WCAG 2.1 Level AA as the standard for state and local governments, and plaintiff attorneys now cite that rule directly when arguing private-sector cases.
The practical consequences:
- New York filed 1,021 ADA digital lawsuits in 2025 (33% of all federal filings).
- Florida filed 487 (nearly doubled YoY).
- California filed 380.
- Illinois filed 237 - a 746% YoY increase as plaintiff firms expand into new jurisdictions.
If your business has any US-facing presence, ADA compliance is no longer optional. For the broader context on how ADA and WCAG interact across US and Canadian jurisdictions, see our companion guide on ADA & WCAG compliance for US and Canada in 2026.
The 6 Most Common ADA Website Violations
The WebAIM Million 2025 study analysed the top 1 million US websites. These are the violations they found on the homepage of the average site - and they account for roughly 96% of real-world ADA lawsuits.
- Low contrast text - 79.1% of homepages fail. Fix by checking every text/background pair against 4.5:1 (normal) or 3:1 (large text, 18pt+/14pt+ bold).
- Missing alt text on images - 55.5% fail. Fix by adding descriptive alt to every meaningful image; empty
alt=""only for decorative ones. - Missing form input labels - 48.2% fail. Fix with
<label for="email">Email</label><input id="email" type="email">oraria-label="Email". - Empty links - 44.6% fail. Usually icon links or images-as-links with no accessible name. Add visible text or
aria-label. - Missing document language - 37.1% fail. Fix by setting
<html lang="en">(or your language code) in every page’s HTML. - Empty buttons - 26.3% fail. Icon-only buttons (hamburger, close, search) need
aria-label. Plain<button>with no text content is invisible to screen readers.
These six are the lowest-hanging fruit and the highest-impact fixes. If you have an existing site, run a free website audit to see which of them your site has - and how many of each.
The Full 30-Step ADA Compliance Checklist
This is the complete WCAG 2.1 Level AA checklist, expanded to include the two most-relevant WCAG 2.2 additions (target size and drag alternatives), organised under the four WCAG principles: Perceivable, Operable, Understandable, Robust.
Perceivable - Information must be presentable in ways users can perceive
1. Add alt text to all meaningful images. Every image that conveys information needs a text alternative describing what it shows. Decorative images should have empty alt attributes (alt="") so screen readers skip them.
2. Provide transcripts for audio content. Any podcast, audio interview, or audio-only content needs a full text transcript.
3. Provide captions for all video content. All videos must have closed captions, including live video. Captions must be accurate and synchronised.
4. Provide audio descriptions for video content where necessary. If visual information in a video is not conveyed in the audio track, an audio description track is required.
5. Ensure sufficient colour contrast. Text must have a contrast ratio of at least 4.5:1 against its background (normal text) or 3:1 (large text). Use a contrast checker tool to verify.
6. Do not use colour as the only means of conveying information. Form error states, required fields, and status indicators must use text or iconography in addition to colour, since colour-blind users cannot distinguish red from green.
7. Ensure text can be resized to 200% without losing content or functionality. When a user zooms text to 200%, the page should remain fully usable - no overlapping text, no hidden content.
8. Avoid content that flashes more than 3 times per second. Flashing content can trigger seizures in people with photosensitive epilepsy.
9. Provide text alternatives for non-text content used as controls. Icons used as buttons (search icon, close icon, menu icon) must have accessible names via aria-label or visible text.
Operable - Interface components must be operable
10. Ensure all functionality is accessible by keyboard. Every interactive element - menus, forms, modals, carousels, tabs - must be operable using only a keyboard (Tab, Enter, Space, arrow keys).
11. Provide a visible focus indicator. When a user navigates via keyboard, the focused element must be clearly visible. Removing the default focus outline without providing an equally visible replacement is a common accessibility failure.
12. Provide skip navigation links. Add a “Skip to main content” link at the top of every page, allowing keyboard users and screen reader users to bypass the navigation and jump directly to the page content.
13. Ensure no time limits cause accessibility barriers. If your site has session timeouts or auto-refreshing content, users must be warned and given the option to extend time limits.
14. Provide users control over moving or auto-updating content. Auto-playing carousels, scrolling tickers, and animated banners must have pause, stop, or hide controls.
15. Ensure page titles are descriptive and unique. Every page must have a unique, descriptive <title> element (e.g., “Contact Us | Company Name”) so screen reader users and tab users know where they are.
16. Provide meaningful link text. Links must describe their destination or purpose. “Click here” and “Read more” are inaccessible. Use “Read our ADA compliance guide” or “Download the 2026 pricing PDF” instead.
Understandable - Information and operation of the UI must be understandable
17. Set the language attribute on the HTML element. The lang attribute on your <html> tag tells screen readers what language to use. All pages must have this set correctly (e.g., lang="en").
18. Identify language changes within the page. If a page contains content in multiple languages, use lang attributes on those specific elements.
19. Ensure forms have visible, properly associated labels. Every form input must have a visible label that is programmatically associated (using for/id or aria-labelledby). Placeholder text is not sufficient as a label.
20. Provide helpful error messages for form validation. Error messages must identify the field with the error and explain how to correct it. “This field is required” is acceptable; a red border alone is not.
21. Ensure consistent navigation across pages. Navigation menus that appear on multiple pages must appear in the same location and same order on each page.
Robust - Content must be robust enough to be interpreted by assistive technologies
22. Use valid, semantic HTML. Headings (h1–h6), lists (ul/ol/li), tables (with proper headers), and landmark roles (nav, main, header, footer) allow screen readers to understand and navigate your content structure. This is what searches for “html ada compliance” are really asking about - clean, semantic HTML is the foundation.
23. Ensure ARIA attributes are used correctly. ARIA (Accessible Rich Internet Applications) attributes like aria-label, aria-expanded, and role must be used accurately. Incorrect ARIA can make a site less accessible than no ARIA at all.
24. Ensure all interactive components have accessible names. Buttons, links, form controls, and custom widgets must all have names that describe their purpose, either through visible text or ARIA attributes.
25. Test with real screen readers and assistive technology. Automated tools catch approximately 30–40% of accessibility issues. Real testing with NVDA (Windows), JAWS (Windows), VoiceOver (Mac/iOS), or TalkBack (Android) is essential to find interaction-level issues.
WCAG 2.2 additions - newer criteria worth meeting now
26. Make target sizes at least 24×24 CSS pixels (44×44 is the accessibility gold standard). Tiny buttons and links exclude users with motor impairments.
27. Provide a non-drag alternative for any drag action. If your interface uses drag-and-drop (file uploads, list reordering, kanban boards), supply a keyboard-accessible alternative - usually a click-to-pick-up / click-to-drop pattern.
28. Eliminate horizontal scroll on mobile. Set max-width: 100% on images and tables; use responsive units. Horizontal scroll is one of the most common mobile accessibility failures.
29. Make error states perceivable beyond colour. Form errors must be announced via aria-live, identified with text + icon (not just a red border), and described in plain language.
30. Retest and document the evaluated scope. Record the applicable criterion, test method, original evidence, remediation, retest status, known limitations, and regression control. If procurement requires an Accessibility Conformance Report, use the appropriate VPAT template and disclose support and gaps accurately.
How Much Does ADA Website Compliance Cost?
The cost depends on the number of unique templates, components, documents, third-party integrations, and user journeys. Page count alone is a poor estimate because one shared component may create the same barrier across hundreds of pages.
At eLan Technology:
| Service | Pricing approach |
|---|---|
| Rapid audit and remediation plan | Starts at $1,500 USD |
| Code-level remediation and retesting | Quoted after audit |
| Accessible website redesign or rebuild | Typically $3,000–$12,000 |
| ACR preparation using a VPAT template | Separately scoped to product and standard |
| Ongoing regression testing | Monthly or quarterly plan |
The written scope should name the evaluated surface, testing methods, deliverables, assumptions, exclusions, and retesting process.
Tools for Auditing Your ADA Compliance Checklist
No automated tool is a complete solution - they catch 30–40% of issues. Combine these with manual keyboard testing and at least one screen reader before you ship.
- axe DevTools - browser extension for automated WCAG testing. The de facto standard for engineers.
- WAVE - visual accessibility evaluation tool from WebAIM. Great for non-developers.
- Lighthouse - built into Chrome DevTools, includes an accessibility audit.
- Pa11y - command-line tool for accessibility testing in CI/CD pipelines.
- WebAIM Contrast Checker - fastest way to verify text/background contrast ratios.
- Screen readers - NVDA (free, Windows), JAWS (paid, Windows, market leader for enterprise), VoiceOver (built into macOS/iOS), TalkBack (built into Android).
- Stark - Figma plugin that catches contrast and accessibility issues during design, before code is written.
For a deeper explanation of how these tools fit into a real audit workflow, see our WCAG 2.2 guide for business owners.
What to Do If Your Website Fails This Checklist
If you have not received a demand letter, work through these steps in order:
- Define representative templates and critical user journeys.
- Run automated and manual testing and rank findings by user impact.
- Schedule remaining medium and low-priority fixes across the next 1–2 sprints.
- Retest the original barriers and record the result.
- Publish an accurate accessibility statement and add regression controls.
If you have received a demand letter or complaint, send it to qualified legal counsel. In parallel, preserve the current technical evidence and follow our emergency ADA website remediation guide. Our emergency remediation service provides scoped technical assessment, source-level remediation, and retesting.
For planned work, our ADA and WCAG accessibility service covers audit, remediation, retesting, and documentation.
Frequently Asked Questions
What is an ADA website compliance checklist? A checklist translates WCAG requirements into practical review steps. It helps identify common barriers and organise remediation, but it does not replace a complete conformance evaluation.
What is required for a website to be ADA compliant in 2026? The answer depends on the organisation and jurisdiction. Use the version and level named by the applicable obligation, and treat WCAG Level AA as the practical engineering baseline.
Is there a free ADA compliance kit or checklist I can download? Use your browser’s Print or Save as PDF function for an offline copy of this checklist.
Does an accessibility widget make my site ADA compliant? An overlay cannot establish WCAG conformance by itself. Many barriers must be fixed in the source and verified manually.
How much does ADA website compliance cost? Our rapid audit and remediation plan starts at $1,500 USD. Full remediation is quoted after the evaluated surface and repeated issue types are understood.
For more questions on scope, current DOJ dates, audit methods, and documentation, see the FAQ section on our ADA and WCAG service page.
Accessibility Pays - Beyond Compliance
Compliance is the floor, not the ceiling. Accessible websites also deliver:
- Better SEO - semantic HTML, alt text, and descriptive link text help search engines crawl and rank your content
- Larger addressable audience - approximately 1 in 4 US adults lives with a disability
- Better mobile usability - accessibility patterns (large targets, clear focus, keyboard-equivalent paths) make every interaction faster
- Stronger brand reputation - accessibility statements and visible commitments build trust
- Lower support costs - accessible forms have higher completion rates and fewer error tickets
The web should work for everyone. This 30-step ADA compliance checklist is your starting point. The next step is doing the work - or requesting an audit so you have a prioritised plan to do it from.