WCAG 2.1 AAChecklistADA Title IIGovernment
WCAG 2.1 AA Checklist for Government Websites (2026)
March 2026 · 12 min read
WCAG 2.1 Level AA includes 50 success criteria across 4 principles: Perceivable, Operable, Understandable, and Robust. The DOJ's ADA Title II final rule requires all state and local government websites to meet these standards by April 24, 2026 (large entities) or April 26, 2027 (smaller entities). This checklist translates each criterion into plain language, specifically for government website contexts.
How to use this checklist
Level A criteria are the baseline — all must pass. Level AA criteria are required under the DOJ rule. Each criterion is marked with its WCAG ID so your team can reference the full specification at w3.org/WAI/WCAG21. Automated scans like CertusAudit catch roughly 40% of these failures automatically. Critical failures — contrast, alt text, form labels, keyboard traps — are often caught in a free scan.
Perceivable — Text Alternatives
1.1.1
A
Non-text Content
All images, icons, and graphics have descriptive alt text. Decorative images have alt="".
1.2.1
A
Audio-only and Video-only
Pre-recorded audio has a text transcript. Pre-recorded video has a text or audio alternative.
1.2.2
A
Captions (Pre-recorded)
All pre-recorded video has synchronized captions — auto-captions reviewed for accuracy count.
1.2.3
A
Audio Description or Media Alternative
Pre-recorded video has audio description OR a text alternative describing visual content.
1.2.5
AA
Audio Description (Pre-recorded)
Pre-recorded video content has audio description for all visual information not in audio track.
Perceivable — Adaptable
1.3.1
A
Info and Relationships
Structure conveyed visually (headings, lists, tables) is also in the markup. Forms have proper label associations.
1.3.2
A
Meaningful Sequence
Reading order of content makes sense when CSS is removed. Screen readers encounter content in logical order.
1.3.3
A
Sensory Characteristics
Instructions don't rely solely on shape, color, size, or position. 'Click the red button' alone is insufficient.
1.3.4
AA
Orientation
Content doesn't lock to portrait or landscape orientation unless essential to the function.
1.3.5
AA
Identify Input Purpose
Input fields for personal data (name, email, address) have autocomplete attributes so browsers can auto-fill.
Perceivable — Distinguishable
1.4.1
A
Use of Color
Color is not the only way to convey information. Error messages use text, icons, or borders — not just red color.
1.4.2
A
Audio Control
Audio that plays automatically for more than 3 seconds can be paused, stopped, or muted.
1.4.3
AA
Contrast (Minimum)
Normal text has at least 4.5:1 contrast ratio. Large text (18pt or 14pt bold) needs 3:1. Most common government site failure.
1.4.4
AA
Resize Text
Text can be resized up to 200% without loss of content or functionality.
1.4.5
AA
Images of Text
Text is used instead of images of text unless essential. Navigation menus, headings, and labels use real text.
1.4.10
AA
Reflow
Content at 320px width doesn't require horizontal scrolling. Responsive design or single-column layout required.
1.4.11
AA
Non-text Contrast
UI components (form borders, focus indicators, icons) have at least 3:1 contrast against adjacent colors.
1.4.12
AA
Text Spacing
No loss of content when letter spacing, word spacing, line height, and paragraph spacing are overridden by user.
1.4.13
AA
Content on Hover or Focus
Tooltip and hover content is dismissible, hoverable (cursor can move to it), and persistent until dismissed.
Operable — Keyboard Accessible
2.1.1
A
Keyboard
All functionality is available using keyboard alone. No mouse required for any action.
2.1.2
A
No Keyboard Trap
Keyboard focus can always move away from any component. Modal dialogs must close with Escape key.
2.1.4
A
Character Key Shortcuts
Single-key shortcuts can be turned off, remapped, or only active when component has focus.
Operable — Enough Time
2.2.1
A
Timing Adjustable
Users can turn off, adjust, or extend any time limit — except for real-time events.
2.2.2
A
Pause, Stop, Hide
Moving or auto-updating content (carousels, news tickers) can be paused, stopped, or hidden.
Operable — Navigable
2.4.1
A
Bypass Blocks
A skip navigation link allows keyboard users to bypass repeated header/nav content. Must be the first focusable element.
2.4.2
A
Page Titled
Every page has a unique, descriptive title that identifies the site and the current page.
2.4.3
A
Focus Order
Tab order follows a logical reading sequence. Focus doesn't jump unexpectedly across the page.
2.4.4
A
Link Purpose
Link text describes its destination. 'Click here' and 'Read more' with no context fail this criterion.
2.4.5
AA
Multiple Ways
More than one way to find any page — search, site map, or navigation links.
2.4.6
AA
Headings and Labels
Headings (H1-H6) describe their sections. Form labels describe their purpose. Both must be descriptive, not generic.
2.4.7
AA
Focus Visible
The keyboard focus indicator is visible when navigating. CSS outline:none or visibility:hidden on :focus fails this.
Understandable — Readable
3.1.1
A
Language of Page
The HTML lang attribute is set to the correct language. <html lang='en'> for English-language sites.
3.1.2
AA
Language of Parts
Phrases in other languages are marked with lang attribute changes. Common for bilingual government sites.
Understandable — Predictable
3.2.1
A
On Focus
Receiving focus doesn't automatically trigger a context change. No auto-submit forms or auto-redirects on focus.
3.2.2
A
On Input
Changing a setting (dropdown, radio button) doesn't automatically cause a page change without warning.
3.2.3
AA
Consistent Navigation
Navigation components appear in the same order on all pages. Common failure when school sites differ from district site.
3.2.4
AA
Consistent Identification
UI components with the same function have the same labels and icons across all pages.
Understandable — Input Assistance
3.3.1
A
Error Identification
Form errors are described in text — not only by color or icon. 'This field is required' not just a red border.
3.3.2
A
Labels or Instructions
Forms provide labels or instructions for all inputs requiring specific format (date, phone number, etc.).
3.3.3
AA
Error Suggestion
Error messages suggest how to fix the error. 'Invalid date' → 'Enter date as MM/DD/YYYY'.
3.3.4
AA
Error Prevention (Legal, Financial)
For legal, financial, or permanent data changes — submissions can be reviewed, confirmed, or reversed.
Robust — Compatible
4.1.1
A
Parsing
HTML has no duplicate IDs, no missing closing tags, and no improperly nested elements that confuse assistive technology.
4.1.2
A
Name, Role, Value
All UI components have accessible names, roles, and states that assistive technologies can read. Custom widgets use ARIA.
4.1.3
AA
Status Messages
Status updates (form submitted, loading, errors) are communicated to assistive technology without requiring focus.
The Automated Scan Limit
Automated tools like CertusAudit reliably detect about 40% of WCAG failures — primarily contrast failures, missing alt text, missing form labels, structural HTML issues, and language attributes. The remaining 60% (keyboard traps, focus order, meaningful sequence, error suggestions, audio descriptions) require human testing with actual assistive technology. The DOJ rule does not specify what kind of testing is required — it specifies the outcome. A combined automated scan + targeted manual review of high-risk areas (forms, navigation, videos) is the minimum defensible approach.
Start With the 40% You Can Fix Today
Run a free scan. Get your automated WCAG score in 60 seconds.
Then order the $299 compliance report for the full issue list, regulatory citations, and a 30/60/90 day roadmap your IT team and legal counsel can act on.