- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 05 Aug 2009 23:16:17 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv25827 Modified Files: Overview.html Log Message: Move summary text to table section. (whatwg r3542) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2736 retrieving revision 1.2737 diff -u -d -r1.2736 -r1.2737 --- Overview.html 5 Aug 2009 01:34:16 -0000 1.2736 +++ Overview.html 5 Aug 2009 23:16:14 -0000 1.2737 @@ -23622,7 +23622,44 @@ </dd> </dl><p>Authors may also use other techniques, or combinations of the - above techniques, as appropriate.<div class="impl"> + above techniques, as appropriate.<p>The <dfn id="attr-table-summary" title="attr-table-summary"><code>summary</code></dfn> + attribute on <code><a href="#the-table-element">table</a></code> elements was suggested in earlier + versions of the language as a technique for providing explanatory + text for complex tables for users of screen readers. One of the <a href="#table-descriptions">techniques</a> described <!--in the + <code>table</code> section--> above should be used + instead. <!--Authors should not specify the <code + title="attr-table-summary">summary</code> attribute on + <code>table</code> elements. --> <!-- 2.65% pages --><p class="note">In particular, authors are encouraged to consider + whether their explanatory text for tables is likely to be useful to + the visually impaired: if their text would not be useful, then it is + best to not include a <code title="attr-table-summary"><a href="#attr-table-summary">summary</a></code> attribute. Similarly, if + their explanatory text could help someone who is not visually + impaired, e.g. someone who is seeing the table for the first time, + then the text would be more useful before the table or in the + <code><a href="#the-caption-element">caption</a></code>. For example, describing the conclusions of the + data in a table is useful to everyone; explaining how to read the + table, if not obvious from the headers alone, is useful to everyone; + describing the structure of the table, if it is easy to grasp + visually, may not be useful to everyone, but it might also not be + useful to users who can quickly navigate the table with an + accessibility tool.</p><!-- + <p class="note">Use of the <code + title="attr-table-summary">summary</code> attribute is discouraged + because in practice it is poorly understood. Because the attribute + is not exposed in visual user agents, authors who have included it + have typically not been able to test it, and have therefore set the + attribute to values that are of no use to users of accessibility + tools. This has lead to accessibility tools introducing heuristics + to try to avoid exposing such usage of the attribute to users. Even + the few authors who have made the best use of the attribute have + often misused it, for example by including text that would in fact + be useful for all users, or that is redundant with other information + on the page separate from the table.</p> + + <p class="XXX">It has been suggested that the summary="" attribute + should not be obsolete, and the working group may vote on the matter + at some future point.</p> + --><div class="impl"> <p>If a <code><a href="#the-table-element">table</a></code> element has a <code title="attr-table-summary"><a href="#attr-table-summary">summary</a></code> attribute, the user agent may report the contents of that attribute to the user.</p> @@ -64545,25 +64582,9 @@ empty string. In earlier versions of the language, this attribute served a similar role as the <code title="attr-id"><a href="#the-id-attribute">id</a></code> attribute. The <code title="attr-id"><a href="#the-id-attribute">id</a></code> attribute should be - used instead.<p>Authors should not specify the <dfn id="attr-table-summary" title="attr-table-summary"><code>summary</code></dfn> attribute on - <code><a href="#the-table-element">table</a></code> elements. <!-- 2.65% pages --> This attribute was - suggested in earlier versions of the language as a technique for - providing explanatory text for complex tables for users of screen - readers. One of the <a href="#table-descriptions">techniques</a> - described in the <code><a href="#the-table-element">table</a></code> section should be used - instead.<p class="note">Use of the <code title="attr-table-summary"><a href="#attr-table-summary">summary</a></code> attribute is discouraged - because in practice it is poorly understood. Because the attribute - is not exposed in visual user agents, authors who have included it - have typically not been able to test it, and have therefore set the - attribute to values that are of no use to users of accessibility - tools. This has lead to accessibility tools introducing heuristics - to try to avoid exposing such usage of the attribute to users. Even - the few authors who have made the best use of the attribute have - often misused it, for example by including text that would in fact - be useful for all users, or that is redundant with other information - on the page separate from the table.<p class="XXX">It has been suggested that the summary="" attribute - should not be obsolete, and the working group may vote on the matter - at some future point.<div class="impl"> + used instead.<p class="note">The <code title="attr-table-summary"><a href="#attr-table-summary">summary</a></code> + attribute, defined in the <code><a href="#the-table-element">table</a></code> section, will also + trigger a warning.<div class="impl"> <h4 id="warnings-for-obsolete-but-conforming-features"><span class="secno">12.1.1 </span>Warnings for obsolete but conforming features</h4>
Received on Wednesday, 5 August 2009 23:16:27 UTC