3 minute read

Roles and Responsibilities

Accessibility isn’t one person’s job.  It takes a team, and everyone’s role looks a little different.

You don’t have to be an expert to make a difference. Just start where you are, with the work you already do.

This isn’t a perfect list.  But it is a practical one.

Designers

You shape what people see – and what they miss.
Use your power to guide, not to confuse.
Build with structure first. Let visuals follow function.
Don’t rely on color alone. Make sure focus states are clearly visible.
Ask how something will work with a keyboard, not just how it looks on a screen.
And when you get feedback from someone using assistive tech? Take it seriously. That’s a gift, not a complaint.

Developers

You’re building more than components – you’re building access.
Accessibility isn’t extra code. It’s the right code.
Use semantic HTML. Handle focus. Test with a keyboard.
Don’t just follow the design – question it when it leaves people out.
Your work shapes whether someone can complete a form, navigate a menu, or even know a button is there.
You have the power to make it work for everyone. Use it.

QA, Support, and Analysts (Connectors)

You see what breaks first. You hear what frustrates users. That makes you the early warning system.
Log patterns, not just one-offs. Speak up when complaints repeat.
If something breaks when zoomed, fails keyboard nav, or causes user confusion – flag it.
You’re not just catching bugs. You’re spotting cracks in the foundation.
Don’t underestimate your power.

Content Creators

Words are interfaces. They shape understanding, trust, and action.
Use clear language. Write meaningful link text. Describe images thoughtfully.
Structure your content for everyone, not just those skimming visually.
And remember: if your message doesn’t reach people, it doesn’t work.

Product managers and team leads

You control how the work gets scoped – and what gets cut.
If accessibility only shows up in QA, it’s already too late.
Make it part of the plan, the sprint, and the definition of done.
Push back when timelines cut corners. Celebrate when someone catches an issue.
Track invisible labor and protect the people doing the work.
Your priorities ripple through the team. Make sure they say: accessibility matters.

Leadership

This is where culture either sticks or collapses.
Back accessibility publicly. Fund it before it becomes a crisis.
Tie it to performance reviews and delivery goals.
Hold teams accountable – don’t reward delivery at the expense of inclusion.
Ask about it in check-ins. Share wins, not just lawsuits.
And when the pressure hits? Protect the work and the people doing it.
Lead like it matters – because your priorities become theirs.

Everyone

You don’t need a job title to care.
If something feels wrong, say something.
If you see a pattern, flag it.
Ask questions. Share what you’ve learned. Help the next person do it better.
You don’t have to be an expert. You just have to start.
Because accessibility isn’t a role.
It’s a responsibility.

Previous articleNext article
Back to top