TypeCellOS / TypeCellOS/BlockNote

Focus not moved when image edit panel opens

Offen
#2,813 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

a11y
Vorherrschende Sprache
TypeScript
Sterne
10.2k
Forks
772
Ø Merge
3 T. 11 Std.
Gemergte PRs (30 T.)
17

Beschreibung

What’s broken?

After inserting an image (via / or /image/), the first command menu collapses but the focus remains on it. The image edit panel opens without the focus being moved to it and without any information being provided to the user indicating that a new panel is now available.

Impact

A blind user navigating with a screen reader inserts an image: the first menu collapses, the focus remains on it, and the edit panel opens silently. The user does not know that the panel is available and cannot access it without a mouse.

What did you expect to happen?

When the image edit panel opens, the focus must be moved to this panel or to its first interactive element. If moving the focus is not desirable, the panel opening must be announced via an aria-live region.

Steps to reproduce

Open a Docs document
Navigate using keyboard only
Insert an image via / or /image/
Notice that the focus remains on the first collapsed menu; the edit panel is open but inaccessible without a mouse

BlockNote version

0.51.1

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Start by reproducing the issue in a Docs document with keyboard navigation, inserting an image via / or /image/. Trace the image edit panel opening and its focus behavior. Done means focus reaches the panel or its first interactive element, or the panel opening is announced through an aria-live region, and the keyboard-only flow is accessible to a screen reader user.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
react, typescript
Bereich
accessibility, frontend
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
58/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.