Why QA keeps finding avoidable problems
Aug 13th, 2026
QA keeps finding accessibility issues because teams leave key decisions until the last handoff.
I started this newsletter on March 12th, 2024 and wrote every day for 945 days. These are the emails from that run, alongside anything I've written since. Browse by topic or search for something your team is dealing with.
Aug 13th, 2026
QA keeps finding accessibility issues because teams leave key decisions until the last handoff.
Aug 12th, 2026
Shared responsibility works until a team needs someone to make an accessibility decision.
Aug 11th, 2026
Accessibility rework starts when nobody agrees what done means before work begins.
Aug 10th, 2026
Why work reopens near release, even when team thought it was done.
Aug 9th, 2026
In Issue 110 of Access Denied, Gary makes accessibility a shared responsibility.
Aug 8th, 2026
A short story about vague accessibility requirements, shared ownership and how one innocent line can turn into rework.
Aug 7th, 2026
Why decision rights matter before work turns into rework.
Aug 6th, 2026
Good rework, bad rework and what product teams can learn from the difference.
Aug 5th, 2026
Why accessibility work reopens and what product teams can learn from it
Aug 4th, 2026
A working definition of accessibility rework and why it matters for product teams.
Aug 3rd, 2026
A personal note about accessibility, healthcare, education and the product questions I want to explore next.
Aug 2nd, 2026
In Issue 109 of Access Denied, Gary starts accessibility with a governance group.
Aug 1st, 2026
Big accessibility efforts often burn out. Start smaller, while real work is happening.
Jul 31st, 2026
This newsletter is shifting toward accessibility rework, product quality and digital health delivery.
Jul 30th, 2026
Accessibility improves when teams can make better choices before problems turn into rework.
Jul 29th, 2026
Accessibility standards and policies only help when they shape real product decisions during everyday work.
Jul 28th, 2026
Good accessibility governance helps teams decide faster.
Jul 27th, 2026
Accessibility improves when teams have clear defaults that make the right choice easier during everyday product work.
Jul 26th, 2026
In Issue 108 of Access Denied, Gary moves fast and thinks that justifies ignoring accessibility.
Jul 25th, 2026
Accessibility gets easier when teams focus on repeat problems and shared decisions instead of trying to fix every issue one by one.
Jul 24th, 2026
Accessibility problems often point to deeper product delivery habits, like unclear ownership, late checks and weak definitions of done.
Jul 23rd, 2026
Accessibility improves when you build it into existing product process.
Jul 22nd, 2026
Accessibility problems often reveal delivery problems.
Jul 21st, 2026
AI can help with accessibility work. It can't take responsibility for it.
Jul 20th, 2026
Accessibility is everyone's responsibility, but the decisions still need a person resposible.
Jul 19th, 2026
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.
Jul 17th, 2026
Say what you're doing first, then explain what moves later and why.
Jul 16th, 2026
A target date is risky only when teams treat it like a promise instead of a tool for making tradeoffs.
Jul 15th, 2026
Accessibility work needs outcomes, dates, scope and demos. Awareness does not replace delivery.
I write about accessibility rework, product quality and the decisions teams make while building software.