Authentic conversations so far...

Every Saturday, an email in your inbox where I look at how my accessibility journey has been over the past week.

Small changes can have far-reaching impacts in accessibility. It's like dominoes. One piece leads to another piece leads to a better world.

We constantly miss opportunity because it looks like work. Chances are handed to us, but we need to do the work to turn them into something.

The differences between just-in-time and just-in-case knowledge and how they apply to accessibility.

In the short run, cutting out accessibility seems like a smart move. But on the long run, dumping accessibility will almost always fail.

Some things simply require patience and time to unfold properly. Few things can be rushed. Accessibility is not one of them.

If you want to learn how to swim, you need to get in the water. If you want an accessible website, you need to dig in to it.

The destination of an accessible web is noble. But the path we take to get there matters a whole lot more.

When everything is rushed, it'll be people who suffer the consequences. Don't slow down. Hurry up! Just don't rush!

Treat accessibility not as a one-and-done checklist item, but as an ongoing practice you'll develop and uphold.

Are you going to wait until accessibility issues pile up in your backlog or are you going to plan time for it in each sprint?

Accessibility has a price. Not being accessible has a cost. Either way, you will pay.

Accessibility looks difficult. Until we start looking. Until we start to give a shit about making things usable for everyone.

Being in a wheelchair, or using a cane, we need to have certain adjustments made to our environment in order to function properly.

Forget the jargon, the technical details and the laws. Accessibility is about creating experiences that work for everyone.

Those that believe accessibility is important will fill in the gaps. The ones that prioritise it in their organisations will lead the pack.

If I think accessibility is a human right, if I treat it as a priority, then it's only normal and expected, that others will do the same.

Ask 3 questions to understand why your backlog is teeming with accessibility issues.

One lesson I've learned throughout the last 10 years of my career is never to force change in others.

Throughout the development process, the product owner needs to act as the champion for accessibility.

Having the accessibility roadmap counts for little without actually making the journey.

Some rules are legal, written down, codified and enforced. Some rules are informal. You are expected to behave a certain way.

Accessibility can't be siloed. It requires a shared commitment across teams.

What can you do when clients say that they can't comply with colour contrast requirements because it's not their brand.

We need rules to play the game and we need the WCAG to guide us. But don't take it as the bible, use it as a playbook, a strategic resource.

If you eliminate the surprise and plan for different circumstances your website might be used, your frustration levels will go down.

Here are 10 key steps that have worked for me to ensure accessibility in my website development process.

You can have an accessible website without blocking ongoing work and without paying an arm and a leg. But why would you want one?

You can't outsource accessibility because you can't outsource responsibility.

If you plan accessibility from the start, you'll have little impact on your budget.