Content
View differences
Updated by Judith Roth 1 day ago
**As a** screen reader / keyboard-only user
**I want to** inline and blcok 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 minimum - currently minimal)
* Solution validated manually with at least one screen reader
**I want to** inline and blcok 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
* Solution validated manually with at least one screen reader