Skip to content
ADA Website Compliance Checklist for 2026

ADA Website Compliance Checklist for 2026

4 min read

What Is ADA Website Compliance?

The Americans with Disabilities Act (ADA) requires that businesses open to the public provide equal access to their goods and services, including digital services. While the ADA was originally written for physical spaces, courts and the Department of Justice have consistently interpreted it to cover websites and mobile apps.

In 2026, the DOJ formally references WCAG 2.2 Level AA as the technical standard for web accessibility compliance. Failing to meet this standard puts your organization at risk of lawsuits, demand letters, and regulatory action.

The Complete Checklist

Perceivable Content

  • All images have alt text — Every meaningful image includes a descriptive alt attribute. Decorative images use alt="" to be ignored by screen readers.
  • Videos have captions — All pre-recorded video content includes synchronized captions. Live video provides real-time captioning.
  • Audio has transcripts — Podcast episodes and audio content are accompanied by text transcripts.
  • Color contrast meets standards — Text meets a 4.5:1 contrast ratio for normal text and 3:1 for large text against its background. Use the wcagkit contrast checker to verify.
  • Information is not conveyed by color alone — Error states, required fields, and status indicators use text labels or icons in addition to color.
  • Content reflows on zoom — Users can zoom to 200% without horizontal scrolling or content overlap.

Operable Interface

  • Full keyboard navigation — Every interactive element is reachable and operable via keyboard alone, including menus, modals, tabs, and form controls.
  • Visible focus indicators — A clearly visible outline or highlight appears on the focused element when navigating with a keyboard.
  • Skip navigation link — A “Skip to main content” link appears as the first focusable element on every page.
  • No keyboard traps — Users can always tab away from any component. Modal dialogs allow closing with the Escape key.
  • Motion control — Animations can be paused or disabled. The site respects the prefers-reduced-motion media query.
  • Sufficient time limits — If a session expires, users are warned and given the option to extend it.

Understandable Content

  • Language is declared — The <html> element includes a lang attribute (e.g., lang="en").
  • Form errors are clear — Error messages identify which field has the problem and explain how to fix it.
  • Labels are associated — Every form input has a programmatically associated <label>.
  • Navigation is consistent — Menus and navigation links appear in the same order across pages.
  • Abbreviations are explained — Uncommon abbreviations and acronyms are expanded on first use.

Robust Markup

  • Valid HTML — Pages use properly nested, standards-compliant HTML without duplicate IDs.
  • ARIA is used correctly — ARIA roles, states, and properties follow the WAI-ARIA specification. Avoid unnecessary ARIA when native HTML elements suffice. Use the ARIA Validator to check.
  • Headings follow hierarchy — Pages have a single H1 and headings do not skip levels. Test with the Heading Analyzer.
  • Links have descriptive text — Avoid “click here” or “read more” as link text. Each link describes its destination. Run the Link Checker to find violations.

High-Risk Areas

Certain types of content attract the most accessibility lawsuits:

E-Commerce

Product images without alt text, inaccessible shopping carts, and checkout flows that cannot be completed with a keyboard are the most commonly cited issues in retail accessibility cases.

PDF Documents

PDFs are often overlooked in accessibility audits. Ensure all published PDFs are tagged with a logical reading order, have alt text for images, and are not simply scanned images of text.

Third-Party Widgets

Embedded chat widgets, social media feeds, payment forms, and analytics pop-ups from third parties may introduce accessibility barriers. You are responsible for the accessibility of everything on your page, including third-party code.

Single-Page Applications

JavaScript-heavy SPAs must announce route changes to screen readers, manage focus after navigation, and ensure dynamically loaded content is accessible. Use ARIA live regions to communicate updates.

What Happens If You Are Not Compliant

ADA website accessibility lawsuits have increased steadily, with thousands filed each year in the United States. Settlements typically range from $5,000 to $150,000 or more, and often include ongoing monitoring requirements.

Beyond lawsuits, inaccessible websites exclude potential customers, damage brand reputation, and often perform poorly in search engine rankings since many accessibility best practices overlap with SEO fundamentals.

Getting Started

The most effective approach is to audit your current site, prioritize the most impactful fixes, and integrate accessibility testing into your ongoing development process.

Start with the automated checks. Run your site through wcagkit’s free tools to catch color contrast failures, heading hierarchy issues, missing alt text, and broken ARIA attributes. Then follow up with manual keyboard and screen reader testing to catch what automation misses.

Accessibility is an ongoing practice, not a one-time checkbox. Build it into every sprint, every design review, and every deploy.