- From: Becky Gibson <Becky_Gibson@notesdev.ibm.com>
- Date: Mon, 6 Feb 2006 08:23:40 -0500
- To: "Loretta Guarino Reid" <lguarino@adobe.com>
- Cc: public-wcag-teamb@w3.org
<Loretta>
I think 'failure due to using space characters to format tables' should
also discuss that there is no way to associate the table header cells
with the table data cells, to indicate that a cell is intended to be a
header cell, or to navigate directly to a particular cell in a table. So
even if the reading order happens to come out correct (because cells
only contain items that fit on a single line), the technique still
fails.
For both the table and multi-column failures, we might want to appeal to
the guideline itself and point out explicitly that the screen reader is
changing the presentation of the content. If the text were reflowed, or
changed from a fixed to a variable font, or increased in size until
lines no longer fit on the page, similar issues would arise.
</Loretta>
Thanks, Loretta,
I updated the two techniques with this information.
Becky Gibson
Web Accessibility Architect
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com
Received on Monday, 6 February 2006 13:23:50 UTC