Short URL: http://html5.org/r/5999
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 5999 | 7539 | 2011-04-13 00:06 |
Index: source
===================================================================
--- source (revision 5998)
+++ source (revision 5999)
@@ -41182,7 +41182,6 @@
total).</dd>
<dt>Content attributes:</dt>
<dd><span>Global attributes</span></dd>
- <dd><code title="attr-table-summary">summary</code> (but see prose)</dd>
<dt>DOM interface:</dt>
<dd>
<pre class="idl">interface <dfn>HTMLTableElement</dfn> : <span>HTMLElement</span> {
@@ -41200,7 +41199,6 @@
readonly attribute <span>HTMLCollection</span> <span title="dom-table-rows">rows</span>;
<span>HTMLElement</span> <span title="dom-table-insertRow">insertRow</span>(in optional long index);
void <span title="dom-table-deleteRow">deleteRow</span>(in long index);
- attribute DOMString <span title="dom-table-summary">summary</span>;
};</pre>
</dd>
</dl>
@@ -41244,91 +41242,11 @@
are described in the description of the <span>table
model</span>.</span></p>
- <p id="table-descriptions">For tables that consist of more than just
- a grid of cells with headers in the first row and headers in the
- first column, and for any table in general where the reader might
- have difficulty understanding the content, authors should include
- explanatory information introducing the table. This information is
- useful for all users, but is especially useful for users who cannot
- see the table, e.g. users of screen readers.</p>
+ <p>Authors are encouraged to provide information describing how to
+ interpret complex tables. Guidance on how <a
+ href="#table-descriptions-techniques">provide such information</a>
+ is given below.</p>
- <p>Such explanatory information should introduce the purpose of the
- table, outline its basic cell structure, highlight any trends or
- patterns, and generally teach the user how to use the table.</p>
-
- <div class="example">
-
- <p>For instance, the following table:</p>
-
- <table>
- <caption>Characteristics with positive and negative sides</caption>
- <thead>
- <tr>
- <th id="n"> Negative
- <th> Characteristic
- <th> Positive
- <tbody>
- <tr>
- <td headers="n r1"> Sad
- <th id=r1> Mood
- <td> Happy
- <tr>
- <td headers="n r2"> Failing
- <th id=r2> Grade
- <td> Passing
- </table>
-
- <p>...might benefit from a description explaining the way the table
- is laid out, something like "Characteristics are given in the
- second column, with the negative side in the left column and the
- positive side in the right column".</p>
-
- </div>
-
- <p><a href="#table-descriptions-techniques">Guidance on how to
- provide such information</a> is provided below.</p>
-
- <p>The <dfn title="attr-table-summary"><code>summary</code></dfn>
- attribute on <code>table</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">techniques</a> described
- <!--in the <code>table</code> section--> below 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>
-
- <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">summary</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>caption</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, might 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>
- -->
-
<div class="impl">
<p>If a <code>table</code> element has a <code
@@ -41612,10 +41530,6 @@
</ol>
- <p>The <dfn title="dom-table-summary"><code>summary</code></dfn> IDL
- attribute must <span>reflect</span> the content attribute of the
- same name.</p>
-
</div>
<div class="example">
@@ -41655,6 +41569,50 @@
<h5 id="table-descriptions-techniques">Techniques for describing tables</h5>
+ <p id="table-descriptions">For tables that consist of more than just
+ a grid of cells with headers in the first row and headers in the
+ first column, and for any table in general where the reader might
+ have difficulty understanding the content, authors should include
+ explanatory information introducing the table. This information is
+ useful for all users, but is especially useful for users who cannot
+ see the table, e.g. users of screen readers.</p>
+
+ <p>Such explanatory information should introduce the purpose of the
+ table, outline its basic cell structure, highlight any trends or
+ patterns, and generally teach the user how to use the table.</p>
+
+ <!--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, might 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>For instance, the following table:</p>
+
+ <table>
+ <caption>Characteristics with positive and negative sides</caption>
+ <thead>
+ <tr>
+ <th id="n"> Negative
+ <th> Characteristic
+ <th> Positive
+ <tbody>
+ <tr>
+ <td headers="n r1"> Sad
+ <th id=r1> Mood
+ <td> Happy
+ <tr>
+ <td headers="n r2"> Failing
+ <th id=r2> Grade
+ <td> Passing
+ </table>
+
+ <p>...might benefit from a description explaining the way the table
+ is laid out, something like "Characteristics are given in the
+ second column, with the negative side in the left column and the
+ positive side in the right column".</p>
+
<p>There are a variety of ways to include this information, such as:</p>
<dl>
@@ -103896,11 +103854,7 @@
title="syntax-DOCTYPE">DOCTYPE</span> that is an <span>obsolete
permitted DOCTYPE</span> will also trigger a warning.</p>
- <p class="note">The <code title="attr-table-summary">summary</code>
- attribute, defined in the <code>table</code> section, will also
- trigger a warning.</p>
-
<div class="impl">
<h4>Warnings for obsolete but conforming features</h4>
@@ -103941,10 +103895,6 @@
attribute on an <code>a</code> element, if its value is not the
empty string.</p></li>
- <li><p>The presence of a <code
- title="attr-table-summary">summary</code> attribute on a
- <code>table</code> element.</p></li> <!-- 2.65% pages -->
-
</ul>
<p>Conformance checkers must distinguish between pages that have no
@@ -104145,6 +104095,12 @@
<dt><dfn title="attr-table-datapagesize"><code>datapagesize</code></dfn> on <code>table</code> elements</dt>
<dd><p>Unnecessary. Omit it altogether.</p></dd>
+ <dt><dfn title="attr-table-summary"><code>summary</code></dfn> on <code>table</code> elements</dt><!-- 2.65% pages -->
+ <dd><p>Use one of the <a
+ href="#table-descriptions-techniques">techniques for describing
+ tables</a> given in the <code>table</code> section
+ instead.</p></dd>
+
<dt><dfn title="attr-tdth-abbr"><code>abbr</code></dfn> on <code>td</code> and <code>th</code> elements</dt>
<dd><p>Use text that begins in an unambiguous and terse manner, and include any more elaborate text after that. The <code title="attr-title">title</code> attribute can also be useful in including more detailed text, so that the cell's contents can be made terse.</p>
@@ -105397,12 +105353,14 @@
attribute DOMString <span title="dom-table-cellSpacing">cellSpacing</span>;
attribute DOMString <span title="dom-table-frame">frame</span>;
attribute DOMString <span title="dom-table-rules">rules</span>;
+ attribute DOMString <span title="dom-table-summary">summary</span>;
attribute DOMString <span title="dom-table-width">width</span>;
};</pre>
<p>The <dfn title="dom-table-align"><code>align</code></dfn>, <dfn
title="dom-table-border"><code>border</code></dfn>, <dfn
title="dom-table-frame"><code>frame</code></dfn>, <dfn
+ title="dom-table-summary"><code>summary</code></dfn>, <dfn
title="dom-table-rules"><code>rules</code></dfn>, and <dfn
title="dom-table-width"><code>width</code></dfn>, IDL attributes of
the <code>table</code> element must <span>reflect</span> the
@@ -107698,8 +107656,7 @@
<code>tbody</code>*;
<code>tfoot</code>*;
<code>tr</code>*</td>
- <td><span title="global attributes">globals</span>;
- <code title="attr-table-summary">summary</code></td>
+ <td><span title="global attributes">globals</span></td>
<td><code>HTMLTableElement</code></td>
</tr>
@@ -108948,11 +108905,6 @@
<td> Presentational and formatting instructions
<td> CSS declarations*
<tr>
- <th> <code title="">summary</code>
- <td> <code title="attr-table-summary">table</code>
- <td> Explanatory text for complex tables for users of screen readers
- <td> <a href="#attribute-text">Text</a>*
- <tr>
<th> <code title="">tabindex</code>
<td> <span title="attr-tabindex">HTML elements</span>
<td> Whether the element is focusable, and the relative order of the element for the purposes of sequential focus navigation