Daily emails so far...

Why accessibility work gets damaged when teams call it minor.

AI can help teams learn accessibility faster, but it becomes risky when nobody knows enough to question its answers.

In Issue 105 of Access Denied, Gary discovers one more step before fixing accessibility.

Your backlog is full of new features but empty of accessibility fixes.

AI should not give accessibility a single score. It should help teams find risk, sort issues and decide what needs human review.

A single accessibility score feels useful, but it can hide the failures that block real people.

AI accessibility audits are useful only when their suggested fixes work in the product, for real users.

AI can help with accessibility audits, but issue counts are weak metrics.

AI can help make product language clearer today, starting with error messages, forms and legal copy.

In Issue 105 of Access Denied, Gary uses AI to write about inclusion instead of fixing accessibility issues.

Accessibility needs boring, repeatable help. AI craves applause.

AI can help with accessibility work, but it cannot own decisions, judgment or user impact.

AI can find some accessibility issues, but it cannot replace human judgment, testing or disabled users.

Fixing accessibility has always been slow and expensive. AI is changing that equation, but only if someone decides to prioritise it.

Happy birthday to my son. One year old today!

Every company is doing something with AI, but most can't tell you what.

In Issue 104 of Access Denied, Gary thinks innovation needs more budget than accessibility.

Organisations fund stories, not problems and some work will never have a good enough story.

Accessibility debt doesn't come from nowhere.

Many business conversations sound like innovation, but they are really about risk.

How to refuse accessibility work that delays the user fix without sounding like you are dismissing it.

Smaller scope helps you protect the user outcome and ship useful fixes faster.

Accessibility work gets sharper when you define the outcome, target date and what stays out of scope.

In Issue 103, Gary insists the backlog is the best way to fix accessibility.

Most accessibility approaches fix issues. Journey ownership fixes experiences.

Disability-led sprints are built on what users experience rather than what you think matters.

When you find an accessibility issue, you either fix it now or give it a real date.

The Top 3 rule means you only ever have three accessibility priorities in play.

Severity buckets force you to be honest about accessibility impact and fix what matters most first.

The fix-on-touch approach means developers resolve issues in the components they're already working on.