ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
2
WCAG 2.1 AA Audit Framework
3
ADA Title II Compliance | State and Local Government Entities | Hounder University | hounder.co
4
HOW TO USE: Test each criterion against your target pages or components. Mark Pass, Fail, or N/A. Rate every failure: Critical (blocks task completion), High (major barrier), Medium (degraded experience), Low (minor issue). Every Fail row should become a line item in your Accessibility Remediation Log.
5
Organization: Auditor:
6
Audit Date:Tool(s) Used:
7
Audit Type:Automated Only ☐ Manual + Automated ☐ Full (including user testing) ☐
8
CriterionPrincipleSuccess Criterion DescriptionCommon FailurePassFailN/ASeverity
(if Fail)		Page / Component / URLAssigned ToNotes
9
PERCEIVABLE | Users must be able to perceive all information and UI components.
10
1.1.1PerceivableNon-text content has a text alternative (alt text, label, caption) that serves equivalent purpose.Missing or generic alt text (alt='image' or alt='photo')PassN/AFailCriticalTest with: axe, WAVE, manual screen reader check
11
1.2.2PerceivableCaptions provided for all prerecorded audio in synchronized media.No closed captions on video contentAutomated captions don't count — must be accurate
12
1.2.3PerceivableAudio description or media alternative provided for prerecorded video.No description of visual-only information in video
13
1.2.5PerceivableAudio descriptions provided for all prerecorded video in synchronized media.Video narration doesn't describe on-screen visuals
14
1.3.1PerceivableInformation, structure, and relationships are programmatically determinable.Tables without headers; lists coded as plain paragraphsCheck heading hierarchy and landmark regions
15
1.3.2PerceivableCorrect reading sequence determinable when presentation affects meaning.CSS-repositioned content breaks logical reading orderTab through page without CSS to verify order
16
1.3.3PerceivableInstructions don't rely solely on shape, color, size, or position."Click the green button" or "see the form on the right" as sole instruction
17
1.3.4PerceivableContent doesn't restrict view to a single display orientation.Page locked to portrait or landscape only
18
1.3.5PerceivablePurpose of inputs collecting personal data can be programmatically determined.Form fields missing autocomplete attributesRequired for name, email, address, phone fields
19
1.4.1PerceivableColor is not the only visual means of conveying information.Error states shown only by red color with no other indicatorAdd icon, text label, or border change
20
1.4.2PerceivableMechanism to pause or stop audio that plays automatically.Background audio with no pause/stop/mute control
21
1.4.3PerceivableText has contrast ratio of at least 4.5:1 (3:1 for large text 18pt+ or 14pt bold).Light gray text on white; brand colors with insufficient contrastTest with: WebAIM Contrast Checker
22
1.4.4PerceivableText resizable up to 200% without loss of content or function.Content overflows, truncates, or disappears at 200% browser zoomTest by zooming browser to 200%
23
1.4.5PerceivableText used instead of images of text where possible.Headings or buttons rendered as images containing text
24
1.4.10PerceivableContent reflows without horizontal scrolling at 320px viewport width.Fixed-width layouts requiring horizontal scroll on mobileTest at 320px viewport width
25
1.4.11PerceivableNon-text UI components have contrast ratio of at least 3:1 against adjacent colors.Form borders, icon buttons, or focus rings with insufficient contrastApplies to UI states: focus, hover, active
26
1.4.12PerceivableNo loss of content when letter/word/line/paragraph spacing is overridden.Text truncates or overlaps when spacing increased via browserTest with bookmarklet or browser extension
27
1.4.13PerceivableContent shown on hover or focus can be dismissed, hovered over, and is persistent.Tooltips disappear when user moves cursor toward them
28
OPERABLE | Users must be able to operate all interface components and navigation.
29
2.1.1OperableAll functionality operable through keyboard interface without requiring specific timing.Dropdown menus, modals, or custom components not keyboard accessibleTab through entire page to test
30
2.1.2OperableKeyboard focus never trapped unless intentionally (with escape mechanism).Focus trapped inside modal with no way to exitTest: can you Tab or Esc out of every component?
31
2.1.4OperableSingle-character keyboard shortcuts can be turned off, remapped, or activated only on focus.Single-key shortcuts conflicting with screen reader or voice control commands
32
2.2.1OperableUsers can turn off, adjust, or extend time limits.Session timeout with no warning or extension option20-hour exception for real-time events
33
2.2.2OperableUsers can pause, stop, or hide moving/blinking/auto-updating content.Auto-advancing carousels with no pause; auto-refreshing data feeds
34
2.3.1OperableNo content flashes more than three times per second.Animated GIFs, video intros, or transitions exceeding flash threshold
35
2.4.1OperableMechanism to skip blocks of repeated content.No skip navigation link; no landmark regions for screen reader usersAdd skip-to-main-content link at top of page
36
2.4.2OperableWeb pages have titles that describe topic or purpose.Pages titled "Home" or using site name alone with no page context
37
2.4.3OperableFocus order preserves meaning and operability.Tab order jumps unpredictably; focus moves to bottom of page on modal open
38
2.4.4OperableLink purpose determinable from link text alone or context."Click here" or "Read more" links with no surrounding context that clarifies purpose
39
2.4.5OperableMore than one way to locate a page within a set of pages.No site search, sitemap, or secondary navigationException: page is a step in a process
40
2.4.6OperableHeadings and labels are descriptive.Generic headings like "Section 1"; unlabeled or vague form fields
41
2.4.7OperableKeyboard-focused components have visible focus indicator.Focus ring hidden by CSS outline:none or outline:0Removal of focus ring is one of the most common failures
42
2.5.1OperableAll multipoint or path-based gestures have a single-pointer alternative.Pinch-zoom, two-finger scroll, or swipe-only interactions with no tap alternative
43
2.5.2OperableFunctions triggered on pointer down-event can be aborted or reversed.Actions completing on mousedown/touchstart with no undo
44
2.5.3OperableLabels visible in UI match or contain the accessible name of the component.Visible button label differs from programmatic accessible nameCauses failures for voice control users
45
2.5.4OperableFunctionality triggered by device motion has UI control alternative and can be disabled.Shake-to-undo or tilt features with no interface-based alternative
46
UNDERSTANDABLE | Information and the operation of the UI must be understandable.
47
3.1.1UnderstandableDefault language of page is programmatically determined.Missing lang attribute on <html> elementAutomated tools catch this reliably
48
3.1.2UnderstandableLanguage of passages in a different language is identified.Foreign-language content without lang attribute on containing element
49
3.2.1UnderstandableFocus does not trigger unexpected context changes.Page refreshes or navigation triggered just by receiving focus
50
3.2.2UnderstandableInput does not trigger unexpected context changes without user initiation.Form submits automatically on selection change with no submit button
51
3.2.3UnderstandableNavigation is presented consistently across pages.Primary navigation changes position, order, or labeling between pages
52
3.2.4UnderstandableComponents with same function identified consistently across pages.Search icon labeled 'Search' on one page and 'Find' on another
53
3.3.1UnderstandableInput errors are automatically identified and described to users in text.Form errors shown only by red border or exclamation icon with no text description
54
3.3.2UnderstandableLabels or instructions provided for user input.Placeholder text used as only label (disappears on input); no visible field labels
55
3.3.3UnderstandableError suggestions provided when input error is detected and known."Invalid entry" with no guidance on what format or value is required
56
3.3.4UnderstandableSubmissions causing legal, financial, or data commitments can be checked, confirmed, or reversed.No review or confirmation screen before irreversible form submission
57
ROBUST | Content must be robust enough to be interpreted by assistive technologies.
58
4.1.1RobustHTML parses without duplicate IDs, missing start/end tags, or invalid nesting.Duplicate IDs causing ARIA relationships to break; unclosed elementsAutomated tools catch this well
59
4.1.2RobustAll UI components have accessible name, role, and state programmatically exposed.Custom buttons, dropdowns, toggles, tabs, or accordions missing ARIA roles or statesNo ARIA is better than bad ARIA — test with screen reader
60
4.1.3RobustStatus messages are programmatically determinable without receiving focus.Success messages, error banners, or loading states not announced to screen readersUse role='status' or role='alert' or aria-live regions
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100