Authentic conversations so far...

The number of new accessibility issues your latest release introduced is a critical metric in informing you if you are on the right track.

The purpose of the Goal Rush game is to generate as many user goals as possible that you can later use in the workshop.

Instead of unstructured endless meetings, I advocate for workshops that have a clear process where we uncover accessibility issues together.

This week's 1% is that I've been consistently writing and publishing every day for over 100 days straight.

Web accessibility is a large undertaking and takes time. We need to accept that large tasks take time and that the investment is worth it.

Is there a better way to introduce web accessibility to product teams that doesn't involve dumping a laundry list of issues on them?

There's a difference between not having and not wanting to have disabled users.

Accessibility and responsive web design are two sides of the same coin. They're about adapting experiences to match the needs of the user.

Accessibility is essential in product development. But you won't create a product that works all the time for everyone. And that's ok.

The WCAG provides a clear way to look at accessibility. Its set of principles and criteria are available for all to understand.

A little story about acceptance and commitment.

Don't mistake motion for action. You can be on a hamster wheel and never move forward. Only action leads to accessibility improvements.

It's easy to make promises that describe a distant future and then look at the list of short-term pressures you're already facing.

When your website fails to meet accessibility standards, the different levels of your organisation will start with the finger-pointing.

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

Before you declare accessibility a priority, make sure you have processes in place to make it an integral part of your workflow.

Your inaccessible website forces you into a lose-lose situation, where both you and your customers stand only to lose.

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.