# Open Point AGILE-473 - Decide the accessible role structure for Backlogs cards

Project: Stream agile
Status: needs clarification
URL: https://community.openproject.org/work_packages/AGILE-473

## Details

| Attribute | Value |
| --- | --- |
| Involved people | Behrokh Satarnejad, Darren Cadwallader |
| Assignee | Alexander Coles |
| Decision |  |
| Date |  |
| Module |  |
| Labels |  |

## Related to

| ID | Subject | Type | Status | Assignee | Project |
| --- | --- | --- | --- | --- | --- |
| AGILE-423 | Make Backlogs batch selection operable with VoiceOver | Implementation | in specification |  | Stream agile |
| AGILE-448 | Make selection and context actions in Backlogs fully accessible to assistive technology | Feature | in specification | Alexander Coles | Stream agile |
| DREAM-860 | Decide grid or treegrid semantics for the work package table | Open Point | needs clarification | Behrokh Satarnejad | Stream Design System |

## Description

### Decision needed

Decide whether Backlogs cards keep their current structure (`<article>` focus hosts with `tabindex`, an accessible name and advertised shortcuts, no composite-widget role, selection exposed through a hidden description) or adopt a composite role structure, and which one.

### Context

<mention class="mention" data-id="AGILE-181" data-type="work_package" data-text="#AGILE-181">#AGILE-181</mention> recorded the deliberate choice to avoid `listbox` and `grid` roles for cards; <mention class="mention" data-id="80153" data-type="work_package" data-text="#DREAM-846" data-display-id="DREAM-846">\#DREAM-846</mention>'s technical notes restate it, and the work package table went `treegrid` because it is tabular data (<mention class="mention" data-id="DREAM-860" data-type="work_package" data-text="#DREAM-860">#DREAM-860</mention>). #AGILE-423's phase 0 (2026-09-26) found: the Chrome + VoiceOver core journey works and speaks, including the selected state on return; the silent return from an inner link to its card reproduces in real Backlogs and in the `article`, `grid` and grid-with-cell-entry prototypes alike, so it is a feedback and focus-sync defect, not a role defect. Safari and Quick-Nav-on cells are unrun; NVDA and JAWS are unverified.

### Options

1.  Keep `article` hosts; fix event handling, focus retention and feedback (the primary path of <mention class="mention" data-id="AGILE-423" data-type="work_package" data-text="#AGILE-423">#AGILE-423</mention> and <mention class="mention" data-id="AGILE-424" data-type="work_package" data-text="#AGILE-424">#AGILE-424</mention>).

2.  `grid` with one row per card and cell entry for inner controls, aligned with the table's `treegrid` keys (arrows inside, **Tab** leaves, **Shift+Space** toggles).

3.  `listbox` with `option` cards, rejected in <mention class="mention" data-id="AGILE-181" data-type="work_package" data-text="#AGILE-181">#AGILE-181</mention> because cards hold interactive content; re-evaluate only with new evidence.

4.  `article` plus an explicit, named selection control per card (checkbox semantics) without a composite role.

### Resolution criteria

  - A documented choice with VoiceOver (Safari and Chrome) and NVDA (Firefox and Chrome) evidence for the core flows: identify a card and its selection state, toggle it, build a range, reach batch actions, return focus.

  - Wording and the split between accessible state and announcements agreed with <mention class="mention" data-id="64880" data-type="user" data-text="@Behrokh Satarnejad">@Behrokh Satarnejad</mention> and recorded in <mention class="mention" data-id="AGILE-424" data-type="work_package" data-text="#AGILE-424">#AGILE-424</mention>, aligned with the table's strings from <mention class="mention" data-id="DREAM-894" data-type="work_package" data-text="#DREAM-894">#DREAM-894</mention>.

  - If a markup change is chosen: a child Implementation work package under <mention class="mention" data-id="AGILE-448" data-type="work_package" data-text="#AGILE-448">#AGILE-448</mention> with design sign-off; the table's role decision stays with <mention class="mention" data-id="DREAM-860" data-type="work_package" data-text="#DREAM-860">#DREAM-860</mention>.
