WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible pagination?

for

From: Birkir R. Gunnarsson
Date: Nov 6, 2017 6:53AM

Agree with Tim.
I think "go to page 1" is a goo screen reader text for pagination links.
The screen reader does not see the ARIA landmark when viewing links
out of context, e.g. in a listbox, and "1" is not vry descriptive link
text.
The extra second or so that it takes the screen rader to say "page 1"
or "go to page 1" is not a screen reader user deterrant in my
experience (again, testing with real end users is always the most
valuable source of feedback).

I wish the author ha expounded a bit on this widget, e.g. showed it in
context of an actual page. I think "previous" and "Next" options e.
should b cded as buttons to distinguish them from the links, and that
the number of results per page should be coded as live region
headings.



On 11/6/17, Tim Harshbarger < <EMAIL REMOVED> > wrote:
> Just to offer another perspective, I do not think that this pattern is too
> verbose or problematic as a screen reader user. For me, too verbose is
> something like a group label for radio buttons that is a paragraph long.
> That tends to feel verbose. However, I know other screen reader users might
> feel differently.
>
> My thought is that if you follow this pattern, someone using a screen reader
> would clearly get the idea that this part of the page is the pagination. I
> also think you could use only parts of this pattern and end up with
> something that might be accessible as well, but depending on what you do it
> might not be as clear to screen reader users who don't spend their days
> reviewing, discussing, and testing user interfaces like I do.
>
> This is one of those situations where being able to test with real end users
> would help. You could find out if there are any major differences between
> patterns.
>