- From: Gez Lemon <gez.lemon@gmail.com>
- Date: Wed, 5 Nov 2008 13:25:41 +0000
- To: "Aaron M Leventhal" <aleventh@us.ibm.com>
- Cc: joshue.oconnor@cfit.ie, "Richard Schwerdtfeger" <schwer@us.ibm.com>, "w3c-wai-pf@w3.org PF" <w3c-wai-pf@w3.org>, w3c-wai-pf-request@w3.org, "W3C WAI-XTECH" <wai-xtech@w3.org>
Hi Aaron, > The technique works for most of the sites I've seen. Generally if a form is > lined up by using a <table>, each form control has its own <tr>. Threfore > the contents will be exposed to ATs in the correct order. Yes, that's an example of a table that linearises correctly. Generally, that kind of table isn't going to cause accessibility issues, as it linearises correctly, and the table information is lost when in forms mode (or equivalent cursor mode). The kind of tables that do cause accessibility issues are those where the data doesn't linearise, such as having a navigation item as part of a larger layout table, so the items are visited out of context. As I mentioned in my original reply, I do see a use for role="presentation", but the major accessibility issue with layout tables is with tables that don't linearise. Declaring the table presentational isn't going to help those cases, as the elements will still be out of order. Cheers, Gez -- _____________________________ Supplement your vitamins http://juicystudio.com
Received on Wednesday, 5 November 2008 13:31:27 UTC