#36366: Improving the accessibility of the pagination layout in the admin.
-------------------------------------+-------------------------------------
Reporter: Antoliny | Owner: Antoliny
Type: | Status: assigned
Cleanup/optimization |
Component: contrib.admin | Version: 5.1
Severity: Normal | Resolution:
Keywords: accessibility, | Triage Stage:
screen reader, pagination | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Antoliny:
Old description:
> In the admin, when navigating to the pagination area using a screen
> reader, there is currently no description provided for the area. When
> focusing on a button, the screen reader only announces the button's
> innerHTML and its role.
>
> e.g. "2, button"
>
> [[Image(pagination_screenreader_example.png)]]
>
> This may not clearly communicate the purpose of the button to screen
> reader users, as the innerHTML and role alone can be ambiguous.
>
> I believe accessibility could be improved by using `aria-labelledby` to
> provide a description when entering the pagination area, and by adding
> the `aria-current` attribute to indicate the current page when focusing
> on individual buttons. This would help screenreader users better
> understand the context and purpose of each button control.
New description:
In the admin, when navigating to the pagination area using a screen
reader, there is currently no description provided for the area. When
focusing on a button, the screen reader only announces the button's
innerHTML and its role.
e.g. "2, button"
[[Image(resize_pagination_screenreader_example.png)]]
This may not clearly communicate the purpose of the button to screen
reader users, as the innerHTML and role alone can be ambiguous.
I believe accessibility could be improved by using `aria-labelledby` to
provide a description when entering the pagination area, and by adding the
`aria-current` attribute to indicate the current page when focusing on
individual buttons. This would help screenreader users better understand
the context and purpose of each button control.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/36366#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701969b2e8330-0225f4c7-375b-4aad-9201-1c9b39840f13-000000%40eu-central-1.amazonses.com.
