If your team receives a WCAG 2.2 AA audit report, the phrase means more than "accessibility was checked."
It means the scoped experience should be evaluated against applicable Level A and Level AA success criteria from WCAG 2.2.
What AA means technically
AA includes A plus AA. It does not mean only AA criteria. It also does not include every AAA criterion.
This matters when triaging findings because WCAG level and issue severity are different things.
WCAG level tells you the standards target. Severity tells you how urgent the issue is in the real product context.
What tends to fail in real products
Common WCAG 2.2 AA issues include:
- Keyboard traps.
- Focus indicators that are missing or hidden.
- Controls with missing or incorrect accessible names.
- Form errors that are not programmatically associated.
- Poor contrast or non-text contrast.
- Drag-only interactions without alternatives.
- Small pointer targets.
- Repeated data entry.
- Authentication steps that create cognitive barriers.
- Dynamic status messages not announced to assistive technologies.
Many of these issues are not fully detectable with automation.
What a developer-friendly finding needs
A useful audit finding should include:
- Route, screen, component, state, or document.
- Steps to reproduce.
- Expected behavior.
- Actual behavior.
- WCAG 2.2 criterion and level.
- User impact.
- Evidence.
- Remediation direction.
- Retest expectation.
This converts WCAG from a standards reference into engineering work.
Retesting matters
Do not treat a merged fix as verified closure.
If the original issue involved keyboard behavior, retest with keyboard. If it involved screen reader output, retest with assistive technology. If it involved a PDF, retest the document structure.
The verification method should match the original barrier.
Conclusion
WCAG 2.2 AA is a practical audit target when it is scoped, evidenced, and retested correctly.
For developers and QA teams, the key is to preserve the chain from criterion to issue to fix to verified behavior.
Read the original guide on IAAP Audit: https://iaapaudit.com/blog/wcag-2-2-aa-accessibility-audit
Top comments (0)