- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 13 Apr 2011 00:06:32 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv3172
Modified Files:
Overview.html
Log Message:
apply wg decision (whatwg r5999)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4820
retrieving revision 1.4821
diff -u -d -r1.4820 -r1.4821
--- Overview.html 12 Apr 2011 23:49:30 -0000 1.4820
+++ Overview.html 13 Apr 2011 00:06:26 -0000 1.4821
@@ -343,7 +343,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-12-april-2011">Editor's Draft 12 April 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-13-april-2011">Editor's Draft 13 April 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -487,7 +487,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 12 April 2011 Editor's Draft.
+ This specification is the 13 April 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -27269,7 +27269,6 @@
total).</dd>
<dt>Content attributes:</dt>
<dd><a href="#global-attributes">Global attributes</a></dd>
- <dd><code title="attr-table-summary"><a href="#attr-table-summary">summary</a></code> (but see prose)</dd>
<dt>DOM interface:</dt>
<dd>
<pre class="idl">interface <dfn id="htmltableelement">HTMLTableElement</dfn> : <a href="#htmlelement">HTMLElement</a> {
@@ -27287,7 +27286,6 @@
readonly attribute <a href="#htmlcollection">HTMLCollection</a> <a href="#dom-table-rows" title="dom-table-rows">rows</a>;
<a href="#htmlelement">HTMLElement</a> <a href="#dom-table-insertrow" title="dom-table-insertRow">insertRow</a>(in optional long index);
void <a href="#dom-table-deleterow" title="dom-table-deleteRow">deleteRow</a>(in long index);
- attribute DOMString <a href="#dom-table-summary" title="dom-table-summary">summary</a>;
};</pre>
</dd>
</dl><p>The <code><a href="#the-table-element">table</a></code> element <a href="#represents">represents</a> data with
@@ -27316,68 +27314,9 @@
cover that grid without overlap. <span class="impl note">Precise
rules for determining whether this conformance requirement is met
are described in the description of the <a href="#table-model">table
- model</a>.</span><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>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.<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>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">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 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, 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">
+ model</a>.</span><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.<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>
@@ -27630,11 +27569,7 @@
<li><p>Otherwise, the method must remove the <var title="">index</var>th element in the <code title="dom-table-rows"><a href="#dom-table-rows">rows</a></code> collection from its parent.</p>
- </ol><p>The <dfn id="dom-table-summary" title="dom-table-summary"><code>summary</code></dfn> IDL
- attribute must <a href="#reflect">reflect</a> the content attribute of the
- same name.</p>
-
- </div><div class="example">
+ </ol></div><div class="example">
<p>Here is an example of a table being used to mark up a Sudoku
puzzle. Observe the lack of headers, which are not necessary in
@@ -27666,7 +27601,33 @@
</table>
</section></pre>
- </div><h5 id="table-descriptions-techniques"><span class="secno">4.9.1.1 </span>Techniques for describing tables</h5><p>There are a variety of ways to include this information, such as:<dl><dt>In prose, surrounding the table</dt>
+ </div><h5 id="table-descriptions-techniques"><span class="secno">4.9.1.1 </span>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>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:<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>There are a variety of ways to include this information, such as:<dl><dt>In prose, surrounding the table</dt>
<dd>
<div class="example"><pre><p>In the following table, characteristics are given in the second
@@ -66617,9 +66578,7 @@
earlier versions of the language, this attribute was intended as a
way to specify possible targets for fragment identifiers in <a href="#url" title="URL">URLs</a>. The <code title="attr-id"><a href="#the-id-attribute">id</a></code>
attribute should be used instead.<p class="note">In <a href="#syntax">the HTML syntax</a>, specifying a <a href="#syntax-doctype" title="syntax-DOCTYPE">DOCTYPE</a> that is an <a href="#obsolete-permitted-doctype">obsolete
- permitted DOCTYPE</a> will also trigger a warning.<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">
+ permitted DOCTYPE</a> will also trigger a warning.<div class="impl">
<h4 id="warnings-for-obsolete-but-conforming-features"><span class="secno">11.1.1 </span>Warnings for obsolete but conforming features</h4>
@@ -66652,9 +66611,6 @@
attribute on an <code><a href="#the-a-element">a</a></code> element, if its value is not the
empty string.</li>
- <li><p>The presence of a <code title="attr-table-summary"><a href="#attr-table-summary">summary</a></code> attribute on a
- <code><a href="#the-table-element">table</a></code> element.</li> <!-- 2.65% pages -->
-
</ul><p>Conformance checkers must distinguish between pages that have no
conformance errors and have none of these obsolete features, and
pages that have no conformance errors but do have some of these
@@ -66830,6 +66786,11 @@
<dt><dfn id="attr-table-datapagesize" title="attr-table-datapagesize"><code>datapagesize</code></dfn> on <code><a href="#the-table-element">table</a></code> elements</dt>
<dd><p>Unnecessary. Omit it altogether.</dd>
+ <dt><dfn id="attr-table-summary" title="attr-table-summary"><code>summary</code></dfn> on <code><a href="#the-table-element">table</a></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><a href="#the-table-element">table</a></code> section
+ instead.</dd>
+
<dt><dfn id="attr-tdth-abbr" title="attr-tdth-abbr"><code>abbr</code></dfn> on <code><a href="#the-td-element">td</a></code> and <code><a href="#the-th-element">th</a></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"><a href="#the-title-attribute">title</a></code> attribute can also be useful in including more detailed text, so that the cell's contents can be made terse.</p>
@@ -67845,10 +67806,11 @@
attribute DOMString <a href="#dom-table-cellspacing" title="dom-table-cellSpacing">cellSpacing</a>;
attribute DOMString <a href="#dom-table-frame" title="dom-table-frame">frame</a>;
attribute DOMString <a href="#dom-table-rules" title="dom-table-rules">rules</a>;
+ attribute DOMString <a href="#dom-table-summary" title="dom-table-summary">summary</a>;
attribute DOMString <a href="#dom-table-width" title="dom-table-width">width</a>;
};</pre>
- <p>The <dfn id="dom-table-align" title="dom-table-align"><code>align</code></dfn>, <dfn id="dom-table-border" title="dom-table-border"><code>border</code></dfn>, <dfn id="dom-table-frame" title="dom-table-frame"><code>frame</code></dfn>, <dfn id="dom-table-rules" title="dom-table-rules"><code>rules</code></dfn>, and <dfn id="dom-table-width" title="dom-table-width"><code>width</code></dfn>, IDL attributes of
+ <p>The <dfn id="dom-table-align" title="dom-table-align"><code>align</code></dfn>, <dfn id="dom-table-border" title="dom-table-border"><code>border</code></dfn>, <dfn id="dom-table-frame" title="dom-table-frame"><code>frame</code></dfn>, <dfn id="dom-table-summary" title="dom-table-summary"><code>summary</code></dfn>, <dfn id="dom-table-rules" title="dom-table-rules"><code>rules</code></dfn>, and <dfn id="dom-table-width" title="dom-table-width"><code>width</code></dfn>, IDL attributes of
the <code><a href="#the-table-element">table</a></code> element must <a href="#reflect">reflect</a> the
respective content attributes of the same name.</p>
@@ -69359,8 +69321,7 @@
<code><a href="#the-tbody-element">tbody</a></code>*;
<code><a href="#the-tfoot-element">tfoot</a></code>*;
<code><a href="#the-tr-element">tr</a></code>*</td>
- <td><a href="#global-attributes" title="global attributes">globals</a>;
- <code title="attr-table-summary"><a href="#attr-table-summary">summary</a></code></td>
+ <td><a href="#global-attributes" title="global attributes">globals</a></td>
<td><code><a href="#htmltableelement">HTMLTableElement</a></code></td>
<tr><th><code><a href="#the-tbody-element">tbody</a></code></th>
<td>Group of rows in a table</td>
@@ -70360,10 +70321,6 @@
<td> <a href="#the-style-attribute" title="attr-style">HTML elements</a>
<td> Presentational and formatting instructions
<td> CSS declarations*
- <tr><th> <code title="">summary</code>
- <td> <code title="attr-table-summary"><a href="#attr-table-summary">table</a></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> <a href="#attr-tabindex" title="attr-tabindex">HTML elements</a>
<td> Whether the element is focusable, and the relative order of the element for the purposes of sequential focus navigation
Received on Wednesday, 13 April 2011 00:06:35 UTC