Authentic conversations so far...

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.

We would do well to shift our focus from disability to ability and potential, and acknowledge the diverse needs and capabilities of people.

When it comes to accessibility, a laser-focused approach is a game-changer. Break it down into manageable chunks and do one thing at a time.

We should ask ourselves what our role was in creating the current situation and how we can change ourselves before trying to change others.

If you don't know where you're going, you'd rather get there quicker. The quicker you get to the wrong place, the faster you can go again.

Accessibility and good design go hand in hand to create a better user experience for everyone. It's not an either-or situation.

Building a culture of accessibility isn’t about complying with regulations; it’s about embracing inclusion as a core value within team.

When you're working on your product, you'll face a lot of pressure and requests. But no one will ask you to be less accessible.

You cannot hold the system accountable without taking any individual responsibility yourself.

Systemic failures arise from gaps in education and deeply ingrained bad practices within teams.