Zetema
Edit
Accessibility · A few weeksAnywhere· Source · May 2026

Screen-reader users in JupyterLab aren't told when things happen on screen, because the app has no shared way to announce them.

Screen-reader users who work in JupyterLab notebooks

Where it stands

  1. Sourced (done)
  2. Kit (done)
  3. Wanted (next)
  4. Building
  5. Solved

How this problem came to be

  1. Found2 sourcesgithub.com/jupyterlab
  2. Quoted3 claimseach checked against its page
  3. BriefWrittenand what solved looks like
  4. Market1 signals2 reactions on the issue
  5. Kit5 steps19 tools · 6 routes
  6. People0 want0 live it · 0 would test

The problem, broken down

Who it hurts
Students, researchers and data scientists who use JupyterLab with a screen reader.
The moment
When a cell finishes running or a status changes and nothing is read out.
What people do today
Earlier pull requests, still open, each wrote directly to the page to trigger announcements.
Why it's unsolved
Reviewers want one shared, configurable service rather than repeated one-off code.
What solved looks like
A JupyterLab plugin with a public announce() function and settings to turn announcements off and set a delay, old messages cleared automatically, and at least one real feature using it. Tested with NVDA and VoiceOver.

Evidence

Every claim is tied to the source it comes from
JupyterLab issue #16145: new plugin for aria-live announcements ↗
  1. 1The issue says earlier pull requests for screen-reader announcements repeated code that wrote directly to page elements.
  2. 2Reviewers asked for a configurable delay, clearing entries after a timeout to avoid a memory leak, and a way for users to turn the feature off.
  3. 3The proposal is a new plugin with a public announce() API and settings; it is labelled ‘help wanted’.

Written from the cited sources. Anything they don't say is left as a question, not a guess.

Sources

From a public page with a citation.

  1. [1]JupyterLab issue #16145: new plugin for aria-live announcements
  2. [2]MDN: ARIA live regions
What the source says, in short

The issue says earlier pull requests for screen-reader announcements repeated code that wrote directly to page elements. Reviewers asked for a configurable delay, clearing entries after a timeout to avoid a memory leak, and a way for users to turn the feature off. The proposal is a new plugin with a public announce() API and settings; it is labelled ‘help wanted’.

Forks 0

Nobody has forked this yet. Be the first.

Market read

How big this is, from the evidence

  • GitHub ↗Builders' pull · Medium confidence2 reactions on the issue

How these were measured: Total reactions on the GitHub issue, read from its API.

For whoever takes this up

The builder's path for this problem

Five steps, each with the tools that fit this problem and a word to carry with you. A starter prompt is ready to paste into any assistant.

Open the path

Discussion 0

No comments yet.