` focus hosts with `tabindex`, an accessible name and advertised shortcuts (`Enter`, **Shift+F10**), without a composite-widget role. - Selection state is exposed only through a hidden `aria-describedby` description; change announcements are count-based live-region messages. - Focus is lost to the document body when a list expands (**Show more**) and is not provably preserved when opening the details pane morphs the page. - The supported interaction is not documented where end users can discover it. ### Scope and children - #AGILE-423 — screen-reader operability: navigation, event handling, focus retention, and the documented interaction. - #AGILE-424 — accessible feedback: selected-state exposure, concise plural-aware announcements, wording agreed with Behrang, coordination with #AGILE-364 menu announcements. - A markup-level follow-up (role-structure or explicit selection control) only if the #AGILE-423 decision gate triggers it — see Open decisions. ### Acceptance criteria (umbrella) - A screen-reader user can complete the core flows end to end: identify a card and its selection state, toggle it, build a batch, reach and invoke applicable batch actions, and recover focus afterwards. - The supported interaction is documented per screen reader (VoiceOver, NVDA; JAWS best-effort) and reachable from the in-app keyboard-shortcuts help. - Verified with VoiceOver in Chrome and Safari, with an NVDA smoke pass in Chrome and Firefox; unavailable combinations are labeled unverified, not claimed. - Keyboard focus, selection membership, the range anchor and the work package open in the details pane remain distinct — navigation alone changes none of the others. ### Open decisions - **Role structure for cards.** The current position (recorded in #AGILE-181 and restated in #DREAM-846's technical notes) is that cards deliberately avoid listbox/grid roles. #AGILE-423's phase 0 re-evaluates this with an instrumented diagnosis of the current model and a prototype comparing article, `grid` and grid-with-cell-entry variants. If the evidence escalates to a markup change, a dedicated child WP is created here with design sign-off; the table's role decision remains \#DREAM-860's and is not pre-empted. - **Adoption of AGILE-181's deferred items** (background-click clearing, persistent visible selection count, modified double-click, shared platform detection, split-view scroll loss) — referenced as candidates, not adopted by this feature. ### Coordination - Announcement wording and the state/announcement balance are shared with the work package table through #AGILE-424, so Backlogs and the table speak the same way (#DREAM-846). - Row-count/index conventions, where relevant, follow \#DREAM-858's BorderBoxTable work. ### Out of scope - Work package table, card view and Boards (#DREAM-846 stream). - Permission-independent selection, wider select-all scopes, mobile/tablet long-press (remain deferred under #AGILE-181). - A persistent visible selection count: unscheduled separate work, coordinated with #DREAM-846; #AGILE-424 remains the feedback coordination point, not the count's owner. - Batch move mechanics beyond what operability requires (owned by #AGILE-278 and the delivered stack).