11 minutes
From a list of findings to a roadmap Group findings by the barrier and its root cause, rate severity, reach and effort, and sort the work into quick fixes, planned projects and policy changes.
What you’ll be able to do Group audit findings by root cause, rate each group for severity, reach and effort, and sort the work into quick fixes, planned projects and policy changes. Compare the responses to this question and explain your choice: What is the most useful first move? Document a next step for From a list of findings to a roadmap: Group your audit findings by root cause and write each group as a single problem statement about the system, not the person who found it. The list is not the plan Audits produce findings; organizations need decisions. Between the two sits a translation step that many teams skip, which is why so many audit reports are filed rather than acted on. The step has three parts. First, group findings by root cause. Twelve notices with poor contrast, unlabeled form fields and image-only content are one problem: nobody who produces public documents has an accessible template or a check before publishing. Second, rate each group. Third, sort the groups into the kind of work they are.
Rating uses three lenses. Severity : does this barrier stop someone entirely, make the task much harder, or cause friction? A form that cannot be completed with a screen reader stops people. Reach : how many people meet this barrier and how often? A monthly notice to every participant reaches more than an internal page. Effort : what does the fix take in time, money, skill and authority? Prioritize using all three. Effort alone produces a plan of easy things; severity alone produces a plan nobody funds.
Finally, sort. Quick fixes can be done within days by the people who own the thing: turn on captions, add an access line to the invitation, fix the door closer. Planned projects need an owner, a budget and a schedule: replace the kiosk, remediate the form library, procure captioning. Policy changes alter how work is done so the finding does not come back: an accessible-template standard, a check before publication, an accessibility clause in every contract.
Building the roadmap Group findings by root cause and write one problem statement per group about the system.
Rate each group for severity, reach and effort.
Sort each group into quick fix, planned project or policy change; many root causes need one of each.
Order the roadmap with highest severity first, and place quick fixes early regardless of severity to build momentum.
For each line, name the owner, the decision-maker, a date, the budget need and a measure; the next lesson shows how.
Share the draft with the disabled people who took part in the audit before it goes to leadership.
Quick fix, planned project or policy change? Turn captions on by default for every virtual meeting on the division’s platform.
Choose a category Quick fix Planned project Policy change Replace the lobby check-in kiosk with one usable from a seated position and with a screen reader.
Choose a category Quick fix Planned project Policy change Require an accessibility check before any public document is published.
Choose a category Quick fix Planned project Policy change Add an access-needs line and a named contact to the community meeting invitation template.
Choose a category Quick fix Planned project Policy change Remediate the two hundred forms in the program’s document library.
Choose a category Quick fix Planned project Policy change Add accessibility requirements to the standard contract language for purchased software.
Choose a category Quick fix Planned project Policy change Check matches Reset Keep the most excluded at the top What you can change You control the order of the roadmap and therefore whose barriers are fixed first.
What to watch for Do not let cost or convenience push the barrier that stops people entirely to a later phase. Do not present a plan of quick fixes as the plan.
Your next step Check your roadmap’s first phase: does it contain at least one item that removes a barrier that currently stops someone completely?
Rating and sorting Severity
Stops the person entirely, makes the task much harder, or causes friction. A barrier that stops people is always in the first phase, whatever it costs.
Reach
How many people meet the barrier and how often. Public notices and application forms reach more people than internal pages; weigh accordingly.
Effort
Time, money, skill and authority required. A useful tie-breaker and a scheduling input. Never the first sort key.
Root cause
The reason the finding exists: a missing template, no check, no budget line, no owner, a contract without requirements. Fixing findings without root causes means auditing the same thing next year.
Carry this forward Forty findings are often eight problems; grouping by root cause turns a list into a plan.
Severity asks who is stopped entirely; reach asks how many people and how often; effort asks what it takes to fix. Prioritize with all three, and never with effort alone.
Quick fixes build credibility, planned projects need owners and money, and policy changes are what stop the same finding from returning.
A completed sort of six findings and a short list of grouped root causes from your own audit.
Group your audit findings by root cause and write each group as a single problem statement about the system, not the person who found it.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Course overview Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
