Remediation

Fix it once, in the place it's repeated.

Most accessibility findings aren't hundreds of separate bugs — they're a dozen components rendered across hundreds of pages. Remediation that lands in the design system fixes the whole site at once and stops new pages from reintroducing the same failures.

Why It Matters

Page-by-page remediation never finishes.

The common failure mode is treating an audit as a punch list: fix the 312 flagged pages, declare victory, then publish 40 new pages next quarter with the same broken accordion. Meanwhile the document library keeps growing and nobody revisits the vendor portal.

We sequence remediation by what blocks users, fix at the component and template level wherever possible, and change the authoring and release workflow so conformance holds without a permanent remediation budget.

Signs you need this

  • You have an audit report and no plan for executing it
  • The same findings keep reappearing after each round of fixes
  • Your team knows what's wrong but not how to fix it correctly
  • A deadline or settlement requires demonstrable, dated progress
How Remediation Runs

Five phases, in this order, for a reason.

01

Unblock

Anything that fully prevents a task — keyboard traps, unusable forms, inaccessible navigation — is fixed first, regardless of where it sits in the report.

02

Components

Shared components and the design system are remediated so every template inherits the fix instead of repeating the bug.

03

Templates

Page templates, layouts, and content patterns are corrected: heading structure, landmarks, link text, and focus management.

04

Content

The long tail — alt text, captions, tables, and documents — handled by volume, with authors trained to stop producing more of it.

05

Verify

Every finding retested and closed with evidence, and automated checks wired into the build to catch regressions.

What Gets Fixed

The failures we find in almost every engagement.

Keyboard operability

Custom controls that can't be reached or activated, focus that disappears, modals that don't trap and release focus properly, and skip links that skip nowhere.

Forms and errors

Unlabeled fields, placeholder text standing in for labels, errors signaled by color alone, and validation messages screen readers never announce.

Contrast and visual design

Text and interface contrast below threshold, invisible focus indicators, and layouts that break at 200% zoom or 400% reflow.

Structure and semantics

Heading levels used for size rather than hierarchy, missing landmarks, layout tables, and ARIA applied incorrectly — which is often worse than none at all.

Dynamic content

Cart updates, filter results, and status messages that change silently, plus carousels and auto-playing media with no user control.

Documents and media

Untagged PDFs, scanned forms with no text layer, tables without header associations, and video published without captions or transcripts.

Who Does The Work

We'll fix it, or make your team able to.

Some clients want remediation delivered. Others have a capable development team or an incumbent agency and need specifications, pairing, and verification instead. Both work — what doesn't work is handing a raw findings list to a team that has never implemented an accessible combobox and hoping.

Where a third-party platform owns the failure, we document it precisely, escalate it to the vendor with citations, and build an accommodation path for users blocked in the meantime.

Have a report and no plan? That's the common case.

Send us the findings you already have. We'll tell you what's genuinely urgent, what's a component-level fix, and what a realistic sequence looks like.