ADA Website Compliance Checklist 2026
The April 2026 federal ADA deadline applies to state and local government sites, but private business enforcement is accelerating too. Use this checklist to identify and fix the violations most likely to appear in a lawsuit.
The ADA does not include a government-issued website compliance checklist. What it includes is a legal obligation not to discriminate against people with disabilities, and courts have consistently applied that obligation to websites. WCAG 2.2 Level AA is the de facto technical standard used by courts and regulators to evaluate compliance.
This checklist covers the violations that appear most often in audits, demand letters, and litigation.
Why 2026 Matters
On April 24, 2024, the DOJ published a final rule under ADA Title II requiring state and local government websites to conform to WCAG 2.1 Level AA. The compliance deadline for most government entities is April 24, 2026.
Private businesses are not covered by this specific rule, but the DOJ's move signals broader regulatory intent. Plaintiffs' attorneys have already begun using the new rule as a reference point in Title III cases. For any website owner, now is the right time to run this checklist.
Section 1: Page Fundamentals
1.1 Page Language Declared
Every HTML page must have alang attribute on the element. Screen readers use this to select the correct pronunciation engine.
Check: View source on your homepage. Does (or the appropriate language code) appear?
Fix: Add lang="en" to your tag in your template or layout file.
1.2 Page Title Present
Every page must have a descriptive in the . The title is the first thing screen readers announce when a user lands on a page.
Check: Does each page have a unique, descriptive title that identifies the page content and site name?
Fix: Update your CMS templates to include page-specific titles. Avoid generic titles like "Home" or "Page 1."
1.3 Viewport Meta Tag
The viewport meta tag enables responsive design. Without it, mobile browsers zoom out, making content inaccessible to low-vision users who rely on mobile zoom. Check: Every page should include.
Fix: Add to your HTML . Do not use user-scalable=no, which prevents users from zooming.
Section 2: Images and Media
2.1 All Images Have Alt Text (WCAG 1.1.1)
Every![]()
element must have an alt attribute. Decorative images get alt="". Informative images get descriptive alt text. Images that are links must describe the link destination.
Check: Use your browser's developer tools to inspect every image. Look for alt="" on decorative images and meaningful descriptions on informative ones.
What fails: Images with no alt attribute at all, or alt="image" or alt="photo123.jpg".
2.2 Video Captions (WCAG 1.2.2)
Pre-recorded video with audio must have synchronized captions. Live video must have real-time captions. Check: Play any embedded videos. Are captions available and accurate? What fails: Auto-generated captions that have not been reviewed, or video embedded from YouTube with captions disabled.Section 3: Forms
3.1 All Form Inputs Are Labeled (WCAG 1.3.1, 4.1.2)
Every, , and must be associated with a visible element using the for/id pairing, or use aria-label / aria-labelledby.
Check: Click on each form label. Does the cursor jump to the corresponding field? Tab through the form with a keyboard. Does your screen reader announce the field name?
What fails: Placeholder text used instead of a label (placeholders disappear when typing), or icon-only inputs with no accessible name.
3.2 Error Messages Are Descriptive (WCAG 3.3.1, 3.3.3)
When a form submission fails, the error must be identified in text and explained. Generic messages like "Invalid input" do not pass. Check: Submit your forms with intentional errors. Does the page clearly identify which field failed and why? Is the error programmatically associated with the field?Section 4: Navigation and Keyboard Access
4.1 Skip Navigation Link (WCAG 2.4.1)
A "Skip to main content" link must appear at the top of the page so keyboard users can bypass the navigation menu on every page load. Check: Press Tab on any page. Is the first focusable element a "Skip to main content" link? Fix: AddSkip to main content before your navigation, and add id="main-content" to your main content wrapper.
4.2 Full Keyboard Accessibility (WCAG 2.1.1)
Every interactive element must be operable by keyboard alone: links, buttons, dropdowns, modals, tabs, carousels, and custom widgets. Check: Tab through your entire site without using a mouse. Can you reach and activate every interactive element? Can you close modals and escape dropdowns with the Escape key? What fails: Click-only event handlers on elements, dropdown menus that only open on hover, and modal dialogs that trap keyboard focus.
4.3 Focus Is Always Visible (WCAG 2.4.7, 2.4.11)
The keyboard focus indicator must be visible at all times. WCAG 2.2 added criterion 2.4.11 (Focus Not Obscured), requiring that focused elements are not entirely hidden by sticky headers or other overlapping content.
Check: Tab through your page. Can you see which element is focused at all times? Is the focus ring visible against the background?
What fails: CSS rules like outline: none or outline: 0 applied globally without a replacement focus style.
Section 5: Color and Visual Presentation
5.1 Color Contrast for Text (WCAG 1.4.3)
Normal text (under 18pt regular or 14pt bold) must have a contrast ratio of at least 4.5:1 against its background. Large text requires at least 3:1.
Check: Use a browser extension like Colour Contrast Analyser or check in Chrome DevTools Accessibility panel.
Common failures: Light gray text on white backgrounds, white text on light-colored buttons, placeholder text in form fields.
5.2 Information Not Conveyed by Color Alone (WCAG 1.4.1)
If your UI uses color to communicate meaning (red = error, green = success), that meaning must also be conveyed through text, icons, or patterns.
Check: View your page in grayscale. Is all the information still understandable?
Section 6: Content Structure
6.1 Heading Hierarchy Is Logical (WCAG 1.3.1)
Pages should have one that describes the page topic. Subheadings use , sub-subheadings use , and so on. Headings must not skip levels (e.g., to ).
Check: Use a browser extension or the OnePageAudit scanner to view your heading structure. Is there exactly one ? Do heading levels flow in order without skipping?
6.2 Links Are Descriptive (WCAG 2.4.4)
Link text must describe the link destination when read in isolation. Screen reader users frequently navigate by jumping between links. "Click here" and "read more" provide no context.
Check: Read your link text out of context. Does it tell you where the link goes?
What fails: "Click here," "learn more," empty anchor tags , and image links with no alt text.
Running This Checklist
Manual checking takes time. An automated scanner catches the items with clear pass/fail rules: missing alt text, missing labels, missing page language, empty links, missing skip navigation, missing page title, and heading structure.
Run a free automated scan on OnePageAudit to identify your site's current violations in under 60 seconds. The scan maps each issue to the specific WCAG criterion and tells you how to fix it.
After fixing automated findings, complete the manual steps above, particularly keyboard navigation and screen reader testing.
Related reading:
Frequently Asked Questions
Is there a government-published ADA website compliance checklist?⌄
The DOJ does not publish a step-by-step website checklist, but its April 2024 final rule references WCAG 2.1 AA as the technical standard for government websites under Title II. The W3C's own WCAG Quick Reference (wcag.com/quick-reference) provides an authoritative breakdown of all criteria. For most businesses, the practical checklist is: fix missing alt text, add form labels, ensure keyboard navigation works, verify color contrast, and declare page language.Does this checklist apply to private businesses or only government websites?⌄
The April 2026 deadline specifically targets state and local government websites under ADA Title II. Private businesses fall under Title III, which has no single compliance deadline but is actively enforced through lawsuits. Courts use WCAG 2.1 or 2.2 AA as the practical standard for Title III cases, so this checklist applies to both sectors.How long does it take to fix ADA compliance issues?⌄
Simple fixes like adding alt text and declaring page language can be done in hours. Structural issues like keyboard navigation failures or missing heading hierarchy may take days or weeks depending on your CMS or framework. The best approach is to scan first, categorize by severity, and fix critical violations first since those are most likely to appear in demand letters.What happens if my website fails an ADA audit?⌄
For government entities, failure after the April 2026 deadline can result in DOJ enforcement, civil penalties up to $75,000 for a first violation, and injunctive relief. For private businesses, the most common consequence is a demand letter followed by a lawsuit seeking injunctive relief, attorney fees, and settlement payments. Most private-sector ADA website cases settle in the $5,000 to $75,000 range according to data from Accessible.org.Related Resources
Scan your website free
Find ADA compliance issues in under 60 seconds. No account required.
Run Free Scan