2026-05-17 · 6 min read

ADA Compliance Checklist for Government Websites: What WCAG 2.1 AA Actually Covers

# ADA Compliance Checklist for Government Websites: What WCAG 2.1 AA Actually Covers

Government IT directors searching for an "ADA compliance checklist" are usually looking for the same thing: a list they can work through that tells them whether their website is compliant. The challenge is that WCAG 2.1 Level AA — the specific technical standard the DOJ Title II Final Rule requires — has 50 success criteria organized across four principles, and not all of them are checkable with a simple yes/no.

This post explains what a comprehensive government website ADA compliance checklist covers, how to use a checklist effectively as a pre-audit assessment tool, and what a checklist cannot do that only a full audit can accomplish.

What the DOJ Title II Rule Actually Requires

Title II of the ADA has prohibited discrimination against people with disabilities in government programs and services since 1990. The March 2024 Final Rule establishes specific technical standards for web content and mobile apps: WCAG 2.1 Level AA. The compliance deadline for jurisdictions with populations of 50,000 or more is April 26, 2027.

WCAG 2.1 Level AA means:

• All 25 Level A success criteria (the baseline)
• All 25 Level AA success criteria (the extended standard)
• 50 criteria total

The Four Principles of WCAG 2.1

Perceivable (13 criteria at A and AA)

Content must be presentable to users in ways they can perceive. The key criteria:

• 1.1.1 Non-text Content (A): All images, icons, and non-text elements have text alternatives
• 1.2.2 Captions — Prerecorded (A): All prerecorded video has synchronized captions
• 1.2.4 Captions — Live (AA): All live video has captions
• 1.2.5 Audio Description — Prerecorded (AA): All video has audio descriptions for visual-only information
• 1.3.1 Info and Relationships (A): Structure and relationships (headings, labels, lists) are programmatically determinable
• 1.3.2 Meaningful Sequence (A): Reading order makes sense when CSS is removed
• 1.3.3 Sensory Characteristics (A): Instructions don't rely solely on shape, color, size, or position
• 1.3.4 Orientation (AA): Content doesn't restrict to a single display orientation
• 1.3.5 Identify Input Purpose (AA): Input fields collecting personal information use autocomplete attributes
• 1.4.1 Use of Color (A): Color is not the only means of conveying information
• 1.4.3 Contrast — Minimum (AA): Text has 4.5:1 contrast ratio (3:1 for large text)
• 1.4.4 Resize Text (AA): Text can be resized to 200% without loss of content
• 1.4.10 Reflow (AA): Content reflows to single column at 320px without horizontal scrolling
• 1.4.11 Non-text Contrast (AA): UI components and graphical objects have 3:1 contrast ratio

Operable (18 criteria at A and AA)

All functionality must be operable by users who cannot use a mouse. The key criteria:

• 2.1.1 Keyboard (A): All functionality is operable via keyboard
• 2.1.2 No Keyboard Trap (A): Keyboard focus can always be moved away from any component
• 2.4.1 Bypass Blocks (A): Skip navigation links or other mechanism to bypass repeated content
• 2.4.2 Page Titled (A): Every page has a descriptive title
• 2.4.3 Focus Order (A): Focus moves in a logical order that preserves meaning
• 2.4.4 Link Purpose in Context (A): Link text describes the destination or can be determined from context
• 2.4.7 Focus Visible (AA): Keyboard focus indicator is always visible
• 2.5.1 Pointer Gestures (A): Multi-point or path-based gestures have single-pointer alternatives
• 2.5.3 Label in Name (A): Accessible names contain the visible text labels

Understandable (13 criteria at A and AA)

Content and operation must be understandable. The key criteria:

• 3.1.1 Language of Page (A): Default human language of the page is programmatically identified
• 3.1.2 Language of Parts (AA): Language changes within the page are identified
• 3.2.1 On Focus (A): Focus doesn't trigger context changes automatically
• 3.2.2 On Input (A): Changing a form control doesn't automatically change context
• 3.3.1 Error Identification (A): Input errors are identified in text
• 3.3.2 Labels or Instructions (A): Labels or instructions are provided for user input
• 3.3.3 Error Suggestion (AA): Suggestions for correcting input errors are provided
• 3.3.4 Error Prevention — Legal and Financial (AA): Submissions are reversible, verifiable, or confirmable

Robust (6 criteria at A and AA)

Content must be compatible with current and future assistive technology. The key criteria:

• 4.1.1 Parsing (A): HTML is well-formed and valid
• 4.1.2 Name, Role, Value (A): All UI components have programmatically determinable name, role, and state
• 4.1.3 Status Messages (AA): Status messages are programmatically determinable without receiving focus

How to Use a Checklist as a Pre-Audit Self-Assessment

A compliance checklist used before a professional audit serves two purposes: it helps you identify obvious failures quickly, and it helps you understand the scope of what a professional audit will review.

What a checklist can reliably assess:

• Page titles (2.4.2): check the browser tab on each page type
• Language attribute (3.1.1): view source and check for <html lang="en">
• Color contrast (1.4.3): use the browser's DevTools or a contrast checker
• Alt text presence (1.1.1): right-click inspect any image to check the alt attribute
• Form labels (3.3.2): inspect any form input to see if a label is associated
• Skip navigation (2.4.1): Tab once from the URL bar and see what gets focus
• Focus visibility (2.4.7): Tab through the page and observe the focus indicator
• Reflow (1.4.10): zoom to 400% and check for horizontal scrolling

What a checklist cannot reliably assess:

• Screen reader output (does "Submit Application" announce correctly with context?)
• Keyboard trap detection (can you navigate in AND out of all widgets?)
• Focus order logic (does Tab order match reading order on complex pages?)
• Error message quality (do error messages identify the field and suggest corrections?)
• Caption accuracy (are the captions correct or just auto-generated approximations?)
• ARIA implementation correctness (do custom widgets behave as they claim?)

These require assistive technology testing — specifically NVDA and VoiceOver in their actual operating environments. No checklist can substitute for this.

The Interactive 47-Point Checklist

The free WCAG 2.1 AA Compliance Checklist from Morton Technology Consulting covers 47 of the 50 WCAG 2.1 Level AA success criteria in an interactive, browser-based format with:

• Live progress tracking as you mark items
• Grouped by principle and criterion category
• Notes field for each criterion
• Print-friendly layout for documentation
• Export to CSV for remediation tracking

It is available at no cost and requires no email or registration to use. If you want to track your assessment results and receive guidance on what to prioritize, you can optionally enter your email to receive a follow-up analysis.

From Checklist to Compliance

A checklist self-assessment tells you where the obvious failures are. It does not tell you about the screen reader failures, keyboard trap failures, and ARIA implementation errors that automated tools and visual inspection miss — which account for approximately 43% of WCAG failures.

A professional WCAG audit covers the full 50 criteria with both automated tools and manual testing with NVDA and VoiceOver. The Parallax WCAG audit from Morton Technology Consulting is designed specifically for Florida government agencies facing the April 2027 deadline — 200 representative pages, full manual testing, findings report by criterion, remediation roadmap, and accessibility statement draft.

---

*Morton Technology Consulting LLC, Tallahassee, FL. ADA website compliance audits for Florida government agencies. [email protected]*

Morton Technology Consulting LLC — WCAG 2.1 AA audits for Florida government agencies. Parallax audit → · WCAG Readiness Kit → · All posts →