WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: Sortable Table Question

for

From: Miller, Lisa F (LMS)
Date: Apr 1, 2003 2:49PM

That was my concern, that the reader would not know to start over at the top
- but based on a message from Tim, the user would already be at the top of
the table anyway. The current app we have does not actually do a page
refresh - it truncates and then rebuilds the table in place. Would this
type of dynamic table building cause problems? By the way, Tim gives a much
better description/example than I do of a sortable table - Thanks Tim!

On a side note, is there any opinion on what would be considered "too many
rows" in one table? - or "too many columns"?

Some background: we are looking to redesign the app for 508, and I am trying
to identify those "things" which would cause problems, and to come up with a
better, probably simpler design. This dynamic table sorting jumped out at
me, but I was not sure if it would be a real problem or not. Our sponsor
defines "508 Complient" as being "JAWS Complient", if that helps any.

Thanks,
Lisa

> -----Original Message-----
> From: Joel Ward [SMTP: <EMAIL REMOVED> ]
> Sent: Tuesday, April 01, 2003 1:42 PM
> To: <EMAIL REMOVED>
> Subject: Re: Sortable Table Question
>
> > What method is being employed to "re-order" the table? My first guess
> is
> > that since it is probably a page re-fresh the screen readers would
> probably
> > start over again at row 1, cell 1.
>
> And I don't see how this is necessarily a bad thing. If a table is
> re-sorted, wouldn't you need to start reading it over again since items
> are
> in a different order? Otherwise, how would you know where to start
> re-reading the table?
>
> Lisa, are you worried that some assistive technology would not start
> reading
> the page over if it was re-sorted?
>
>
>
> ----
> To subscribe, unsubscribe, or view list archives,
> visit http://www.webaim.org/discussion/


----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/