Three questions that reveal where accessibility rework enters your product process.
Daily emails so far...
This is an archive of the short emails I've sent since March 12th, 2024 about accessibility rework, product quality and the messy bits of delivery. Enjoy!
Too early to define done
Yesterday
You can define done too early and not reduce any rework.
Too late to define done
Aug 24th, 2026
How missing done definitions turn into release debate and accessibility rework.
Access Denied #112: Success charts
Aug 23rd, 2026
In Issue 112 of Access Denied, Gary thinks fixing the same issue all the time signals success.
How to know when accessibility will cause rework
Aug 22nd, 2026
A short list of product metrics that can warn accessibility is becoming delivery risk.
Delivery risk is still human
Aug 21st, 2026
Accessibility can be both human impact and delivery risk.
When fixes don't stick
Aug 20th, 2026
Some fixes need to live in patterns, not tickets.
When shortcuts become normal
Aug 19th, 2026
Accessibility debt often starts as small exceptions, unclear decisions and repeated fixes you learn to tolerate.
What finished means
Aug 18th, 2026
Why finished needs a shared meaning before work can move forward.
Mea culpa
Aug 17th, 2026
Silly mistake in Kit prevented any emails from sending.
Access Denied #111: Continuous accessibility coverage
Aug 16th, 2026
In Issue 111 of Access Denied, Gary pitches continuous accessibility coverage.
Where accessibility rework starts
Aug 15th, 2026
Introducing the email course for digital health product leaders who want fewer late accessibility surprises and less rework.
Why the same accessibility issues keep coming back
Aug 14th, 2026
Repeated accessibility issues cost more than one fix.
Why QA keeps finding avoidable problems
Aug 13th, 2026
QA keeps finding accessibility issues because teams leave key decisions until the last handoff.
Why shared responsibility creates unclear ownership
Aug 12th, 2026
Shared responsibility works until a team needs someone to make an accessibility decision.
Why your definition of done is missing accessibility
Aug 11th, 2026
Accessibility rework starts when nobody agrees what done means before work begins.
Why finished work keeps reopening
Aug 10th, 2026
Why work reopens near release, even when team thought it was done.
Access Denied #110: No blockers
Aug 9th, 2026
In Issue 110 of Access Denied, Gary makes accessibility a shared responsibility.
The form should be accessible
Aug 8th, 2026
A short story about vague accessibility requirements, shared ownership and how one innocent line can turn into rework.
Who gets to decide?
Aug 7th, 2026
Why decision rights matter before work turns into rework.
Is rework always bad?
Aug 6th, 2026
Good rework, bad rework and what product teams can learn from the difference.
What made us think this was done?
Aug 5th, 2026
Why accessibility work reopens and what product teams can learn from it
Rework, in plain terms
Aug 4th, 2026
A working definition of accessibility rework and why it matters for product teams.
What I missed for a decade
Aug 3rd, 2026
A personal note about accessibility, healthcare, education and the product questions I want to explore next.
Access Denied #109: The smallest most boring thing
Aug 2nd, 2026
In Issue 109 of Access Denied, Gary starts accessibility with a governance group.
Start with kindling
Aug 1st, 2026
Big accessibility efforts often burn out. Start smaller, while real work is happening.
The newsletter is changing
Jul 31st, 2026
This newsletter is shifting toward accessibility rework, product quality and digital health delivery.
Make the better choice easier
Jul 30th, 2026
Accessibility improves when teams can make better choices before problems turn into rework.
Make standards useful
Jul 29th, 2026
Accessibility standards and policies only help when they shape real product decisions during everyday work.
Governance should remove decisions
Jul 28th, 2026
Good accessibility governance helps teams decide faster.
Want the next email?
I send one short email every day for product leaders who want to kill accessibility rework before it slows delivery. Expect accessibility debt, better metrics, clearer ownership, product quality and decisions teams can use.