The fix matters more than the finding.
Anyone can hand you a list of issues; we’re here for the part where they disappear. Labrador remediation takes your audit’s findings and turns them into shipped fixes, written by our developers and reviewed by yours. We stay until the re-test comes back clean.
Get a quote Start with an audit
- <div>+ <button>
What a fix looks like
Most fixes are smaller than you think.
Accessibility remediation has a reputation for rewrites that it doesn’t deserve. Most findings close with a change a reviewer can read in a minute: a real element in place of an imitation, a name on something that lacked one, focus given back to the keyboard. Here are two fixes we make constantly, shown as your developers would meet them.
- <div class="buy-button" onclick="checkout()">
- Buy now
- </div>
+ <button class="buy-button" type="button" onclick="checkout()">
+ Buy now
+ </button>
A div responds to a mouse and nothing else: keyboard users tab straight past it, and a screen reader finds nothing worth announcing. The button version is focusable, announces its role, and works with Enter and Space, no extra script required. One element swap closes two criteria.
- <img src="q3-revenue.png" />
+ <img
+ src="q3-revenue.png"
+ alt="Q3 revenue: up 38% year over year"
+ />
Without a text alternative, a screen reader has nothing to announce but the filename. The fix is a sentence carrying what the image shows, written to give the same takeaway a sighted reader gets. “Chart” would technically pass and help nobody; good alt text is copywriting.
How we work in your codebase
-
Your repo, your rules
We work in branches and open pull requests like any other contributor, following the conventions your codebase already has. Nothing merges without your approval.
-
Our developers, our workload
Labrador’s developers write the fixes; your team’s only job is review. If a fix isn’t to your team’s taste, we rework it until it is.
How it runs
The findings list is the work order.
Every fix maps to a finding, and every finding already carries what a developer needs: the criterion it fails, the evidence, the severity, and a suggested approach. We work in priority order from the walkthrough, so the barriers that lock people out entirely fall first.
Fixes don’t close on our say-so. Each one is re-tested the way the issue was found: by hand, with the same assistive technology, and the finding’s status updates in Labrador (the testing platform we built) as it happens. When the list reads clean, you have the re-test to prove it.
- Modals and dialogs
- Custom dropdowns
- Date pickers
- Carousels
- Forms and error messages
- Focus order
- Color and contrast
- ARIA repair
The price
Scoped from your findings, from $2,000.
Two things set the number: how many findings there are, and how deep each one goes. A missing label is a minutes-long fix; an inaccessible date picker is a component rebuild. Your proposal prices the real list, finding by finding, so you’ll see the whole cost before anything begins.
Remediation typically follows an audit of ours: the findings list is the work order, and we verify each fix the same way we found the issue. If you haven’t been audited yet, that’s where we start: see how an audit runs.
Start a conversation
Say hi (opens chat)
Tell us what your audit found, and we’ll tell you what fixing it takes. Our founding team spans Maine, Wales, and Delhi, so someone’s online through most of your working day. Expect a scoped, fixed-fee proposal within one business day. A call is welcome, never required.