Use the arrow keys to navigate between menu items.

Who gave you permission to do it?

2 minutes read

Who told you that you could work on accessibility?

Who gave you permission to test with a screen reader?

Where’s your permit? Who said you could solve this?

What? Do you think that accessibility work requires some form of special authorisation? The reality is, you don't need anyone's permission to prioritise accessibility. It's part of the job description. It's already your responsibility.

If you’re the designer, developer, or any stakeholder in a product, you already have the authority to ensure that your product is usable by everyone. You don’t need a special license. And you don't need to ask for permission.

Just start.

Read up on the Web Content Accessibility Guidelines (WCAG). These guidelines are publicly available and meant to be used by anyone creating digital content.

Try out tools and techniques used by people with disabilities. Testing with a screen reader or any other assistive technology is something anyone can and should do. Share your findings, collaborate with others and keep learning.

Solving accessibility issues should be seen as part of good practice in web development. It's just like ensuring your code is secure or your design is user-friendly.

For accessibility, all you need is awareness, empathy and a commitment to inclusivity.

If you're passionate about making digital spaces accessible, don't wait for permission. Go ahead and start.

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.