WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: table paging

for

From: E.J. Zufelt
Date: Jan 31, 2011 10:18AM

The edit field for page number is a good idea, when talking about documents.

If talking about other tabular data it may be less useful.

As an example, in the Drupal bug tracker you can access a listing of open issues, which is formatted into a table.

Searching the tracker for "accessibility" will give you several pages of results (50 results per page).

The data is tabular as it may contain table headings such as: Project, Issue, Status, Assigned to, etc.

In drupal the pager consists of links for: First, Previous, 1, 2, 3, 4, Next and Last.

I am not sure how many pages are required before the list of numbers is truncated.

HTH,
Everett Zufelt
http://zufelt.ca

Follow me on Twitter
http://twitter.com/ezufelt

View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt



On 2011-01-31, at 12:00 PM, Langum, Michael J wrote:

> It seems to me that the important issue here is what is the most appropriate form of navigation for large multi-page documents.
>
> We need to ask, how will users navigate the content. In my experience, navigation by links to content blocks (e.g. chapter and section titles) is usually most appropriate. I think it is rare when users need to navigate by page number.
>
> But I can imagine cases (e.g. you can find the answer to your question on page 132), where page navigation is desirable. But in these cases, PDF is usually preferable. And PDF readers have built-in page navigation.
>
> If a large document must be provided in HTML, and must be navigable by page reference, then the implication is that the user (when beginning his session) already knows what page he/she wants. In that case an edit field seems more useful that a large drop-down list.
>
> -- Mike
>
>
>
>
>