- From: Joshue O Connor <joshue.oconnor@cfit.ie>
- Date: Tue, 12 Jul 2011 15:24:18 +0100
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
- CC: Janina Sajka <janina@rednote.net>, Judy Brewer <jbrewer@w3.org>, Laura Carlson <laura.lee.carlson@gmail.com>, John Foliot <jfoliot@stanford.edu>, lwatson@nomensa.com, "Katie @ GMAIL" <ryladog@gmail.com>
I formally request to reopen ISSUE 32 - table @summary. The table summary decision by the HTML WG chairs gives three examples of new information that would be acceptable in re-opening ISSUE 32.[1] They were: 1) identification of specific use cases 2) first hand statements from authors of development tools, and 3) identification of specific operational problems with aria-describedby. Vlad Alexander is an author of a development tool who provides a useful example of how @summary is still a valid attribute. [2] My CP also highlights how the current spec examples ( in 4.9.1.1 Techniques for describing tables) are not only not backwards compatible with legacy Assistive Technologies but do not even demonstrate the same user experience that is possible with @summary using current 'state of the art' Assistive Technologies (such as JAWS 12, and VoiceOver). [3] I trust that the combination of this statement by an established development tool author, as well as the observations outlined in my CP are sufficient new information which will suffice to help to reopen the issue. [4] Sincerely Joshue O Connor [1] http://lists.w3.org/Archives/Public/public-html/2011Apr/0092.html [2] http://rebuildingtheweb.com/en/aria-for-content-doomed/ [3] http://www.w3.org/TR/2011/WD-html5-20110525/tabular-data.html#table-descriptions-techniques [4] http://www.w3.org/WAI/PF/HTML/wiki/Category:Table_Summary
Received on Tuesday, 12 July 2011 14:24:49 UTC