Every list's pager is labelled "List pages", so a page with several lists has navigation regions a screen reader cannot tell apart #324

Open
opened 2026-11-05 22:07:34 +00:00 by cgalo5758 · 0 comments
Owner

What happens

Each governed list's pager renders inside <nav aria-label="List pages">. A screen reader lists a page's navigation regions by their labels, and a person moving by region uses those labels to pick one. The operator Domains page can page three lists (live claims, placements and claim history), so it can offer three regions all named "List pages". The organization page can offer four (the grants ledger, Members, Entitlement changes and Tier changes). Nothing in the label says which list a pager belongs to.

The search inputs on those pages had the same fault and now take a label per list ("Search placements", "Search members", and so on, through ListNav.SearchLabel). The pager has no such field.

What should happen

Each pager's region is named after its list, so no two navigation regions on one page share a label. A list alone on its page may keep "List pages". The new labels are heard by screen readers only. A test renders each page that holds several paged lists, with every list past one page, and fails when two navigation regions share a label.

Where

listPager in internal/embeds/templates/partials/operator_list_controls.html (the <nav aria-label="List pages">), ListNav in internal/server/list_scale.go, and the navs built in internal/server/operator_domains.go and internal/server/operator_enrollment.go.

Steps

  1. As an operator, open the Domains page on a deployment with more than ten placements and more than ten terminal claims, or open an organization with more than ten members.
  2. List the page's landmarks with a screen reader, or read the browser's accessibility tree. Two or more navigation regions are named "List pages".

Why it matters

Moving by landmark is how a screen-reader user skips to one part of a page. When the landmarks share a name, the user has to enter each one to learn which list it pages, on the two operator pages that hold the most lists.

### What happens Each governed list's pager renders inside `<nav aria-label="List pages">`. A screen reader lists a page's navigation regions by their labels, and a person moving by region uses those labels to pick one. The operator Domains page can page three lists (live claims, placements and claim history), so it can offer three regions all named "List pages". The organization page can offer four (the grants ledger, Members, Entitlement changes and Tier changes). Nothing in the label says which list a pager belongs to. The search inputs on those pages had the same fault and now take a label per list ("Search placements", "Search members", and so on, through `ListNav.SearchLabel`). The pager has no such field. ### What should happen Each pager's region is named after its list, so no two navigation regions on one page share a label. A list alone on its page may keep "List pages". The new labels are heard by screen readers only. A test renders each page that holds several paged lists, with every list past one page, and fails when two navigation regions share a label. ### Where `listPager` in `internal/embeds/templates/partials/operator_list_controls.html` (the `<nav aria-label="List pages">`), `ListNav` in `internal/server/list_scale.go`, and the navs built in `internal/server/operator_domains.go` and `internal/server/operator_enrollment.go`. ### Steps 1. As an operator, open the Domains page on a deployment with more than ten placements and more than ten terminal claims, or open an organization with more than ten members. 2. List the page's landmarks with a screen reader, or read the browser's accessibility tree. Two or more navigation regions are named "List pages". ### Why it matters Moving by landmark is how a screen-reader user skips to one part of a page. When the landmarks share a name, the user has to enter each one to learn which list it pages, on the two operator pages that hold the most lists.
cgalo5758 added the
kind
bug
area/operator-uiaccessibility
labels 2026-11-05 22:07:34 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#324