Glossary · Accessibility term

Remediation

Remediation is the work of fixing the accessibility problems an audit found, in the code, the content and the design, until the failures are gone. An audit tells you what is broken and why. Remediation is what makes it work, and the two are usually bought separately because they are two different jobs. One thing to know before you plan it. Conformance is judged a whole page at a time. Nine fixes out of ten leaves that page exactly where it started as far as a claim goes, if the tenth is a failure at the level you are claiming, however much better the page is to use. The order that works is by user impact first, in your own code rather than under a widget layered on top, and then retested.

In practice

Two orderings exist and they do not agree, so the first decision is which one you are following. Ask screen reader users which twelve things cause them the most trouble and CAPTCHA comes first by a clear margin. Controls that do not behave as expected and links that make no sense come next. Measure which failures actually appear on real home pages and low contrast text leads, on more than four pages in five, and it is not on the list of twelve problems those respondents were asked to rank at all. Frequency and impact are different orderings, and neither list is the other's answer. Ranking by WCAG level instead of either one is the mistake, because a Level AAA failure blocking checkout can matter more than a Level A failure in your footer. Judge the blocked task, not the letter.

The volume data holds a shortcut. Six error types account for almost all the failures a machine detects across the top million home pages, and they have been the same six for seven years. Low contrast text, missing alt text, missing form labels, empty links, empty buttons, and a page that never declares its language. Fix those six in your templates and most of your count disappears, which is not the same as being finished and is the right place to start.

Fix at source, not under a widget. Work done in your own codebase is work you own, and a later release can still undo it, which is why retesting is not optional. Repairs applied by a vendor's script at page load are rented, and they stop the day you stop paying, because your source was never changed. There are also whole categories automated repair does not reach reliably, including text alternatives for images, form labeling and error handling, and keyboard access, plus formats it does not touch at all.

Retest, and expect to keep retesting. Conformance is a claim about specific pages at a moment, and the average home page grew 22.5% more elements in the year to February 2026. On a site that ships weekly, remediation is not a project with an end date, it is a thing your process either holds or loses.

If you work in federal technology, sequence carefully. Existing systems that met the earlier Section 508 standards and have not been altered since January 18, 2018 do not have to be brought up to the current one. Alteration is a defined word there rather than any edit at all. It means a change affecting interoperability, the user interface, or access to information and data, so fixing a typo is not one, and the components you did alter are what comes into scope.

Why it matters

Remediation has to be finished rather than merely improved, and that is what makes the standard feel unreasonable to somebody who has just done a great deal of work. So the honest scope conversation belongs before the work rather than after it. The wider picture argues the same way. Detected failures rose across the top million home pages in 2026, ending six years of slow improvement, and the researchers' own reading is that heavier frameworks and AI-assisted code are the likely reason rather than the proven one. Remediation is turning into something a process has to hold rather than something a project finishes.

The order that works

Fix the template before the pages. One header component usually carries the same defect across every page on the site. One change then closes hundreds of findings, and the report shrinks in a way that looks implausible until you see where the defect lived.

Where this shows up on the site

Related terms

Knowing the word is the easy part.

Find out where your own site stands. The free scan checks 10 pages in a real browser against all 90 supported automated rules, separates 27 best-practice checks from its WCAG findings, and names the rule behind every result.

Run the free scan