[myabc]

Note

This PR is stacked on #26288 (DREAM-885, treegrid semantics). Please review/merge that PR first.

Ticket

https://community.openproject.org/wp/DREAM-938

What are you trying to accomplish?

tl;dr for humans: Screen readers can now say "row 57 of 120" in flat and grouped tables, counted across pages and collapsed groups, so users know where they are in a long list.

Adds aria-rowindex/aria-rowcount to flat and grouped tables. Positions are query-wide (page 2 keeps them), collapsed groups leave gaps instead of renumbering, and header, sums, totals, empty and creation rows count towards the total. Hierarchy mode follows in DREAM-941 (#26293); aria-posinset/aria-setsize wait for DREAM-860.

What approach did you choose and why?

Pagination and group metadata are captured with each render and applied only when it commits. The whole projection is validated first; anything it cannot vouch for (unsupported modes, stale collections, contradictory groups, unknown rows) clears the attributes instead of guessing. Tables without keyboard navigation are unchanged.

Hints for dev review

• Default views use hierarchy mode; test with a flat or grouped query.
• Positions clear while a relation or children column is expanded and during a drag; a failed drop restores them.
• After a successful drop, and on unsaved manually sorted queries, positions stay absent until the next load. DREAM-941 ([DREAM-941] Publish row positions in hierarchy mode #26293) fixes this for saved ungrouped queries; the rest is DREAM-943.

AI involvement

Directed – I specified the requirements and AI implemented most of it; I validated via testing rather than a full line-by-line review.

Merge checklist

• Added/updated tests
• Added/updated documentation in Lookbook (patterns, previews, etc)
• Tested major browsers (Chrome, Firefox, Edge, ...)

[github-actions]

Warning

Flaky specs

• rspec ./spec/features/work_packages/table/delete_work_packages_with_descendants_spec.rb[1:1:2]

🤖 Ask Copilot to investigate

Copy the prompt below into a new comment on this PR to delegate the investigation to GitHub Copilot. It will look into the flakiness and open a separate pull request with you as reviewer.

@copilot The following spec(s) are flaky in CI (first seen on PR #26291, linked for reference only):

- `rspec ./spec/features/work_packages/table/delete_work_packages_with_descendants_spec.rb[1:1:2]`

Treat this as a standalone task, unrelated to PR #26291. Create a new branch from origin/dev and open a new pull request targeting dev — do not stack it on PR #26291 or reuse that branch.

Follow the playbook in docs/development/testing/handling-flaky-tests/README.md to find the root cause and fix the underlying race — do not skip, delete, or weaken the spec to make it pass; disabling is a last resort per the playbook, and only with a bug ticket. Verify the fix by running the spec(s) repeatedly (e.g. `script/bulk_run_rspec --run-count 10`).

If you cannot reproduce the flake or are not confident in a fix after reasonable investigation, do not fabricate a change or skip the spec to force CI green. Instead, leave the pull request in draft and document what you tried, the suspected cause, and any leads in its description, then assign @myabc to take over.

Once the fix is verified, title the PR after the spec(s) it fixes, and use the PR description to explain the root cause, how the change resolves it, and the before/after results. Label the PR `flaky-spec`, assign @myabc, and request a review from @myabc.
On every commit, set @myabc as the sole co-author with a `Co-authored-by:` trailer (use their GitHub no-reply email so it links to their account), so it is traceable who dispatched the fix.