Why We Need to Fix How We Talk About Accessibility Audits (And What to Do Instead)

Clients are tired of getting massive accessibility audit reports that leave them feeling overwhelmed and unsure where to start.

I read this blog post by Karl Groves (the Web Accessibility Viking) and, rather than depressing me, it thrilled me.

Let’s talk about why I agree that this approach isn’t working and, more importantly, what we can do to make accessibility improvements actually happen.

The Problem with Traditional Accessibility Reports

Picture this: You’re a designer or developer who wants to make your product accessible (awesome!). You hire an accessibility consultant, and a few weeks later, you receive a 50-page PDF listing every single issue they found.

cue overwhelm

It’s like being handed a manual written in a language you’re still learning and being told, “Good luck!” Not exactly helpful, right?

There’s a Better Way

What if instead of dropping a massive report in your lap and disappearing, accessibility experts worked alongside your team? Imagine having someone right there in your Jira or GitHub, logging issues in a way that makes sense to your team and helping you prioritize what to tackle first.

Here’s why this matters:

• You get real-time guidance (no more guessing what the report means)
• Your team learns as they go (goodbye, steep learning curve!)
• Issues get fixed faster (because you understand exactly what needs to happen)
• The solutions actually work (because they’re tailored to your specific situation)

What This Looks Like in Practice

Let’s break down what good accessibility documentation actually looks like. Here’s what your team needs to know for each issue:

1. What’s broken? (In plain English, please!)
2. Who does it affect? (Real people, not just WCAG guidelines)
3. How bad is it? (From “fix this now” to “put it on the roadmap”)
4. How do we fix it? (With actual, practical solutions)
5. How do we know it’s fixed? (Clear steps to verify the solution works)

Here’s a quick example:

Issue: Main navigation can't be used with keyboard
Affects: Anyone who can't or doesn't use a mouse 
Severity: Critical (users literally can't use the website)
Fix: Add proper focus states and keyboard event listeners (bonus points if we can say "here's an example...")
Verify: Try navigating with just your keyboard - can you access everything?

Making This Work for Your Team

Here’s the thing: accessibility isn’t just about checking boxes on a compliance checklist. It’s about making your product work for everyone. And that happens through collaboration, not consultation.

Want to make this work for your team? Try these steps:

1. Give your accessibility expert access to your issue tracking system
2. Ask them to document issues as they find them (not in a separate report)
3. Have them join your stand-ups or planning sessions when discussing accessibility
4. Encourage questions and discussion about proposed solutions
5. Make them part of your verification process

The Real Game-Changer

You know what’s really cool about this approach? Your team actually learns accessibility as they go. Instead of struggling to interpret a report, they’re getting hands-on experience fixing real issues with expert guidance.

It’s like having a mentor right there with you, showing you how to think about accessibility and solve problems effectively.

Ready to Make This Happen?

If you’re working on making your products more accessible (and you should be!), here’s what I want you to do:

1. Stop accepting massive PDF reports as deliverables
2. Ask your accessibility consultants to work directly in your project management tools (and give them access)
3. Make accessibility part of your regular development process, not a separate audit
4. Document issues in a way that helps your team learn and grow

Remember: The goal isn’t just to fix current issues – it’s to build a team that knows how to create accessible products from the start. But the team that can integrate with yours and help move accessibility remediation along in a meaningful way, that’s the next best thing!

What’s your experience with accessibility audits? Drop a comment below – I’d love to hear your thoughts!