how-to
What the Website Remediation Process Actually Involves
Last Updated: November 6, 2026
Quick Summary
Website remediation is the structured process of finding and fixing the barriers that stop people from using a website, then proving the fixes work. We run it as a five-step cycle: scope the site and assign owners, combine automated scanning with manual testing, log findings and fix by severity, verify fixes with assistive technology, and lock in regression checks.
- A useful audit tests against WCAG and pairs automated scanning with manual checks by a person.
- Automated tools catch only a portion of real barriers; the rest surface through manual testing.
- Score each finding on user impact, severity, effort and risk so the fix order is defensible.
- Fix the source template or component, not just the live page, or the next content update reintroduces the barrier.
- Add accessibility checks to your publishing checklist so new pages ship clean.
Table of Contents
- What Website Remediation Means in Practice
- Why Remediation Matters Beyond Compliance
- How a Website Accessibility Audit Surfaces Real Barriers
- Step-by-Step: The Website Remediation Process
- Building an Accessibility Remediation Plan Your Team Can Run
- Setting a Realistic Accessibility Remediation Timeline
- Accessibility Remediation Best Practices That Hold Up
- Book a Remediation Assessment for Your Site
- Frequently Asked Questions
What Website Remediation Means in Practice
Website remediation is the structured process of finding and fixing the barriers that stop people from using a website, then proving the fixes work.
The core idea is simple. A site is not "done" when the code changes.
That distinction matters because most sites drift out of shape over time. New pages get published, plugins get updated, and old fixes quietly break.
Why Remediation Matters Beyond Compliance
Compliance is the floor, not the ceiling. The stronger reason to remediate is that accessibility barriers cost you real users and real revenue.
Consider what a barrier actually does. A form field with no label is invisible to a screen reader.
The legal side still matters.
We tell clients the same thing every time: fix for the user first, and compliance tends to follow.
How a Website Accessibility Audit Surfaces Real Barriers
A website accessibility audit is a structured review that tests a site against recognized standards and records every barrier it finds, with enough detail that a developer can reproduce and fix it. The output is not a pass/fail grade. It is a findings register your team can schedule, assign, and verify.
The audit is where the remediation process starts, because you cannot fix what you have not found. A useful audit does five things:
- Tests against the Web Content Accessibility Guidelines (WCAG), the standard most legal frameworks point to, at the conformance level your organization has committed to
- Combines automated scanning with manual checks by a person using a keyboard and assistive technology
- Samples templates and high-traffic journeys rather than only the home page, since one broken template can affect hundreds of pages
- Records each issue with its page or component, the WCAG success criterion it fails, its severity, and the user group it affects
What automated scanning can and cannot catch
Automated tools are fast and consistent, and they are worth running first. They reliably flag things like missing form labels, images with no alternative text attribute, insufficient color contrast in many cases, and duplicate IDs.
A common pattern is to treat a clean automated scan as proof of accessibility. It is not. Automated tools catch only a portion of real barriers, and the remainder surface only through manual testing.
Scoring findings so the fix order is defensible
Every finding gets a score before it gets a date. A transparent method beats a gut-feel ranking because it survives scrutiny from legal, product, and engineering at the same time. We score each issue on four factors:
- User impact: does the barrier block a task entirely, make it harder, or cause annoyance? A form that cannot be submitted by keyboard is a blocker; a slightly small tap target is friction.
- Severity: how many users and which journeys are affected? A broken header menu affects everyone; a single buried PDF affects few.
- Effort: is this a content edit, a component fix, or a platform change? Effort drives sequencing, not priority on its own.
- Risk: is the issue on a regulated journey, a public-facing service, or a page named in a complaint or procurement requirement?
Multiply impact and severity to set the priority tier, then use effort and risk to order work within that tier. The result is a ranked list where the top of the register is defensible in writing, not just in a meeting.
If you want to run or commission your own review, our website accessibility audit checklist walks through the checks we use, including the manual tests scanners miss.
Step-by-Step: The Website Remediation Process
Here is the workflow we run, in order. Skipping a step is how remediation projects stall halfway.

Step 1: Scope the site and assign owners
List every page, template, and component that matters, then name one person accountable for each area. Group by template and component rather than by page, because fixing a shared header or form component resolves the same barrier everywhere it appears. A named owner per area turns a findings list into a schedule. Most stalled projects fail here: nobody owns the fix, so nobody ships it.
Step 2: Combine automated scanning with manual testing
Run a scanner across the site to build a fast baseline, then test the high-traffic journeys by hand with a keyboard and a screen reader. Automated scans set the floor; human testing finds the ceiling. Test the journeys that matter most, such as sign-up, checkout, search, and account recovery, because those are where a barrier costs the most.
Step 3: Log findings and fix by severity
Record every issue in one shared register and rank each by user impact, severity, effort, and risk. Fix the blockers first: the issues that stop a task completely, like a form that cannot be submitted by keyboard or a dialog that traps focus. Cosmetic issues can wait. Concrete fixes at this stage look like the following:
- Keyboard access: a custom dropdown that only responds to a mouse is rebuilt to open with Enter or Space, move with arrow keys, and close with Escape, with visible focus.
- Form labels: an input identified only by placeholder text gets a persistent visible label tied to the field, so screen readers announce it and the label does not vanish on typing.
- Headings: a page that styles text to look like headings without using heading markup is corrected so the heading structure is real and navigable.
- Contrast: text that fails the contrast ratio is adjusted at the design-token level so the fix propagates rather than being patched page by page.
- Alternative text: decorative images are marked as decorative, and meaningful images get descriptions written as part of the content step.
Watch out: fixing issues in the live page without updating the template or component means the next content update reintroduces them. Fix the source, not just the page.
Step 4: Verify fixes with assistive technology
Re-test every fix with the same tools a real user would use: keyboard only, a screen reader, and zoomed text. Confirm the barrier is gone, not just that the code changed. Verification is the step teams skip under deadline pressure, and it is the step that proves the work. A fix you have not verified is a guess.
Step 5: Lock in regression checks and ownership
Remediation is not finished when the register is empty. Add accessibility checks to the publishing checklist, keep the shared register open, and re-test the fixed components on a fixed schedule and before major releases. Assign ongoing ownership of new content so the site does not drift back out of shape between audits.
Here is the five-step workflow in order, with what each step involves.
| Step | What to do |
|---|---|
| Step 1 | Scope the site and assign owners |
| Step 2 | Combine automated scanning with manual testing |
| Step 3 | Log findings and fix by severity |
| Step 4 | Verify fixes with assistive technology |
| Step 5 | Lock in regression checks and ownership |
Building an Accessibility Remediation Plan Your Team Can Run
An accessibility remediation plan turns audit findings into assigned work with dates. Keep it short enough that people actually use it.
We build ours around four columns: the issue, the owner, the fix, and the verification date. That is it. Anything more elaborate tends to become a document nobody opens.
Deciding who does the work is the real question. Some teams keep it in-house. Our guide on whether to handle website accessibility remediation in-house lays out the trade-offs.
A common mistake is treating the plan as a one-off project list.
Setting a Realistic Accessibility Remediation Timeline
An accessibility remediation timeline is the schedule that maps each fix to a date and a responsible person.
Plan in phases. Blockers go first, usually within the current cycle. Broader template and CMS fixes follow.
Some factors tend to stretch timelines, such as third-party widgets and legacy systems.
- Third-party widgets you do not control, which need vendor conversations
- Legacy systems with no clean way to update the front end
Build slack for both. Our five-step guide to planning a remediation timeline shows how we sequence the phases.
Accessibility Remediation Best Practices That Hold Up
The accessibility remediation best practices that last share one trait: they build accessibility into the workflow instead of bolting it on at the end.
Start with these:
- Add accessibility checks to your publishing checklist, so new pages ship clean
- Write alternative text as part of the content step, not as a cleanup task
- Test with a keyboard before every major release
- Keep one shared issue log across teams
- Re-audit on a fixed schedule, not only after a complaint
The best practice most teams miss is ownership of new content. Remediation fixes the past. A publishing standard protects the future.
Watch out: fixing issues in the live site without updating the templates means the next content update reintroduces them.
Book a Remediation Assessment for Your Site
The remediation process works best when it starts with a clear picture of where your site stands.
At Elevated Digital, we run remediation as a measured, defensible process. Our step-by-step guide to requesting a remediation quote shows exactly what to send us and what you get back.
If legal exposure is part of your concern, our guide to website remediation for legal compliance covers how the process supports that goal.
A site that fails real users is a site that fails its purpose. If you are not sure where your barriers are, start with an assessment rather than a guess.
Frequently Asked Questions
What are the steps in the website remediation process?
The process runs in four stages. First, scope the site and assign an owner for each section. Second, run an accessibility audit that pairs automated scanning with manual keyboard and screen reader testing. Third, log every finding, rate its severity, and fix the highest-impact issues first. Fourth, retest each fix with assistive technology before closing the ticket. A remediation plan and a realistic timeline sit on top of those steps, and a monitoring routine keeps new issues from piling up after launch.
How long does website remediation take?
It depends on site size, how many templates are in use, and how many third-party widgets you rely on. A small marketing site with a handful of templates can move through audit, fixes, and verification in a few weeks. A large e-commerce site with custom checkout flows and legacy pages often takes several months. The accessibility remediation timeline should be built from the audit findings, not guessed upfront, and it should schedule verification time for every fix rather than treating the fix itself as the finish line.
How do you test a website after remediation?
Retest each fixed element the same way you found it. Run the automated scan again to confirm the rule no longer fires, then repeat the manual check: tab through the page with a keyboard, listen to it with a screen reader, zoom to 200 percent, and confirm form labels and error messages are announced. Testing the fix in isolation is not enough. Check the page in context, because a corrected component can still fail when it sits inside a poorly structured layout or a third-party embed.
How can you prevent accessibility issues from returning?
Fold accessibility into the build process instead of treating it as a one-time project. Add automated checks to your deployment pipeline, require a manual review before new templates ship, and give content editors a short checklist for alt text, headings, and link text. Keep a register of known issues with owners and review it monthly.