WCAG 2.2 AA Audit Deliverable — Prioritized Findings

A regional behavioral health organization needed a structured WCAG 2.2 AA audit of their WordPress portal site to scope remediation work ahead of stakeholder review. The deliverable was an audit pass — not implementation — producing an actionable findings list the client could triage and budget against.

I worked the site systematically across five evaluation tracks:

Keyboard navigation traversal across all interactive surfaces — every button, link, form input, and custom widget. Tested with Tab / Shift+Tab / Enter / Space / Arrow keys to verify expected behavior under WCAG 2.1.1 (Keyboard).

Screen reader pass on key flows using NVDA + VoiceOver — verifying landmark structure, heading hierarchy, ARIA roles, and announced text under WCAG 1.3.1 (Info and Relationships) and 4.1.2 (Name, Role, Value).

Contrast measurement on theme and content tokens via automated tools and manual spot-checks for WCAG 1.4.3 (Contrast Minimum). Both normal text (4.5:1) and large text (3:1) thresholds verified.

Focus visibility audit under WCAG 2.4.7 (Focus Visible) and 2.4.11 (Focus Not Obscured, new in 2.2).

Automated axe DevTools sweep as a baseline, followed by manual verification of every flagged item to filter false positives.

Motion / auto-playing content review against WCAG 2.2.2 (Pause, Stop, Hide), including hero carousels and embedded video.

Each finding got logged with: the specific WCAG criterion, the affected element/location, a recommended fix, and an effort estimate in hours.

The output was a structured findings report — 13 substantive findings across keyboard, focus, contrast, link naming, and motion categories, plus 2 polish-tier items. Findings grouped by remediation effort (Quick Wins / Standard / Heavy Lift) so the client could greenlight by tier rather than line-item, with ~6–8 hours of implementation work estimated for full pass-through.

Compliance audits and remediation are often bundled. They shouldn't always be. Procurement processes and internal stakeholder approval gates frequently need a vendor-neutral findings document before any implementation contract gets signed — and the audit deliverable is what unlocks the rest of the budget. Pairing the audit with a clean tier-by-effort breakdown gives the client a real conversation tool for their next budget cycle.

axe DevTools, Lighthouse a11y, NVDA + VoiceOver, manual keyboard + screen reader testing, color contrast analyzers, WCAG 2.2 reference, structured findings template.

13 findings + 2 polish items delivered in 2.5 audit hours. Client gets a prioritized roadmap with effort estimates per tier. Implementation pass scoped and ready for separate engagement.

Tags: Accessibility, WCAG 2.2, ADA compliance, audit, a11y, WordPress, findings report, NVDA, VoiceOver, axe DevTools