← Back to Blog
·11 min read

ADA Website Compliance Checklist for 2025: Every Item You Need to Check

# ADA Website Compliance Checklist for 2025: Every Item You Need to Check


Checklists work. That's why pilots use them before every flight, surgeons use them before every procedure, and smart business owners use them before their websites become litigation targets.

In 2025, over 5,100 federal ADA website accessibility lawsuits were filed — a 37% increase from the year before. Most of those defendants had no idea their website had issues until they received a demand letter.

This checklist helps you spot problems before a plaintiff's attorney does. We've organized it by category and priority level so you know what to fix first.

A quick honest note before you start: this checklist covers the most common and testable WCAG 2.1 AA requirements. No checklist — and no automated tool — can guarantee full legal compliance. A clean scan plus this checklist gets you most of the way there, but complex interactions and edge cases still benefit from human review.

With that said, let's get to work.


How to Use This Checklist

Each item is labeled with:

  • Priority: 🔴 Critical | 🟡 Important | 🟢 Nice-to-Have
  • WCAG Criterion: The specific standard it maps to
  • Type: Technical (code) | Design (visual) | Content (copy) | Legal (documentation)

Start with 🔴 Critical items. These are the most commonly cited violations in lawsuits and the most likely to affect users with disabilities right now.


Section 1: Images and Visual Content

🔴 1.1 — All meaningful images have alt text

  • WCAG: 1.1.1 Non-text Content
  • Type: Technical / Content
  • Every tag should have an alt attribute describing what the image shows
  • Decorative images should have alt="" (empty) so screen readers skip them
  • Bad: | Good: Blue leather wallet, open showing card slots

🔴 1.2 — Complex images have extended descriptions

  • WCAG: 1.1.1 Non-text Content
  • Type: Content
  • Charts, graphs, infographics, and diagrams need text descriptions that convey the same information
  • A caption saying "Figure 1: Sales growth" is not enough — describe the actual data

🟡 1.3 — Images of text are avoided

  • WCAG: 1.4.5 Images of Text
  • Type: Design / Technical
  • Don't use images to display text that could be real HTML text
  • Exception: logos and text that is essential to the message

🟡 1.4 — Video has captions

  • WCAG: 1.2.2 Captions (Prerecorded)
  • Type: Content
  • All pre-recorded video with spoken audio needs synchronized captions
  • Auto-generated captions (YouTube, etc.) must be reviewed for accuracy

🟢 1.5 — Audio-only content has transcripts

  • WCAG: 1.2.1 Audio-only
  • Type: Content
  • Podcasts and audio clips need text transcripts

Section 2: Color and Visual Design

🔴 2.1 — Normal text meets 4.5:1 contrast ratio

  • WCAG: 1.4.3 Contrast (Minimum)
  • Type: Design
  • Small text (below 18pt or 14pt bold) needs at least 4.5:1 contrast against background
  • Test tool: WebAIM Contrast Checker (free)

🔴 2.2 — Large text meets 3:1 contrast ratio

  • WCAG: 1.4.3 Contrast (Minimum)
  • Type: Design
  • Text 18pt+ or 14pt+ bold can use the lower 3:1 threshold

🔴 2.3 — Information is not conveyed by color alone

  • WCAG: 1.4.1 Use of Color
  • Type: Design
  • Required form fields shouldn't only be marked with a red border — also add an asterisk or label
  • Error messages shouldn't only turn text red — add an icon or explicit "Error:" label

🟡 2.4 — Focus indicators are visible

  • WCAG: 2.4.7 Focus Visible
  • Type: Design / Technical
  • When a user navigates with Tab, the focused element must be visually highlighted
  • Many sites override outline: none in CSS — this breaks keyboard navigation entirely

🟡 2.5 — UI components meet 3:1 contrast against background

  • WCAG: 1.4.11 Non-text Contrast (WCAG 2.1)
  • Type: Design
  • Buttons, form fields, checkboxes, and other UI components need 3:1 contrast ratio

Section 3: Keyboard and Navigation

🔴 3.1 — All functionality works with keyboard only

  • WCAG: 2.1.1 Keyboard
  • Type: Technical
  • Every link, button, form field, and interactive element must be reachable with Tab and operable with Enter/Space
  • Test: unplug your mouse and navigate your entire site

🔴 3.2 — No keyboard traps

  • WCAG: 2.1.2 No Keyboard Trap
  • Type: Technical
  • Users must be able to navigate OUT of every component (especially modals and custom widgets) using only the keyboard
  • Modals should close with Escape

🔴 3.3 — Skip navigation link is present

  • WCAG: 2.4.1 Bypass Blocks
  • Type: Technical
  • A "Skip to main content" link should be the first focusable element on every page
  • It can be visually hidden but must appear on focus

🟡 3.4 — Page has a logical tab order

  • WCAG: 1.3.2 Meaningful Sequence / 2.4.3 Focus Order
  • Type: Technical
  • Tab order should follow the visual/reading order of the page
  • Avoid using tabindex values greater than 0 to reorder focus

🟡 3.5 — Dropdown menus are keyboard accessible

  • WCAG: 2.1.1 Keyboard
  • Type: Technical
  • Navigation menus that open on hover should also open on focus/Enter and close on Escape

Section 4: Forms

🔴 4.1 — All form inputs have visible labels

  • WCAG: 1.3.1 Info and Relationships / 3.3.2 Labels or Instructions
  • Type: Technical / Design
  • Every ,