Daily emails so far...

In Issue 110 of Access Denied, Gary makes accessibility a shared responsibility.

A short story about vague accessibility requirements, shared ownership and how one innocent line can turn into rework.

Why decision rights matter before work turns into rework.

Good rework, bad rework and what product teams can learn from the difference.

Why accessibility work reopens and what product teams can learn from it

A working definition of accessibility rework and why it matters for product teams.

A personal note about accessibility, healthcare, education and the product questions I want to explore next.

In Issue 109 of Access Denied, Gary starts accessibility with a governance group.

Big accessibility efforts often burn out. Start smaller, while real work is happening.

This newsletter is shifting toward accessibility rework, product quality and digital health delivery.

Accessibility improves when teams can make better choices before problems turn into rework.

Accessibility standards and policies only help when they shape real product decisions during everyday work.

Good accessibility governance helps teams decide faster.

Accessibility improves when teams have clear defaults that make the right choice easier during everyday product work.

In Issue 108 of Access Denied, Gary moves fast and thinks that justifies ignoring accessibility.

Accessibility gets easier when teams focus on repeat problems and shared decisions instead of trying to fix every issue one by one.

Accessibility problems often point to deeper product delivery habits, like unclear ownership, late checks and weak definitions of done.

Accessibility improves when you build it into existing product process.

Accessibility problems often reveal delivery problems.

AI can help with accessibility work. It can't take responsibility for it.

Accessibility is everyone's responsibility, but the decisions still need a person resposible.

In Issue 107 of Access Denied, Gary misreads that accessibility is ongoing and decides not to ship anything.

Short practical answers to common questions about leading accessibility work.

Say what you're doing first, then explain what moves later and why.

A target date is risky only when teams treat it like a promise instead of a tool for making tradeoffs.

Accessibility work needs outcomes, dates, scope and demos. Awareness does not replace delivery.

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.