WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: table paging

for

From: adam solomon
Date: Jan 31, 2011 11:27AM

Just to clarify: I didn't make it clear before that I am talking about
tabular data, not pages of a book. For instance, a list of schools, which
might reach 1000. The number of the pages is not important except insomuch
as finding a particular school is concerned.

On Mon, Jan 31, 2011 at 7:15 PM, E.J. Zufelt < <EMAIL REMOVED> > wrote:

> 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
> >
> >
> >
> >
> > -----Original Message-----
> > From: <EMAIL REMOVED> [mailto:
> <EMAIL REMOVED> ] On Behalf Of Accessibility India
> > Sent: Monday, January 31, 2011 11:37 AM
> > To: WebAIM Discussion List
> > Subject: Re: [WebAIM] table paging
> >
> > I believe the list showed with google search results will be a better
> choice which is almost near to your first option.
> >
> > Thanks & regards
> > Rakesh
> > On 1/30/11, 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/>;
> >>