# Feature COMMS-892 - Improve accessibility (keyboard navigation & screen reader support) for WPs in BlockNote

Project: Stream Communicator
Status: merged
URL: https://community.openproject.org/work_packages/COMMS-892

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint | Sprint 20 |
| Backlog bucket |  |
| Votes |  |
| List | a11y report 2026 |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Documents, Accessibility |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Community (COM) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | Yes |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As a** screen reader / keyboard-only user  
**I want to** inline and block work packages in the rich text editor to expose a clear, consistent accessible role and behavior  
**so that** I can understand what these elements are, know that they're interactive, and (if decided) operate them without a mouse

**Acceptance criteria**

*   Decision made and documented on interaction pattern for inline wp: proper menu-button (role="button" + aria-haspopup + aria-expanded + tabIndex + onKeyDown) vs. deliberate mouse-only role
    
*   Inline chip role/behavior is consistent with block card role/behavior (currently block uses role="button", inline has none)
    
*   If keyboard support is added: focus handling on the chip does not break ProseMirror's contenteditable selection/cursor behavior
    
*   Block work package exposes more informative content to screen readers (status, ID, subject at minimum, depending on the size - currently minimal)
    
*   Solution validated manually with at least one screen reader