I’m looking for an accessible pattern for pagination where there will be a lot of pages.

I’m thinking a next and previous link with an ordered list of available pages. I think that might be a bit much for assistive tech though.

Any tips will be gladly received!

@hankchizljaw Are people likely to jump to specific pages? If not I would just use previous and next page links and an indicator for the current and total number of pages (Page 3 of 765).

@yatil that’s a good question. For a feed, you’d think probably not, really.

Just next and previous links would very much simplify things.

@hankchizljaw @yatil If on the web: HTML can put related links into its header, for relationships like home, title, previous, next, last, up.

It doesn't provide for a "skip 20" or something like that.

Yes, access to specific pages does come in handy. I would look for that in a chapter listing, but also to jump to a specific know page.

Don't make me scroll 500 pages to get to page 501 out of 788.

@aeveltstra @hankchizljaw No browser I know of surfaces the relationships specified in head. They can be useful for search engines but afaik are useless for actual users.

@yatil @hankchizljaw That's a shame.

I used to use the Opera browser, which did surface those links in their user interface. It was one of the reasons why I chose to use that browser over others.

And then they sold the company and the new owner fucked it all up.

@aeveltstra @yatil yeh I definitely want to avoid a butt-load of links, but also UI clutter too!!

@hankchizljaw @yatil The html links in the html header wouldn't get shown to the user. But an accessibility-aware client could choose to add them to the UI, if so desired by its user. I would show them by default with an option to hide, just so that the user knows it exists at all.

@aeveltstra @yatil I don’t think it’d take much work to get them in their so definitely worth investigating. Thanks André!

@hankchizljaw @aeveltstra The dream of accessibility-aware clients showing such metadata did not come true. There has been one Firefox plugin, and it was mostly empty because of no support on websites. I don't like hidden information because it often is out of date or wrong when developers are not aware.

In previous jobs we used to have these long pagination bars with page numbers centered on the current page.

And the buttons on the corners are first page, prev 10, prev, next, next 10, and last, with double <'s and >'s for the prev 10 and next 10, respectively. That pattern has always been the most useful for me.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!