Real WCAG Remediation
Not Overlays, Not Certificates
A buyer wants your VPAT, the EU's Accessibility Act deadline hit, or an ADA demand letter landed. We audit against WCAG 2.2 AA / EN 301 549, fix the real source code, and hand you an audit-backed VPAT and accessibility statement you own. Fixed price. No band-aids, no “certification” theater.
CodesSavvy is a senior engineering studio offering accessibility audits and WCAG remediation. We test against WCAG 2.1/2.2 AA and EN 301 549, remediate the real source code, and author defensible VPAT/ACR reports and accessibility statements — for ADA, Section 508, HHS §504, and European Accessibility Act obligations. Fixed price, you own the code. We work with startups and businesses in the US, UK, Canada, and Australia.
Web Accessibility in 2026, By the Numbers
Litigation is at record highs, hard deadlines are live, and the cheap shortcut just collapsed. The one thing courts, regulators, and enterprise buyers now agree on: they want real, conformant code.
FTC fine against the largest accessibility-overlay vendor for false WCAG compliance claims — overlays are not a fix. FTC, 2025
of H1-2025 US web-accessibility lawsuits targeted sites that had already installed an overlay widget. The band-aid is now the evidence. UsableNet, 2025
the EU's European Accessibility Act became enforceable — for any business selling to EU consumers, benchmarked to EN 301 549 / WCAG 2.1 AA. European Commission
What Actually Reduces Risk — and What Doesn't
This market is full of shortcuts that make the problem worse. Here's the honest line between what a court, regulator, or buyer accepts and what they now treat as evidence against you.
What Actually Works
- ✓A genuine manual audit against WCAG 2.1 / 2.2 AA (and EN 301 549 for the EU/Canada)
- ✓Real source-code remediation — keyboard, focus, ARIA, forms, contrast, components
- ✓An audit-backed VPAT / ACR your buyer's team can actually scrutinise
- ✓A published accessibility statement and a defensible paper trail
- ✓Ongoing monitoring so it stays conformant as the product changes
- ✓Code you fully own — your repo, your cloud, your keys, no lock-in
What's a Liability
- ✗A 'WCAG certificate' — no such thing exists and it reduces zero liability
- ✗An overlay widget that injects JavaScript screen readers ignore at load
- ✗A blank VPAT template you filled in yourself, untested and indefensible
- ✗An automated scan alone — it catches only ~20–40% of real issues
- ✗A promise you 'won't get sued' — no honest vendor can guarantee that
- ✗A dependency on the vendor's script that breaks the moment you cancel
Our rule: the only thing that holds up under a security review, a regulator, or a courtroom is conformant code plus an honest, audit-backed paper trail. Everything else is theater — and the overlay kind is now cited as evidence in the lawsuit. We only build the version that survives scrutiny.
What We Do
The full loop from audit to defensible artifact to staying-compliant — all as real engineering, all code you own.
WCAG 2.2 AA Audit
Manual + automated audit against WCAG 2.1/2.2 AA or EN 301 549 — keyboard, screen reader, contrast, forms, and complex components. A findings report you can act on, not a vanity score.
Real-Code Remediation
Senior engineers fix the actual source — focus management, ARIA names/roles/states, labelled forms, contrast, and the hard parts overlays can't touch. In your repo. You keep every line.
VPAT / ACR Authoring
An audit-backed Accessibility Conformance Report your buyer's procurement team can scrutinise — for Section 508, EN 301 549, or WCAG. Re-issued per release. Never a rubber stamp.
PDF/UA Document Remediation
Accessible PDFs and documents (ISO 14289 / PDF-UA) — tag trees, reading order, tables, and forms. For the back-catalogs Section 508, HHS §504, and EN 301 549 put on the hook.
Complex UI & Data-Viz
The corner of WCAG where generalists freeze: keyboard-navigable charts, screen-reader data tables, and accessible dashboards. We build these — so we can fix them.
Monitoring & Re-Audit
Automated scanning + periodic manual review + real fixes, keeping your VPAT and statement current. Because ~73% of issues resurface within six months without it.
The Regimes We Map Your Fix To
“Accessible” means something specific depending on who's forcing you. We target the exact standard and deadline that applies to your business — not a generic checklist.
| Regime | What forces it | Standard | Who's on the hook |
|---|---|---|---|
| ADA Title III (US) | Private lawsuits & demand letters | WCAG 2.1 AA (de facto) | Any US business, esp. e-commerce |
| ADA Title II (US) | DOJ rule — deadline 2027 / 2028 | WCAG 2.1 AA | State/local govt + their vendors |
| HHS Section 504 (US) | Federal-funds rule — May 2026 | WCAG 2.1 AA | HHS-funded healthcare |
| Section 508 (US) | Federal procurement gate | WCAG 2.0/2.1 AA + WCAG2ICT | Vendors selling to the govt |
| EAA (EU) | Enforceable since Jun 2025 | EN 301 549 → WCAG 2.1 AA | Anyone selling to EU consumers |
| Accessible Canada Act | Deadlines 2027 / 2028 | CAN/ASC-EN 301 549 | Federally-regulated: banks, telcos |
Not sure which applies? The free VPAT Gap Check tells you which regime is forcing you and what it would take to satisfy it.
Audit → Remediate → VPAT → Monitor
A fixed-price path from “we're exposed” to “we're defensible.” You sign off at each step before the next begins.
Audit & Gap Read
A senior engineer audits your product against WCAG 2.2 AA / EN 301 549 — manual testing, not just a scanner. You get a red/amber/green findings report, the blockers ranked, and which law actually applies to you. Start free with a VPAT Gap Check.
Fixed-Price Remediation
We fix the real source code — keyboard, focus, ARIA, forms, contrast, and complex components — in your repository. Fixed price on a written scope. You test each batch. You own every line.
VPAT / ACR + Statement
We author an audit-backed VPAT/ACR and a published accessibility statement you own — the defensible artifact procurement, regulators, or courts ask for. Never a certificate, never an overlay.
Monitoring (optional)
A retainer that re-audits on each release, keeps the VPAT current, and fixes regressions before they become findings — because accessibility degrades every time the product changes.
Accessibility & VPAT — Frequently Asked Questions
Find out what stands between you and the VPAT
Send us your product and what's forcing this — a VPAT request, an EAA deadline, a demand letter. A senior engineer sends back an honest gap read: where you stand against WCAG 2.2 AA and exactly what it would take to be defensible. Free.
VPAT Gap Check
A buyer wants your VPAT? Get a free read on what stands between you and a defensible one
RelatedAI App Rescue
AI built it, but it breaks in production? We fix the real code
RelatedSupabase Security Audit
Leaking data between users? We audit RLS, auth, and storage
RelatedWeb App Development
Production-grade builds — accessible from day one, code you own