Use the arrow keys to navigate between menu items.

How to help the developers

2 minutes read

The people who build our websites are crucial to making them accessible for all.

I'm talking about those who sit down with a code editor and write the instructions that will later become a web product.

The developers.

If you want improvements in accessibility, getting them on board is a must.

But they can't do it without proper support. The right tools make all the difference.

This is where we come in. We need to recommend systems that are reliable. Tools that do the job without much need for training. Tools that don't get it wrong more often than they get it right.

If you flag non-existent problems, you're creating a nightmare for developers. Nothing damages your credibility faster than having them waste time chasing issues that aren't actually there.

The tools should match your team's skill level too. For developers new to accessibility, automated testing can catch the low hanging fruit straight away. More experienced devs benefit from more advanced tools that build upon their manual testing process.

Helping teams focus on what matters most is essential.

Developers need clear guidance on which accessibility issues are critical and which can wait. Time wasted on low-priority problems or duplicated work demoralises everyone involved.

Give devs reliable tools, match those tools to their skills and help them prioritise effectively.

It's a simple approach. It's just difficult to get right.

Did you enjoy this bite-sized message?

I send out short emails like this every day to help you gain a fresh perspective on accessibility and understand it without the jargon, so you can build more robust products that everyone can use, including people with disabilities.

You can unsubscribe in one click and I will never share your email address.