The not-so-simple world of accessibility: Part 3

Enter part 3

Welcome to Part 3 of our accessibility journey. In Parts 1 and 2, we looked at how accessibility intersects with design systems, code, process, and leadership. Now it’s time to talk about the heart of accessibility: people.

Because here’s the truth—no matter how well you know WCAG, no matter how perfect your code is, if real people can’t use what you built, it’s not accessible.

A personal story – When compliance wasn’t enough

I once audited a product that was fully "WCAG-compliant." Every button had a label, all images had alt text, color contrast passed, and the keyboard flow worked. On paper, it was perfect.

But when we tested it with someone who uses a screen reader, things fell apart. The flow was confusing. Content order didn’t match the visual layout. The labeling made sense to developers, but not to people. It passed all the rules, but it failed the people it was supposed to help.

That moment stuck with me. Guidelines are important. But they're not the finish line. They're the starting point. Accessibility lives in human experience.

Elevate the vibe – Guidelines aren't enough

Standards give you structure

WCAG is critical. It helps you measure, guide, and defend accessibility work. But those rules don’t always tell the full story. They don’t tell you if someone felt frustrated. They don’t tell you if a task took five extra steps. They don’t tell you if someone gave up.

Lived experience shows you the truth

People who use screen readers, switch devices, voice control, or magnifiers interact with technology in ways we can’t simulate with a tool. Only they can show us the real pain points—and the moments of joy.

Compliance doesn’t equal usability

You can technically "pass" accessibility and still deliver a frustrating, confusing, or overwhelming experience. Accessibility without usability is like a ramp that leads nowhere.

Self-reflection – Are you designing for checklists or for people?

Ask yourself:

Have I tested my product with real assistive technology?

Have I involved people with disabilities in usability testing?

Am I focused on the rules more than the human experience?

Do I treat accessibility as an outcome, or as a relationship with real people?

If you’re chasing checkboxes, it might be time to slow down and listen.

Vibe in action – Centering accessibility around people

Run inclusive usability studies

Bring people with different disabilities into your research and testing process. Pay them. Respect their time. Learn from them.

Listen more than you explain

Don’t defend the design. Don’t explain what it’s supposed to do. Just watch. Ask questions. Learn what worked and what didn’t. Let the feedback reshape your product.

Build feedback loops with disabled communities

Create regular opportunities to hear from people with lived experience. Build relationships with advocacy groups and accessibility consultants who can tell you what needs to change.

Adjust your metrics

Stop measuring accessibility by "number of violations" and start measuring by human impact. Did the person complete the task? Did they feel confident doing it? Would they come back?

Share the human impact with your team

Tell real stories. Share quotes. Replay usability recordings. Make sure your team hears what the people are saying.

Vibing out

Accessibility isn’t just technical. It’s emotional. It’s human. It’s about trust, dignity, and independence.

If we build for checklists, we might pass the audit. But if we build for people, we change lives.

Let this be your reminder: accessibility starts with empathy, grows with feedback, and thrives in partnership.

Part 4 is coming. We’re not done yet.