Opened 15 months ago
Last modified 14 months ago
#34835 closed Cleanup/optimization
Use a `nav` element or `navigation` landmark for changelist filters — at Version 2
| Reported by: | Thibaud Colas | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.admin | Version: | 4.2 |
| Severity: | Normal | Keywords: | accessibility, screen reader, landmarks |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | yes |
Description (last modified by )
Related: #34832, #34833, #34834. Changelist filters are a very useful way to navigate long lists of entries. The filters would be easier to reach for screen reader users if they were in a navigation landmark done with a <nav> element or role="navigation" attribute. Currently they are a <div id="changelist-filter">.
This element should be switched to a <nav>, and we should also add an aria-labelledby set to the id of <h2>Filter</h2> element within, so the navigation landmark has a distinct label.
Change History (2)
comment:1 by , 15 months ago
| Description: | modified (diff) |
|---|
comment:2 by , 15 months ago
| Description: | modified (diff) |
|---|
Note:
See TracTickets
for help on using tickets.