TypeCellOS / TypeCellOS/BlockNote

Docs editor: tab indentation not announced to assistive technologies

Open
#2,812 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What’s broken?

When the user presses the Tab key in the content area, the text is visually indented but no announcement is made by screen readers. The formatting change is not reported.

Impact

A blind user navigating with a screen reader presses Tab in the content area: no feedback is vocalized. They don't know if the indentation has been applied or at what level it is located.

What did you expect to happen?

When indentation is applied via the Tab key, a message must be conveyed by assistive technologies to inform the user of the indentation level change (e.g., "Indented", "Indentation level: 2").

Steps to reproduce

Open a Docs document
Place the cursor in the content area
Press the Tab key
Observe that the content is visually indented but no announcement is vocalized
RGAA criteria

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.

Research direction

Start by locating the Docs editor's Tab-key indentation handling and its accessibility announcement path. Reproduce the issue with a screen reader; it is done when applying indentation announces the formatting change and indentation level to assistive technologies.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.