WCAG 2.2 Audits
POUR-framework audits combining axe-core, Lighthouse, Playwright accessibility tree inspection, and live NVDA/JAWS testing. Every violation documented with WCAG criterion, severity, and a code-level fix.
View audit packagesExpert accessibility auditing, remediation, and monitoring — grounded in WCAG 2.2, ADA risk context, and Section 508 awareness, validated through 25+ years of authentic screen reader mastery.
Auditing against
- WCAG 2.2 Level AA
- ADA Title II
- Section 508
- EN 301 549
- POUR Framework
- axe-core · Lighthouse · NVDA
Proven in production
Trusted by teams who cannot afford inaccessible software.
Audit, remediation, and monitoring engagements delivered across financial services, home technology, education finance, and higher education.
- Mountain America Credit Union
- Vivint
- Nelnet Business Solutions
- Stark Science Learning Center, University of Utah
17-page
Comprehensive audit report delivered to the Stark Science Learning Center at the University of Utah, now in active remediation
25+ years
Daily screen reader use behind every audit — findings come from lived experience, not a checklist
WCAG 2.2 AA
Conformance target for every engagement, with ADA Title II and Section 508 context included
JAWS & NVDA
Manual assistive technology testing on real software, alongside keyboard-only and focus management review
Client testimonial
“Quintin and Lewis's audit went far beyond standards compliance and surfaced real-world friction points that no automated tool would have caught. His partnership has reshaped how our team approaches accessibility, and we cannot recommend QA11Y Labs highly enough to anyone serious about building genuinely usable digital experiences.”
What We Do
Full-service accessibility, start to finish.
From rapid audits to full remediation support — every engagement is grounded in real assistive technology testing.
Remediation
We write and review semantic HTML, ARIA patterns, keyboard navigation, and focus management — building the fix directly into your codebase, not just a report alongside it.
View remediationOngoing Monitoring
Scheduled automated scans with regression alerts — so new deployments don't reintroduce violations. We monitor against your agreed baseline and flag changes before users encounter them.
Monitoring plansConsulting
Expert consulting on ARIA patterns, keyboard navigation, screen reader testing methodology, and WCAG 2.2 conformance. We work directly with your team to identify and solve complex accessibility problems.
Talk to us
Why QA11Y Labs
We don't test accessibility.
We don't test accessibility.
We live it.
Most accessibility consultants run automated tools and hand you a spreadsheet. We bring something no tool can replicate — 25+ years as a daily screen reader user. We experience the web the way your disabled users do, which means we find barriers that automated scanners miss entirely.
Lighthouse scored the module we audited for SSLC at 100/100 for accessibility. Our manual tree inspection found 69 critical violations that Lighthouse never touched.
-
Real screen reader testing NVDA, JAWS, VoiceOver — validated on actual assistive technology, not simulations.
-
Automated + manual, combined axe-core, Playwright accessibility tree, and Lighthouse — then we go further by hand.
-
Code-level remediation reports Every finding comes with the exact HTML/ARIA fix — not just a reference to the WCAG criterion.
-
Legal defensibility Structured VPAT-ready documentation that holds up under ADA Title II and Section 508 scrutiny.
The audit process
What you get, step by step.
Every engagement runs through the same four stages, so you always know what has been checked, what was found, and what happens next.
1. Automated scan
axe-core and Lighthouse run across your pages to establish a baseline and clear the machine-detectable issues quickly, so paid manual time goes to the problems tooling cannot reach.
2. Manual screen reader review
Each key flow is driven by hand with JAWS, NVDA, and VoiceOver, plus keyboard-only navigation and focus management checks. This is where the friction real users hit gets found.
3. Code-level remediation
Every finding is documented with its WCAG 2.2 criterion, severity, and the specific HTML or ARIA fix — and we work alongside your developers while those fixes land.
4. Ongoing monitoring
Scheduled re-scans watch your agreed baseline and flag regressions, so a later deploy does not quietly reintroduce a violation you have already paid to fix.