Opened 7 weeks ago
Last modified 7 weeks ago
#36510 new Cleanup/optimization
Header text for pagination contains title of table while it's the only pagination on the page.
Reported by: | laurenherregodts | Owned by: | |
---|---|---|---|
Component: | contrib.admin | Version: | 5.2 |
Severity: | Normal | Keywords: | accessibility, pagination |
Cc: | Thibaud Colas, Antoliny | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | yes |
Description
On the page Release in the django admin demo project, the pagination underneath the table has Pagination release
as h2
header text.
This has been identified while using the Landmark check of AXE. No accessibility issue was flagged, but just wondering if the release
in the header text is needed.
I believe release
can be removed from the header text since there is only one pagination present on the page.
Change History (3)
comment:1 by , 7 weeks ago
Cc: | added |
---|---|
Triage Stage: | Unreviewed → Accepted |
comment:2 by , 7 weeks ago
Cc: | added |
---|
comment:3 by , 7 weeks ago
First of all, thank you for submitting the ticket :)
As you mentioned, if multiple paginations are applied, using "pagination + model name" is naturally necessary.
However, even if only one pagination is used on the admin ChangeList
page, I do not think that "pagination + model name" becomes excessive information that interferes with screen reader users.
On the contrary, I believe it is necessary information that provides clarity.
Since a web page can usually contain many models and therefore many different ChangeList
pages for those models, "pagination + model name" can help screen reader users perceive at once which model's pagination this is.
So, I feel there is no need to remove the model name deliberately.
Thank you! This looks like a recent change from #36366, in PR Fixed #36366 -- Improved accessibility of pagination in the admin. #19448.
I think this label tweak would work much better for its intended audience, but this will probably need accessibility team discussion on how best to achieve the desired results. The issue I see is that for _landmark names_ verboseness isn’t desirable. If we wanted the added context we would be better off with
aria-describedby
.