Daily emails so far...

Why companies often opt for quick fixes over long-term solutions, and what are the benefits of a proactive approach to digital inclusion.

Re-frame statements that reflect common misconceptions about accessibility into more constructive questions.

This Sunday's joke features product owners constantly postponing accessibility fixes.

A good checklist will yield consistent results, improve the quality of my work, save me time, increase productivity and reduce stress.

Effective accessibility requires deliberate practice. The best at it understand what inclusive design requires.

Signals coming from your customers are the most important indicators of accessibility you can have.

The purpose of the Focus Finder game is to prioritise a list of ideas to just a few you'll explore further.

Seemingly minor design choices have a significant impact on users with various invisible disabilities.

Our design choices on the web have an often-overlooked impact on people with diverse cognitive abilities.

This Sunday's joke features the accessibility police and image alternative texts.

Take what you read, especially online, with a grain of salt.

Meaningful change in accessibility is a journey with countless little baby steps. It's not a single huge step that we need to focus on.

You don't have to build this long-term sustainable solution to every accessibility problem. Sometimes you just need to get it done.

Scoring 100 in the Accessibility section in Lighthouse doesn't mean people with disabilities can effectively use your website.

Reworking inaccessible features is often significantly more expensive and time-consuming than building accessibility in from the start.

Never attribute to malice that which can be adequately explained by neglect, ignorance, or incompetence.

Tomorrow is the magical land where with minimal effort you'll make all your accessibility worries go away.

The more you know, the more you have to put aside when training others. It's more useful to start the process from where they are.

Many teams treat web accessibility for people with disabilities as special. But accessibility isn't special. It's specialised work.

If you're missing the right processes for people to rely on, even well-funded accessibility projects can fail.

Just as there are no cheat codes and shortcuts in getting in shape, tackling web accessibility requires a step-by-step approach.

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.