Table of Contents
- Why Doesn’t WCAG Tell You What to Fix First?
- Filter 1: Is It a Barrier or a Recommendation?
- Filter 2: Is the Issue Global or Page-Specific?
- Filter 3: How Severe Is It, and How Many People Does It Affect?
- Filter 4: How Visible Is the Page and How Critical Is the Task?
- Batch the Quick Wins
- Track, Retest, and Document Your Progress
- What Not to Do
- Your Accessibility Remediation Priority Checklist
- Frequently Asked Questions
- Have an Audit and Don’t Know Where to Start?
Your accessibility audit just landed in your inbox. You open it, start scrolling, and keep scrolling. Twenty issues. A hundred issues. Maybe more. Where do you even start?
An audit tells you what’s wrong. It typically doesn’t tell you what to fix first. In this guide, I’ll walk you through the method we use, which I call the Remediation Triage Funnel: four filters that turn an overwhelming report into an actionable plan you can actually work from.
Key Takeaways
- Separate WCAG barriers from best practices first. You may find more than half the issues weren’t barriers in your target level.
- WCAG doesn’t define a severity scale, so translate every auditor’s labels into one consistent scale before you plan.
- Fix global issues (header, navigation, footer, templates) first. One fix repairs every page that uses them.
- Rank what’s left by severity and number of people affected, starting with high-visibility pages and critical tasks like forms and payments.
- Track, retest, and document every fix. Your remediation record is your evidence of good-faith progress.
Why Doesn’t WCAG Tell You What to Fix First?
WCAG tells you what conforms and what doesn’t. It doesn’t tell you what to fix first. The Web Content Accessibility Guidelines sort success criteria into three conformance levels (A, AA, and AAA), but those levels describe conformance, not urgency. A Level AA contrast failure on your bill pay button can hurt more people than a Level A issue buried on an archived page.
So auditors create their own severity scales. Most use four levels. Ours are Critical, Serious, Moderate, and Minor, which match the impact labels used by the popular axe testing engine. I’ve also seen High, Medium, and Low. Neither approach is wrong. The trouble starts when you’re comparing reports from different vendors, or this year’s audit from Vendor A to last year’s audit from Vendor B.
Before you plan anything, translate every issue into one scale. Here’s how the most common labels line up with ours:
| Our level | What it means for the user | Other labels you’ll see | Typical examples |
|---|---|---|---|
| Critical | Blocks a task completely. No workaround. | High, Blocker, Severe | Mobile menu can’t be opened with a keyboard; submit button has no accessible name |
| Serious | Major difficulty. Many users will give up. | High, Major, Significant | Form fields without labels; focus outline removed in CSS; low-contrast body text |
| Moderate | Frustrating or slow, but a workaround exists. | Medium | Skipped heading levels; vague “read more” links |
| Minor | A technical failure with limited impact. | Low | Decorative image announced with unnecessary alt text |
| Not a barrier | Improves the experience; not a WCAG failure at your target level. | Best Practice, Advisory, Recommendation | Content outside page landmarks; AAA criteria when your target is AA |
Filter 1: Is It a Barrier or a Recommendation?
Recommendations or best practices are suggestions that improve the user experience but don’t fail a WCAG success criterion at your target level. They’re worth doing eventually. They’re not where your remediation budget goes first.
Here’s how to sort them quickly:
- Does the issue cite a specific success criterion, like 1.4.3 Contrast (Minimum)? It’s probably a barrier.
- Is that criterion at your target level, usually WCAG 2.1 or 2.2 AA? If it’s AAA, it’s an enhancement, not a requirement.
- Is it labeled best practice, advisory, or recommendation with no criterion? Park it.
Move best practices to a separate list. Don’t delete them, just revisit them once the barriers are gone. In a 26-issue audit we received, this one step cut the working list down to 8.
Filter 2: Is the Issue Global or Page-Specific?
Most audits group findings as global (sitewide) or by page. Use that grouping because it’s the single biggest shortcut in remediation.
Global issues live in shared components: the header, navigation, footer, search, cookie banner, or page templates. Fix the component once and every page that uses it improves. A keyboard trap in your mobile menu isn’t one issue. It’s an issue on every page of your site.
That’s why global issues with the highest severity are where we start every remediation project. The global barriers we find most often:
- Mobile menus that let focus escape to the page behind them
- Hidden submenus that still receive keyboard focus
- A missing skip link
- Focus outlines removed in CSS with no replacement
Filter 3: How Severe Is It, and How Many People Does It Affect?
Now rank the remaining barriers by two questions together:
- Severity: Can the user still complete the task?
- Reach: How many users and how many pages does it touch?
A Moderate issue on every page can outrank a Serious issue on one archived page. Here’s the simple grid we use:
| Severity Level | Affects many pages or users | Affects few pages or users |
|---|---|---|
| Critical or Serious | Fix now | Fix next |
| Moderate or Minor | Schedule it | Batch it later |
Keyboard and screen reader blockers almost always land at the top. If someone can’t reach or operate a control, nothing else on that page matters to them. Not sure how an issue behaves for those users? Our phased approach to testing your website for accessibility walks through keyboard and screen reader checks step by step.
Filter 4: How Visible Is the Page and How Critical Is the Task?
Start with your highest-visibility pages. Your homepage is the obvious first stop: it’s usually your most visited page, and it’s the first page a frustrated user, or a complaint reviewer, will see. Then pull your top ten pages from analytics.
For government agencies, municipalities, and special districts, high visibility also means high stakes. Prioritize the pages where people complete essential tasks:
- Paying a bill or setting up autopay
- Board agendas, minutes, and public notices
- Service requests and contact forms
- Emergency alerts, outage notices, and boil-water advisories
- Rates, fees, and permit information
Don’t forget the documents. The PDFs attached to these pages are part of the task. If the bill pay page is accessible but the autopay form is an inaccessible PDF, the task still fails.
Batch the Quick Wins
Some fixes take minutes and can be handled by content editors instead of developers. Bundle them so they don’t sit in line behind complex development work:
- Vague link text. Replace “click here” and “read more” with descriptive links. Here’s why “click here” is an accessibility problem.
- Missing or unhelpful alt text. Start with your most visited pages. See writing effective alt text.
- Decorative images that get announced. Learn the difference between decorative vs. meaningful images.
- Videos without captions. Our guide to accessible video covers captions, transcripts, and audio description.
Assign quick wins to your editors while developers tackle the global components. Two tracks running in parallel move a lot faster than one long queue.
Track, Retest, and Document Your Progress
Remediation isn’t done when the code changes. It’s done when the fix is verified. For every issue, track:
- The WCAG success criterion
- Where it lives (global component or specific page)
- Severity, using your translated scale
- Who owns the fix
- Status, date fixed, and date verified
Retest each fix the same way it was found. If the auditor found it with a keyboard or a screen reader, verify it with a keyboard or a screen reader.
For public entities, that record matters as much as the fixes themselves. If a complaint arrives, the question isn’t just whether your site is accessible today. It’s what you knew, when you knew it, and what you did about it. A dated remediation record supports your digital accessibility policy and your obligations under laws like Colorado HB21-1110.
This is exactly why we built the Ally Ocean Compliance Hub. You can import an audit from any vendor as an Excel or CSV file, match its columns during upload, and assign severity by criterion, so mismatched scales finally line up. Every status change and note is dated, and between audits it keeps scanning for new issues automation can detect.
What Not to Do
- Don’t fix issues in report order. Page one of the audit isn’t priority one.
- Don’t treat an automated scan’s score as proof of compliance. Scanners only catch a portion of WCAG issues, and they can’t judge whether alt text or focus order actually makes sense.
- Don’t install an overlay and call it done. Here’s why accessibility overlay widgets aren’t the solution and end up doing more harm than good.
- Don’t stop at the audit. Every new page, PDF, and plugin update can introduce new barriers. An audit is a snapshot, not a finish line.
Your Accessibility Remediation Priority Checklist
Bookmark this list or print it and keep it next to your audit.
Before you start
- Confirm your target standard (WCAG 2.1 AA or WCAG 2.2 AA)
- Put every issue in one list, whether that’s a spreadsheet or a tracking tool like the Ally Ocean Compliance Hub
- Translate every severity label into one consistent scale
Triage
Remediate
Verify and document
Frequently Asked Questions
Do I have to fix best practice issues?
Not to conform with WCAG. Best practices don’t fail a success criterion at your target level. They do improve usability though, so fix them after your barriers are resolved.
What if my audit doesn’t include severity ratings?
Assign them yourself. Ask whether someone using a keyboard or screen reader can still complete the task. If they can’t, it’s Critical. If they can with real difficulty, it’s Serious. Everything else is Moderate or Minor.
Can an automated scan prioritize issues for me?
Only partly. A scanner can sort its own findings by impact, but it can’t evaluate issues it can’t detect, like confusing focus order or misleading alt text. A manual evaluation is still needed to find and rank the full list.
How long does accessibility remediation take?
It depends on the size of your site, how many issues are global, and whether fixes need a developer or an editor. Fixing global components first usually resolves a large share of issues quickly. Plan in phases, and document as you go.
Accessibility requirements and enforcement can vary by jurisdiction. This article reflects general WCAG best practices and is not a substitute for legal or regulatory guidance.
Have an Audit and Don’t Know Where to Start?
We remediate from any auditor’s report, ours or a third party’s. With the Ally Ocean Compliance Hub, you can import that audit, track every fix, and keep a dated record of your progress. Book a Compliance Hub demo → or learn more about our accessibility services →
