Authentic conversations so far...

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.

Treating accessibility as solely the developers' responsibility is shortsighted and leads to costly fixes and delays.

Accessibility isn't a feature, it's the foundation upon which we build products and services.

Statistics show that around 15% of the world's population lives with disabilities. This makes people with disabilities the largest minority.

Could we start believing six seemingly impossible things as we tackle accessibility and do this before we have had our morning coffee?

Investing in accessibility features early in the development process saves time and resources down the line.

Accessibility is like flour on a cake. You can't add it after baking the cake and expect a good flavour.

Tackle both small accessibility bugs and those larger tasks with intention and you'll streamline your workflow.

The future is uncertain, but your personal growth is inevitable once you make the leap and face the challenges.

It's hard to work to talk about helping people with disabilities in the abstract, but it's easier to relate to helping just one person.

If you're in charge of shipping an inclusive experience, you run the danger of falling into the trap of waiting for certainty before action.

If you wait long enough, things will take care of themselves. Accessibility isn’t one of those things.

When people confuse terms or don't know what some acronyms stand for, it can be impossible to carry out conversations about accessibility.

There are legitimate instances when speed can come first. I see two, off the top of my head: emergencies and first to market advantage.

Are you truly making your website accessible for everyone by checking the WCAG? Or are you just falling for the illusion of false certainty?

Unless you ship an accessible product, the people you're trying to help will not be able to appreciate all your efforts.