Authentic conversations so far...

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.

Some breaking changes don't just inconvenience users, they lock them out entirely.

In Issue 75 of Access Denied, Gary thinks it's okay for touch screen to be inaccessible.

We can't stop change, but we can make sure it doesn't break things.

Share your experience, not your judgment.

Momentum is what keeps you and your accessibility work moving.

Stop measuring coverage and start measuring confidence in your accessibility tests.

If accessibility isn't in your spec, it won't get built.

If your spec doesn't include accessibility, AI agents will build exactly what you asked for, and nothing more.

In Issue 74 of Access Denied, Gary relies exclusively on AI to write code.

AI agents are writing, reviewing and testing code without anyone asking about accessibility.

Stop acting like you need to finish every other task on the roadmap before accessibility gets a look.