Keyboard workflow for deleting a table is not explained

Open Beginner friendly
#2,829 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
accessibility, documentation

Research direction

Start with the audited Docs document and locate the “Delete a table” block. Determine the keyboard-only and screen-reader workflow, then update the block so those steps and any difference from mouse interaction are explicit; done means users can delete a table without a mouse.

Written by the indexing model from the issue text.

Description

a11y

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
  1. Open the audited Docs document.
  2. Go to the “Delete a table” block.
  3. Review the visual explanation.
  4. Notice that the deletion workflow is explained through mouse interaction.
  5. 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

Dominant language
TypeScript
Stars
10.2k
Forks
772
Avg merge
3d 11h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TypeCellOS/BlockNote

All issues in TypeCellOS/BlockNote

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.