Non-standard functionality for pagination controls #3474
rhoadsstevens
started this conversation in
Accessibility
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Priority level 2 (out of 3) from UW Accessible Technologies
WCAG mapping: 4.1.3 Status Messages
STEPS TO REPRODUCE:
OBSERVED BEHAVIOR:
The first issue is that even when the "prev" button is visually greyed out when you are on the first page of the search results, it is still focusable and when clicked it refreshes the page. Additionally, the "prev" and "next" buttons are in sublists of size 1, which does not make sense as they are single elements. Finally, when using the "next" button to go to the next page the viewport of the page goes back to the top, but the focus remains on the "next" button.
EXPECTED BEHAVIOR:
Buttons that should be unavailable, such as the "prev" button on the first page of search results, should not be focusable. We also do not think that the "prev" and "next" buttons need to be in their own separate lists, and instead there should only be one list corresponding to the list of page numbers. When using the "next" button, one option for the focus would to move it to the top of the search results list, although this can be up for discussion. At the very least, the viewport should not move to the top of the page while the focus remains on the "next" button.
Beta Was this translation helpful? Give feedback.
All reactions