E-mail List Archives
Re: sorting column headers
From: Jared Smith
Date: Nov 14, 2012 6:05PM
- Next message: Bryan Garaventa: "Accessible tab generation using HTML5 and content preloading"
- Previous message: Patrick Dunphy: "Re: sorting column headers"
- Next message in Thread: None
- Previous message in Thread: Patrick Dunphy: "Re: sorting column headers"
- View all messages in this Thread
On Wed, Nov 14, 2012 at 5:37 PM, Angela French wrote:
> Would you say, or not, that a link in a table header is understood by screen reader users to indicate sorting functionality?
I don't think this is really an accessibility-specific question. Does
the link alone provide sufficient indication to users in general
(whether blind or not) that it would sort the table? If so, why would
a screen reader user require something additional? If not, fix it so
it does.
Certainly it would not be a compliance failure to have a potentially
confusing link presented to everyone - it would be equally
inaccessible to all users. But that doesn't mean it's a good idea.
If, on the other hand, you are providing a visual indication of sort
functionality (such as an arrow), then it would be necessary for this
information to be presented to all users.
Another thing to consider is efficiency. While it might take some
orientation to learn that a link will sort the table initially, the
burden of this orientation may very well be much less significant than
hearing (or seeing) "sort" for every single table header for the rest
of time.
In short, there's no absolute correct answer to this question.
Jared
- Next message: Bryan Garaventa: "Accessible tab generation using HTML5 and content preloading"
- Previous message: Patrick Dunphy: "Re: sorting column headers"
- Next message in Thread: None
- Previous message in Thread: Patrick Dunphy: "Re: sorting column headers"
- View all messages in this Thread