Authentic conversations so far...

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.

In Issue 102 of Access Denied, Gary thinks building up the backlog is progress.

Bloated backlogs hurt your product.

Five questions to help you change how your team thinks about accessibility or how they behave.

Trying to change how your team thinks and behaves about accessibility at the same time is impossible.

Changing team behaviour around accessibility means building it into the process and holding the line.

Changing how your team thinks about accessibility is powerful, but slow to engineer.

Getting a team to take accessibility seriously means making a deliberate choice between changing how people think and changing what they do.