WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: table paging


From: Birkir Rúnar Gunnarsson
Date: Jan 31, 2011 6:33AM

Would it be possible to provide both of these options (how much work
would that be)?
A third navigation possibility may be to navigate by chapters, have a
list box of chapters along with their page numbers (chapter 1, page4 -
chapter 2, page 23 - etc).
As a user I am most likely just reading the book through, page by
page, or I have to jump to a specific chapter, or I have to find a
specific page (assuming this is a book in html format).
The problem with next and prev buttons is that I may need to go to
page 116, this might be a text book for class, and I sure do not want
to click "next" 115 times, it would render the next nearly useless to
By both having a next and prev buttons and a drop list you solve this problem.
Most often I will be reading a book straight through, but sometimes I
need to start reading at a certain point in the book.
The chaper idea is bonus, and might not be worth the implemntation effort.

On 1/31/11, William Lawrence < <EMAIL REMOVED> > wrote:
> THere's a great paging information article out there that is not
> available right now that talks about some different approaches to
> paging.
> THere's a copy here:
> http://kurafire.net.sharedcopy.com/log/archive/2007/06/22/727aea9f881047adf6b42d874edd2bcd.html
> The original was here:
> http://kurafire.net/log/archive/2007/06/22/pagination-101
> Best regards,
> William
> --
> William Lawrence
> Accessibility Engineer
> On Mon, Jan 31, 2011 at 1:30 AM, Jeevan Reddy
> < <EMAIL REMOVED> > wrote:
>> Hi Adam,
>>    I would Suggest you to go with First Method you Mentioned.
>> Irrespective of the number of pages you have, this method is popular now a
>> days, and accessible too.
>> And the numbered links can be accessible Via Link List for Screen Reader
>> users, and
>> You need to take Care of two things to implement this More Accessible.
>> 1 Provide Enough clickable Area.
>> 2 Provide Previous and Next Buttons(image buttons) so that Screen Reader
>> user can directly Access the Buttons and numbered list Between them as
>> well.
>> Thanks and Regards,
>> Jeevan.
>> On Sun, Jan 30, 2011 at 3:49 PM, adam solomon
>> < <EMAIL REMOVED> >wrote:
>>> What is the best way to implement a simple yet accessible paging. The two
>>> standard ways I see all over the place are:
>>> 1. set of numbers, each one a link to that particular numbered page, with
>>> arrow links to navigate to different sets of pages.
>>> 2. dropdownlist with all the pages, and a button next to it - choose the
>>> page number and press go.
>>> I personally prefer the second option - simple and to the point, and
>>> easier
>>> to markp up correctly. Yet, I am worried about a situation where there
>>> are
>>> many pages (500) and a keyboard user would have to navigate all the way
>>> down
>>> with arrow keys. The truth is that this is a problem even in the
>>> numbering
>>> paging - the user would have to suffer a number of postbacks before
>>> getting
>>> to the correct set of pages.
>>> Any thoughts?
>>> --
>>> adam solomon
>>> linkedin <http://il.linkedin.com/pub/adam-solomon/24/449/a4>;
>>> blogix <http://adam.blogix.co.il/>;