Focus not moved when image edit panel opens

Abierto
#2,813 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
react, typescript
Área
accessibility, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

a11y
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

Lenguaje dominante
TypeScript
Estrellas
10.2k
Forks
772
Merge medio
3 d 11 h
PR fusionados (30 d)
17

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TypeCellOS/BlockNote

Todos los issues de TypeCellOS/BlockNote

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.