July 3, 2026
Screen reader vs. reality
How working with a blind client revealed invisible accessibility gaps
A simple job turned into an 18-hour reality check — and the comments got spicy
TLDR: A developer tried to make a work tool usable for blind and deaf employees and discovered the biggest problems came from the platforms themselves, not just their own work. Commenters split between treating the 18-hour fix as normal, mocking the article’s writing style, and arguing the story exposed a much bigger everyday accessibility blind spot.
What looked like a quick accessibility tidy-up turned into a full-blown "wow, the internet is a different planet" moment. The writer thought helping a blind client use a Microsoft-based approval system would take a couple of hours. Instead? 18 hours, multiple test calls, and a depressing parade of platform problems: pages repeating “read only” over and over to screen readers, broken heading structure, emails that were hard to read aloud, and an approvals tool that apparently didn’t play nicely at all. The biggest gasp from readers wasn’t even the bug list — it was the realization that these problems were hiding in plain sight the whole time.
But the comments quickly became their own drama feed. One camp basically shrugged and said, “18 hours? So… a few workdays. Sounds normal.” Another group was far less forgiving, dragging the piece itself for having what one reader called an “AI-slop-stench,” accusing the writing of sounding vague and synthetic instead of giving sharper examples. Then came the philosophical pile-on: one commenter pointed out that even the title leans on the language of sight — “revealed invisible” — which sparked a meta debate about how deeply able-bodied language is baked into everyday life. And in the most unexpectedly raw turn, one deaf commenter zoomed out from software entirely, saying the story reflects a wider pattern of disabled people being ignored in daily life, right down to being bullied off sidewalks by cyclists. So yes, the software flaws were bad — but the comment section made it clear the real scandal is how often accessibility only matters when someone is forced to notice it.
Key Points
- •The article says a client accessibility review for a Power Automate purchasing approval workflow took 18 hours instead of the few hours originally expected.
- •A blind in-house accessibility specialist tested the workflow using her own account and desktop apps after Microsoft browser apps proved difficult to navigate with screen readers.
- •Testing sessions were conducted over Zoom because the specialist considered it more accessible than Microsoft Teams and Google Meet.
- •SharePoint's read-only mode added '(read only)' to every field on a tracking page, creating repetitive output for screen-reader users and consuming space on braille displays.
- •The article attributes several issues to platform limitations, including Teams approvals not being recognized by screen readers, JAWS compatibility problems in Outlook, and SharePoint producing multiple H1 headings.