Accessibility remediation that fixes the code, not the symptoms.
We fix the WCAG failures in your website or web app at the source: markup, labels, focus, keyboard behaviour and your component library. Then we retest with a keyboard and real screen readers and document where you stand. React and Next.js apps are our home ground.
Fixed quote after an audit or code review. Don't know where you stand yet? Start with an audit from $499.
What's included
Fixed scope
Quoted after an audit or code review
We work from an audit (ours or one you already have), fix in order of impact, and retest every fix before we call it done.
- Code-level fixes for WCAG 2.2 AA failures, blockers first
- Remediation of your component library, so fixes carry to every page
- Accessible rebuilds of legacy front ends in Next.js, when patching costs more
- Retest with keyboard, VoiceOver and NVDA after every round
- Accessibility statement and conformance documentation for procurement
- Automated checks in CI and guidelines so issues stay fixed
Sound familiar?
You got a demand letter
A lawyer says your site fails WCAG. You need real fixes and a record of them, fast, not a widget.
An audit found hundreds of issues
You have the report. Your developers are on the roadmap, and the backlog is not getting smaller.
A deal or the EAA needs proof
Enterprise procurement wants an accessibility conformance report, or you sell into the EU, where the European Accessibility Act has applied since June 2025.
The overlay did not fix it
You installed an accessibility widget and the scans and complaints kept coming, because the problems are in the code underneath.
How it works
- 01
Audit or code review
We start from an audit, ours or yours, or review your code to size the work.
- 02
Fixed-scope plan
What gets fixed, in what order, whether patching or rebuilding is cheaper, and one price.
- 03
Fix in rounds
Blockers first: anything that stops a keyboard or screen reader user completing a task.
- 04
Retest and document
Every fix retested by hand, then a conformance summary and accessibility statement.
What we fix
Most accessibility failures fall into these groups. Each item is tied to the WCAG success criterion it fails, so you can match fixes to your audit.
Keyboard and focus
- Everything reachable and usable without a mouse (2.1.1)
- Visible focus on every control (2.4.7)
- Logical focus order in menus, dialogs and forms (2.4.3)
Forms and errors
- Visible, connected labels on every field (1.3.1, 3.3.2)
- Errors that say what went wrong and how to fix it (3.3.1, 3.3.3)
- Status messages announced to screen readers (4.1.3)
Custom components
- Dialogs, menus, tabs and comboboxes with correct roles and states (4.1.2)
- Focus trapped and restored in modals
- Drag and drop with a keyboard alternative (2.5.7)
Visual design
- Text and UI contrast (1.4.3, 1.4.11)
- Layouts that survive 200% zoom and reflow (1.4.4, 1.4.10)
- Colour never the only signal (1.4.1)
Content and media
- Useful alt text, empty alt on decoration (1.1.1)
- Captions and transcripts (1.2.2)
- Headings and landmarks that describe the page (1.3.1, 2.4.6)
Guardrails
- Automated checks in CI so fixed issues stay fixed
- Accessible patterns in your component library
- Guidelines your team can follow on new work
Three ways to fix accessibility
Only two of them change the code that fails. Here's how they compare.
| Approach | Best for | Watch out for |
|---|---|---|
Overlay widget A script tag that promises instant compliance | Nothing on its own. It can add a toolbar, but it cannot fix your markup, labels or keyboard behaviour | The underlying issues stay in your code. In 2025 the FTC ordered overlay vendor accessiBe to pay $1 million over claims that its tool made sites compliant |
Your team fixes from an audit Audit report plus in-house developers | Teams with front-end capacity who want to learn the patterns | Remediation competes with the roadmap, and fixes without a retest often miss the edge cases |
Code-level remediation Specialists fix the code and retest | A deadline (a demand letter, a deal, the EAA), a large backlog, or a component library everything depends on | Needs access to your repository and a review of each fix by your team |
Want to see what you're dealing with first? Our free accessibility checker scans any URL, and our WCAG AA checklist covers every criterion.
Why fix the components first
In a modern React or Next.js app, most pages are built from the same few dozen components.
One fix
to a shared button, input or dialog corrects that failure on every page that uses it
Blockers first
anything that stops a keyboard or screen reader user finishing a task gets fixed before cosmetic issues
Retested
by hand with a keyboard, VoiceOver and NVDA, because automated scans only catch part of WCAG
We build accessible components for a living: every thefrontkit kit ships WCAG AA components on shadcn/ui and Radix. That's the pattern library we bring to your codebase, whether it uses shadcn/ui, MUI or components your team wrote.
Other ways to work with us
Accessibility Audit Services
Manual WCAG 2.1 AA audits with fixed prices from $499. Audit fees are credited toward remediation.
Learn more →Free Accessibility Checker
Scan any URL for automated WCAG failures in seconds. Free, no sign-up.
Learn more →Custom Builds
Need a new front end rather than a fix? We build accessible SaaS and MVPs in Next.js.
Learn more →Frequently Asked Questions
What remediation involves, cost, overlays, timelines and WCAG versions.
Accessibility remediation is fixing the issues that make a website or app fail accessibility standards such as WCAG 2.2 AA. It means changing the code: adding labels, fixing keyboard and focus behaviour, correcting roles and states on custom components, raising contrast and restructuring content. Good remediation ends with a manual retest so you know the fixes work for keyboard and screen reader users.
It depends on how many issues there are and where they live. A handful of shared components can fix hundreds of pages at once, while one-off pages need individual work. We quote a fixed price after an audit or code review, so you know the cost before we start. If you have us do the audit first, the audit fee is credited toward remediation.
You need to know what is broken, so yes, but it does not have to be ours. If you already have a recent audit from another provider, we can quote from it. If you have none, start with our audit from $499, or run our free accessibility checker for an automated baseline.
No. Overlays add a script on top of your page, but they cannot rewrite your markup, fix keyboard behaviour or label your forms, so the underlying failures remain. In 2025 the US Federal Trade Commission ordered overlay vendor accessiBe to pay $1 million over claims that its product made websites compliant.
Small sites with a focused set of issues can be fixed in a couple of weeks. Larger apps usually run in rounds over one to two months, blockers first. If you have a deadline, such as a demand letter response date or a procurement review, tell us on the first call and we'll plan around it.
Yes. When a legacy front end would cost more to patch than to replace, we rebuild it in Next.js with accessible components from the start, and connect it to your existing API. We'll tell you after the review which option is cheaper for your app.
Target WCAG 2.2 AA for new work. It is the current version and adds criteria such as minimum target size, focus not obscured and accessible authentication. Many laws and contracts still reference 2.1 AA, and meeting 2.2 AA also meets 2.1 AA.
Get your site to WCAG AA and keep it there
Start with a 15-minute call about your site, your deadline and any audit you already have. Fixed quote after the review.
Book a 15-min call