WCAG 2.2 monitoring
Ongoing accessibility monitoring without false certainty.
BarrierTrace helps teams watch for detectable WCAG 2.2 issues while retaining the manual evidence and scope needed to interpret every result honestly.
01
Accessibility changes whenever a website changes
New components, content, third-party services and design-system updates can introduce barriers after an audit has finished. Repeatable monitoring provides an early signal when tested pages change or automated findings appear.
BarrierTrace records scans against a known page set, making trends easier to compare and helping teams decide where human review is most useful.
02
WCAG evidence needs context
WCAG 2.2 includes requirements that software can test reliably, requirements that need human judgement and requirements that depend on complete user journeys. A clean automated result therefore does not mean that a page or website conforms.
BarrierTrace shows automated findings as evidence within a wider assurance process. Teams can record keyboard navigation, focus visibility, screen-reader behaviour, zoom, reflow and content observations without obscuring who performed the check.
- Automated signals mapped to relevant WCAG criteria
- Human checks with notes, tester and revision history
- Visible limitations and incomplete evidence
- Portfolio reporting across monitored websites
03
Use trends to guide action, not certify compliance
A trend can show that detectable issues have reduced, remained stable or reappeared. It cannot prove that every success criterion was tested across every relevant state.
BarrierTrace keeps this distinction clear so reports can support governance conversations, remediation planning and follow-up testing without making unsupported compliance claims.