ROVQIX audits websites and applications against WCAG 2.2 AA using automated tooling plus manual keyboard and screen reader testing, then implements the fixes in your codebase and documents the result for procurement, legal or VPAT purposes.
Automated scanners catch roughly a third of accessibility issues. The rest — focus order, meaningful labels, sensible announcements — need someone to actually operate the site without a mouse.
Audit standard
Keyboard + screen reader
Fixes, not a list
For procurement
Full-site scanning to catch the mechanical issues quickly — contrast, missing labels, invalid ARIA.
Every primary flow operated by keyboard alone and with a screen reader, which is where the real issues live.
Issues ranked by user impact and legal exposure, each with the specific code change required.
Fixes written and merged in your codebase, with regression tests where the pattern is likely to recur.
Repairing shared components fixes hundreds of pages at once — usually the highest-leverage work.
A conformance report you can give procurement, plus guidance so new work does not reintroduce the same issues.
| Automated tools catch | Only manual testing catches |
|---|---|
| Missing alt attributes | Whether alt text is meaningful |
| Colour contrast failures | Information conveyed by colour alone |
| Missing form labels | Whether labels describe the actual input |
| Invalid ARIA usage | Whether ARIA improves or breaks the experience |
| Missing landmarks | Whether focus order matches visual order |
| Empty links and buttons | Whether dynamic changes are announced |
| Missing lang attribute | Whether error recovery is possible |
| Scope | Audit | Remediation |
|---|---|---|
| Marketing site, under 20 pages | 3–5 days | 1–2 weeks |
| Larger site with templates | 1–2 weeks | 2–4 weeks |
| Web application | 2–3 weeks | 4–10 weeks |
| Design system | 1 week | 2–4 weeks |
Remediating shared components first is what makes application work tractable — one fixed date picker resolves the same issue on every page that uses it.
The ADA does not specify a technical standard; courts and settlements consistently reference WCAG. Meeting WCAG 2.2 AA substantially reduces exposure, but compliance is a legal determination and we are not lawyers. We will document exactly what was tested and fixed.
No, and they can make things worse. They have been the subject of numerous lawsuits and are widely rejected by disabled users. Fix the underlying code instead — there is no shortcut here.
We provide the detailed conformance documentation a VPAT is built from. For a formal signed VPAT, an independent accessibility firm is the appropriate route, and we will remediate against their findings.
Every unique template and every primary user flow, rather than every page. On a template-driven site that is usually 15 to 30 pages representing the whole thing.
Indicative ranges in USD. Every engagement is quoted to a written scope before work starts, so the number you approve is the number you pay.
$1,800 – $6,000
1–3 weeks
Best for: Knowing where you stand
$5,000 – $20,000
4–10 weeks
Best for: Actually reaching WCAG 2.2 AA
from $900 / month
Ongoing
Best for: Teams shipping continuously
How we think about this work, in more depth.
Accessibility
A 30-minute call, then a written proposal with scope, price and timeline within two to three working days. No retainer required to get a real number, and no obligation if the answer is that we are not the right fit.