WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: table paging

for

From: adam solomon
Date: Mar 1, 2011 11:48PM

Going with the list of links option where there are numbered links and arrow
links to get to a different set of pages: the arrow links are just text -
i.e. one or two arrow characters. Even if we add a title specifying the
function of this link (namely to navigate to the next set of pages) is this
wcag conformed? Title attribute is not well supported in a link where there
is text - and understanding the link's function from the text (arrows) might
be a bit shaky? What say all of you?

On Sun, Feb 6, 2011 at 2:44 PM, < <EMAIL REMOVED> > wrote:

> JAWS versions will read items in a dropdown menu using a particular command
> "alt down arrow" in most cases.
> Chuck
> ----- Original Message -----
> From: "Jordan, Courtney" < <EMAIL REMOVED> >
> To: "WebAIM Discussion List" < <EMAIL REMOVED> >
> Sent: Monday, January 31, 2011 12:46 PM
> Subject: Re: [WebAIM] table paging
>
>
> > 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/>;
> >
> >
> >