Key Takeaways
WCAG 2.2 AA adds nine new success criteria to 2.1, focusing on cognitive load, mobile interactions, and authentication.
SaaS accessibility requires testing dynamic states (modals, toasts, virtualized lists), not just static pages.
Automated tools catch ~30% of issues; manual keyboard and screen reader testing is non-negotiable for AA conformance.
Contrast ratios (4.5:1 text, 3:1 UI components) must be verified in all themes—light, dark, and high-contrast modes.
Document remediation in a living audit report tied to your issue tracker to prove ongoing compliance.
Why WCAG 2.2 AA Matters for Modern Web Apps
WCAG 2.2 (released October 2023) is the current benchmark for legal compliance (ADA, EAA, AODA) and procurement requirements (VPAT/ACR). For SaaS accessibility, the stakes are higher: single-page applications (SPAs), real-time collaboration, and complex dashboards introduce failure modes that static marketing sites never encounter.
The 2.2 update introduces nine new Success Criteria (SC). Six apply at Level AA. If your product targets enterprise or government buyers, a WCAG 2.2 AA checklist is now a sales enablement artifact, not just a compliance exercise.
The Six New AA Criteria You Must Test
| Criterion | Short Name | What It Breaks in SaaS |
| :--- | :--- | :--- |
| 2.4.11 | Focus Not Obscured (Minimum) | Sticky headers, chat widgets, or cookie banners hiding keyboard focus. |
| 2.4.12 | Focus Not Obscured (Enhanced) | Same as above, but no part of the focus indicator may be hidden. |
| 2.5.7 | Dragging Movements | Kanban boards, slider inputs, map pinching—must offer a single-pointer alternative. |
| 2.5.8 | Target Size (Minimum) | 24×24 px CSS hit area for icons, avatar menus, dense toolbar actions. |
| 3.2.6 | Consistent Help | Help link/chat icon must appear in the same relative order on every page/view. |
| 3.3.8 | Accessible Authentication (Minimum) | No cognitive function tests (puzzles, recall) for login/MFA unless an alternative exists. |
Note: 2.4.13 (Focus Appearance) is Level AAA in 2.2 but widely adopted as a de-facto AA standard. Treat it as required.
5-Step Practical Audit Checklist
1. Automated Baseline Scan
Run a web accessibility audit tool (axe-core, WAVE, or Lighthouse) against every unique route and major component state (open modal, error toast, loading skeleton).
Action: Export JSON results; deduplicate by component, not URL.
Gap: Automation misses focus order, drag alternatives, and authentication flows.
2. Keyboard-Only Navigation Sweep
Disable the mouse. Tab through every interactive element in this sequence:
Global: Skip link → Header → Main → Footer.
App Shell: Sidebar navigation, user menu, notification bell.
Data Dense: Virtualized tables (ensure focus moves into rows), pagination, inline edit.
Modals/Drawers: Focus trap, restore focus on close,
Escdismiss.
-
Verify: Focus Not Obscured (SC 2.4.11/12) against sticky headers (
position: sticky) and fixed footers.
3. Visual & Contrast Validation
Use a contrast checker (e.g., Colour Contrast Analyser, Figma plugin, or browser DevTools) on computed styles.
Text: 4.5:1 (normal), 3:1 (large ≥18.5px bold / 24px regular).
UI Components & Graphics: 3:1 against adjacent colors (borders, icons, chart segments).
States: Hover, focus, active, disabled, error, and forced-colors/high-contrast mode.
Themes: Run the matrix for Light, Dark, and System-preference modes.
4. Cognitive & Interaction Barriers
Dragging (2.5.7): For every drag-and-drop UI, provide arrow-key reorder, "Move to…" menu, or input field alternative.
Target Size (2.5.8): Measure hit areas in DevTools (
offsetWidth/Height). Pad small icons with transparent::beforepseudo-elements if visual design cannot change.Authentication (3.3.8): Audit login, MFA, password reset, and account recovery. Allow password managers, WebAuthn/passkeys, magic links, or SMS/email codes without memorization or transcription puzzles.
5. Screen Reader & Live Region Testing
Test with NVDA (Windows) + Chrome and VoiceOver (macOS) + Safari.
Announcements: Toast notifications, form validation errors, loading state changes (
aria-live="polite"vs"assertive").Virtualized Lists: Ensure
aria-setsize/aria-posinsetupdate on scroll.Landmarks: Unique
aria-labelon each<nav>,<aside>,<section role="region">.Consistent Help (3.2.6): Verify help/chat link position is identical in DOM order across Dashboard, Settings, and Help Center views
Free Browser-Local Tool: Free WCAG 2.2 Audit Tool (zero signup, runs 100% in your browser)
Originally published at https://b2appsdev-del.github.io/blog/wcag-2-2-aa-accessibility-audit-checklist.html. Educational and planning guide only; not financial, tax, or legal advice.
Top comments (0)