What’s broken?
This issue was identified during the Docs accessibility audit on a page containing table-related content.
Audited page:
https://docs.numerique.gouv.fr/docs/0d998bef-1b69-47ce-bd18-83d4d849c734/
In the “Delete a table” block, the visual content explains how to delete a table using the mouse.
However, the keyboard workflow is different and is not clearly explained.
A keyboard-only user or screen reader user does not receive enough information to perform the same action without a mouse.
What did you expect to happen?
When an action is demonstrated with the mouse, the equivalent keyboard workflow should also be explained.
The documentation should clearly describe how to delete a table using the keyboard.
If the keyboard interaction is different from the mouse interaction, this difference should be explicitly documented.
Steps to reproduce
- Open the audited Docs document.
- Go to the “Delete a table” block.
- Review the visual explanation.
- Notice that the deletion workflow is explained through mouse interaction.
- Notice that the equivalent keyboard workflow is not clearly explained.
Impact
Keyboard-only users and screen reader users may not understand how to delete a table.
This creates an unequal experience where mouse users receive instructions, but keyboard users do not.
WCAG Criteria
WCAG 2.1.1 - Keyboard
WCAG 2.4.6 - Headings and Labels
BlockNote version
0.51.4
What’s broken?
This issue was identified during the Docs accessibility audit on a page containing table-related content.
Audited page:
https://docs.numerique.gouv.fr/docs/0d998bef-1b69-47ce-bd18-83d4d849c734/
In the “Delete a table” block, the visual content explains how to delete a table using the mouse.
However, the keyboard workflow is different and is not clearly explained.
A keyboard-only user or screen reader user does not receive enough information to perform the same action without a mouse.
What did you expect to happen?
When an action is demonstrated with the mouse, the equivalent keyboard workflow should also be explained.
The documentation should clearly describe how to delete a table using the keyboard.
If the keyboard interaction is different from the mouse interaction, this difference should be explicitly documented.
Steps to reproduce
Impact
Keyboard-only users and screen reader users may not understand how to delete a table.
This creates an unequal experience where mouse users receive instructions, but keyboard users do not.
WCAG Criteria
WCAG 2.1.1 - Keyboard
WCAG 2.4.6 - Headings and Labels
BlockNote version
0.51.4