RLA Accessibility Audit
Organized by scope, then prioritized by impact
1. How broadly does the issue occur?
Findings are grouped by the reach of the problem.
- Global Multiple websites or systems
Shared issues across sites, when applicable.
- Sitewide An entire website
Issues that recur across the site.
- Page-specific Individual pages
Each page has its own prioritized findings.
Page AOwn findings and prioritiesPage BOwn findings and prioritiesThe same applies to every additional page.
2. How is each group prioritized?
The same ordering applies at every level, including each individual page.
- First: High-impact, easy wins
Important issues that are relatively easy to fix.
- Then: Remaining issues by severity
Critical through minor, within each group.
How findings become a plan
- GroupBy scope
- PrioritizeWithin each group
- PlanAcross findings
3. Every finding includes
WCAG
Relevant success criteria
Severity
Critical-to-minor rating
Human impact
How the issue affects users
Remediation
Clear steps tailored to the audience
4. The report concludes with
Prioritized remediation roadmap
Recommended fixes ordered by priority across the report.
Recommendations to prevent future issues
For example, following up with a plugin developer or providing alt-text training.
What the client receives
A clear path forward: what to fix, why it matters, where to start, and how to reduce future issues.