Daily emails so far...

Even good intentions in the planning phase lead to inaccessible products.

Relationships, health, freedom and web accessibility all require you to pay the full cost up front.

When it comes to accessibility in product development, paying debt later costs way more than building it in from the start.

In Issue 79 of Access Denied, Gary thinks lawsuit headlines can make the case for accessibility.

The business case for accessibility only works when it solves a real problem your company has right now.

Accessibility needs both inspiration and consequences. The carrot and the stick.

The Web Almanac's Accessibility chapter analyses millions of websites to reveal the real state of web accessibility.

Make 2026 count by being kind to each other.

Two wrongs don't make a right and two shortcuts don't create inclusion.

After 658 emails and 200,000 words on accessibility, I've learned that persistence means finding the explanation that lands.

In Issue 78 of Access Denied, Sarah tells Gary she speaks project management now.

Honest reflections on fighting for web accessibility in 2025. The wins, the losses, the burnout and why I keep showing up anyway.

The shortcuts worth keeping are those that save you time without costing someone else theirs.

All shortcuts save time, but some also exclude people.

Accessibility is often invisible work: the advocacy, the teaching, the quiet fixes.

The blame game starts fast when bugs appear after an accessibility sprint.

Accessibility fixes get blamed for bugs immediately, but when you skip accessibility, nobody blames its absence.

In Issue 77 of Access Denied, Gary thinks accessibility fixes caused bugs in the last release.

After one sprint of accessibility fixes, suddenly every bug is "caused by accessibility."

It's exhausting always raising accessibility in every meeting and then see them go in a backlog to die.

A recap of the 10 things you should focus on for web accessibility.

Good testing cultures are comfortable with untested territory. Not everything needs testing.

What looks like a limitation is actually clarity.

Accessibility shouldn't be in the prioritisation conversation at all.

In Issue 76 of Access Denied, Gary prioritises accessibility and thinks it's a strategic move.

Prioritisation isn't about cutting corners or doing less.

Product teams can predict features months in advance but somehow never see accessibility coming.

Sustainability is what helps what you do today stick around when you're not there tomorrow.

Be deliberate in your choices of what to test for accessibility, because you can't test everything.

Developers get changelogs and support on a breaking change. Users get to just live with the update.