Accessibility Remediation

We fix the code, so the fix lasts.

An audit tells you what’s broken. Remediation is where it gets repaired — in your actual source code, by a developer, then re-tested to confirm it’s genuinely resolved. Nothing layered on top. Nothing that disappears when a subscription lapses.
The overlay problem

A script on top doesn't fix what's underneath.

Overlay widgets promise compliance from one line of code. It’s an appealing offer, and it’s why thousands of small businesses installed one. But an overlay doesn’t change your website. It loads on top of it and tries to patch problems in the visitor’s browser — guessing at labels, rewriting structure on the fly, adding a toolbar. Your underlying code stays exactly as broken as it was.

The consequences are practical, not theoretical. Screen-reader users frequently report that overlays make sites harder to use, not easier — some install browser extensions specifically to block them. Businesses running overlays have continued to receive accessibility lawsuits. Regulators have taken action against overstated compliance claims in this market. And the moment the script fails to load, or the subscription ends, every “fix” vanishes at once.

Source-code remediation
Overlay widget

Who it’s for

This is for you if…

You have an audit report and need someone to actually implement the fixes.
You had an audit done elsewhere and your developer is stuck or unavailable.
You installed an overlay widget and want real fixes underneath it.
You’ve received a demand letter and need documented remediation work, fast.

We’re happy to work from another vendor’s audit — you don’t need to buy ours first. If the report is thin or unclear, we’ll tell you honestly what’s missing before we quote.

What we fix

What actually gets repaired.

Every fix is made in your source code and verified against the relevant WCAG 2.2 Level AA success criteria.

Semantic HTML structure

Real headings, landmarks and elements, so assistive technology understands your page.

ARIA, used correctly

Added where it genuinely helps, removed where it’s doing harm. Bad ARIA is worse than none.

Keyboard accessibility

Every menu, form and control operable without a mouse, with no traps.

Focus management

Visible focus, logical order, and focus that lands where it should in menus and modals.

Forms and error handling

Proper labels, clear required fields, and errors that are actually announced.

Navigation and menus

Dropdowns and mobile menus that work for keyboard and screen-reader users.

Color contrast

Text and interface elements corrected to meet AA, without wrecking your brand.

Images and alternative text

Meaningful descriptions written by a person, decorative images correctly hidden.

Interactive components

Accordions, tabs, modals and carousels rebuilt to behave properly.

Headings and document structure A logical outline, so people can navigate by heading instead of guessing.
How we work

How remediation works.

Review your audit

We read your report — ours or someone else’s — and confirm what’s in scope.

Fixed quote

You get a written estimate with a clear scope, before any work starts. No hourly surprises.

Fix in source

We work through the issues in priority order, in your actual codebase, on a staging environment where possible.

Re-test each fix

Every fix is verified with a keyboard and screen reader, not just marked done.

Handover

You get a completion report showing each issue, what changed, and how it was verified.
Before & after

What a real fix looks like.

Three common issues, and what changes in your code.
WCAG 2.2 · 4.1.2

A clickable div used as a button

No keyboard access and no accessible name — a keyboard or screen-reader user can't activate it.

Before

<div class="btn"
  onclick="go()">Menu</div>

After

<button type="button"
  onclick="go()">Menu</button>

What changed: a real button element — focusable, and operable with Enter and Space.

WCAG 2.2 · 1.1.1

An image link with no alt text

A screen reader announces only the file name — "IMG_4821 dot jpg" — instead of the destination.

Before

<a href="/menu">
  <img src="IMG_4821.jpg">
</a>

After

<a href="/menu">
  <img src="IMG_4821.jpg"
    alt="View our menu">
</a>

What changed: meaningful alt text, so the link's purpose is announced.

WCAG 2.2 · 3.3.2

An input with a placeholder, no label

The placeholder vanishes on typing, and a screen reader announces the field as blank.

Before

<input type="email"
  placeholder="Email">

After

<label for="email">Email</label>
<input type="email" id="email">

What changed: a real, persistent label tied to the field.

Why NexoBee

Fixed by a developer, not a ticket queue.

Remediation goes wrong when the person writing the report and the person touching the code never speak. Khokon has spent 15 years building websites for clients across the US and EU, and audits ADA accessibility professionally — including remote work with a Los Angeles agency. The same person who identifies the issue implements the fix and verifies it, which is why nothing gets lost in translation.

Pricing

Priced by the work, quoted before we start.

Remediation cost depends on what the audit found and how your site is built. So we quote it properly rather than guessing at a package price.

Focused fixes

From $450
The Critical and Serious findings first, up to 10 fixes on a small site. Every fix is rechecked and your report is updated, at no extra cost.

Full small-business

From $950
A complete pass through every audit finding on a brochure or booking site of up to 15 pages. Every fix is rechecked and your report is updated, at no extra cost.

Complex or e-commerce

Custom quote
Multiple templates, checkout flows, and third-party components.

Every quote is fixed scope and fixed price, written down before work begins. If the audit reveals your site is so structurally broken that fixing it costs more than rebuilding it, we’ll tell you that instead of quietly billing the hours.

Who builds it

Built by one developer, not handed down a chain.

Khokon has spent 15 years building websites for clients across the US and EU, and audits ADA accessibility professionally — including remote work with a Los Angeles agency. On a rebuild you work with the person doing the work, which means accessibility decisions get made by someone who understands both the code and the people it locks out.
Khokon

FAQ

Frequently asked questions.

You need a report of some kind, but it doesn’t have to be ours. We’re happy to work from another vendor’s audit. Without one, we’d be guessing — so if you don’t have a report yet, start there.
You can, and it’s cheaper. But it doesn’t change your source code, so the barriers remain underneath — and overlays are still being cited in lawsuits. When the script fails or the subscription ends, every ‘fix’ disappears at once. Real remediation lives in your site and stays there.
Almost certainly. We work with WordPress, custom-built sites, and most common site builders and frameworks. If there’s a real constraint, we’ll tell you before you commit.

Rarely in any noticeable way. Most fixes are structural — in the markup and behavior, not the visual design. Where a contrast fix is needed, we adjust colors carefully to meet AA while staying true to your brand.

Every fix is re-tested with a keyboard and a screen reader, not just marked done. You get a completion report listing each issue, what changed, and how it was verified.
No, and be cautious of anyone who promises that. We fix what’s in scope against WCAG 2.2 Level AA and document it, which meaningfully reduces your risk. But no vendor can guarantee compliance or immunity from a lawsuit.
We’ll tell you honestly. If the audit shows fixing your site would cost more than rebuilding it accessibly, we’ll say so rather than quietly billing the hours — and a rebuild might be the better investment.