WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: table paging


From: Jordan, Courtney
Date: Jan 31, 2011 1:48PM

That's certainly a lot of pages! Is there any way that you can break it
up into categories? Even as a sighted user, I would be frustrated
looking through 500 options in a drop-down list. That is assuming that I
even knew what the particular title of the page was. We can't expect
people to remember the title of every page. People can generally hold
about 5-7 or fewer items in memory. From my experience using JAWS 9, I
couldn't get the screen reader to "read" any items under the first one.
It would automatically trigger the first one and I would never get to
the others. Including a button avoided that issue as it didn't trigger a
JavaScript event from the drop-down selection itself, but from the
clicking of the button.

Good luck!
Courtney Jordan

-----Original Message-----
From: adam solomon [mailto: <EMAIL REMOVED> ]
Sent: Sunday, January 30, 2011 5:20 AM
To: WebAIM Discussion List
Subject: [WebAIM] table paging

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/>;