Do I really need a manual audit — isn't an automated scan enough?
Automated tools catch roughly 30% of accessibility issues. The rest — keyboard traps, illogical focus order, missing context, unusable widgets — require a human and an assistive-technology user. Every audit we run combines automated coverage with expert manual testing.
What is WCAG 2.2 and which level do I need?
WCAG 2.2 is the current Web Content Accessibility Guidelines standard that courts, the DOJ, and enterprise procurement teams reference. Level AA is the level nearly every organisation is expected to meet, and it is the level we test and remediate to.
Can accessibility actually reduce my legal risk?
Yes. Courts consistently treat business websites as places of public accommodation under the ADA. Documented, defensible WCAG 2.2 conformance — plus a remediation record showing continuous effort — is the strongest protection available before a demand letter arrives.
Do you fix the issues, or just tell me what's wrong?
Both. The audit gives your team a prioritised, developer-ready report, and our engineers can remediate at the source in your own codebase, then re-test to confirm every issue is resolved.
How long does an audit take?
A single-template audit typically takes about a week. A full multi-template site with complex flows usually runs two to four weeks, depending on the number of unique templates and the amount of dynamic functionality involved.
Do you offer ongoing monitoring after remediation?
Yes. Sites change constantly, and new content ships new barriers. Continuous monitoring scans your live site for regressions and flags them before your users — or a plaintiff — find them.