Skip to content
Browse files

[c] (2) apply wg decision

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7539

git-svn-id: http://svn.whatwg.org/webapps@5999 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
1 parent 9101289 commit 7d36a2fa9773f00f4baa73e2d656c6a30714238f @Hixie Hixie committed
Showing with 155 additions and 297 deletions.
  1. +49 −96 complete.html
  2. +49 −96 index
  3. +57 −105 source
View
145 complete.html
@@ -239,7 +239,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>Web Applications 1.0</h1>
- <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 12 April 2011</h2>
+ <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 13 April 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -37097,7 +37097,6 @@ <h4 id=the-table-element><span class=secno>4.9.1 </span>The <dfn><code>table</co
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> {
@@ -37115,7 +37114,6 @@ <h4 id=the-table-element><span class=secno>4.9.1 </span>The <dfn><code>table</co
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
@@ -37156,80 +37154,9 @@ <h4 id=the-table-element><span class=secno>4.9.1 </span>The <dfn><code>table</co
are described in the description of the <a href=#table-model>table
model</a>.</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>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 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>
-
- <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>
- -->
+ <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>
<div class=impl>
@@ -37486,11 +37413,7 @@ <h4 id=the-table-element><span class=secno>4.9.1 </span>The <dfn><code>table</co
<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>
+ </ol></div>
<div class=example>
@@ -37529,6 +37452,42 @@ <h4 id=the-table-element><span class=secno>4.9.1 </span>The <dfn><code>table</co
<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>
+
+ <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><dt>In prose, surrounding the table</dt>
@@ -91606,10 +91565,6 @@ <h3 id=obsolete-but-conforming-features><span class=secno>16.1 </span>Obsolete b
<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>
- <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.</p>
-
<div class=impl>
@@ -91644,9 +91599,6 @@ <h4 id=warnings-for-obsolete-but-conforming-features><span class=secno>16.1.1 </
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
@@ -91831,6 +91783,11 @@ <h3 id=non-conforming-features><span class=secno>16.2 </span>Non-conforming feat
<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>
@@ -92846,10 +92803,11 @@ <h4 id=other-elements,-attributes-and-apis><span class=secno>16.3.4 </span>Other
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>
@@ -94761,8 +94719,7 @@ <h3 class=no-num id=elements-1>Elements</h3>
<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>
@@ -95824,10 +95781,6 @@ <h3 class=no-num id=element-content-categories>Element content categories</h3>
<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
View
145 index
@@ -243,7 +243,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 12 April 2011</h2>
+ <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 13 April 2011</h2>
</hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -37102,7 +37102,6 @@ function AddCloud(data, x, y) { ... }</pre>
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> {
@@ -37120,7 +37119,6 @@ function AddCloud(data, x, y) { ... }</pre>
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
@@ -37161,80 +37159,9 @@ function AddCloud(data, x, y) { ... }</pre>
are described in the description of the <a href=#table-model>table
model</a>.</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>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 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>
-
- <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>
- -->
+ <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>
<div class=impl>
@@ -37491,11 +37418,7 @@ function AddCloud(data, x, y) { ... }</pre>
<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>
+ </ol></div>
<div class=example>
@@ -37534,6 +37457,42 @@ function AddCloud(data, x, y) { ... }</pre>
<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>
+
+ <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><dt>In prose, surrounding the table</dt>
@@ -87567,10 +87526,6 @@ if (s = prompt('What is your name?')) {
<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>
- <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.</p>
-
<div class=impl>
@@ -87605,9 +87560,6 @@ if (s = prompt('What is your name?')) {
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
@@ -87792,6 +87744,11 @@ if (s = prompt('What is your name?')) {
<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>
@@ -88807,10 +88764,11 @@ interface <a href=#htmltableelement>HTMLTableElement</a> {
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>
@@ -90722,8 +90680,7 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<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>
@@ -91785,10 +91742,6 @@ interface <a href=#htmldocument>HTMLDocument</a> {
<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
View
162 source
@@ -41182,7 +41182,6 @@ function AddCloud(data, x, y) { ... }</pre>
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 @@ function AddCloud(data, x, y) { ... }</pre>
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,90 +41242,10 @@ function AddCloud(data, x, y) { ... }</pre>
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>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>
- -->
+ <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>
<div class="impl">
@@ -41612,10 +41530,6 @@ function AddCloud(data, x, y) { ... }</pre>
</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 @@ function AddCloud(data, x, y) { ... }</pre>
<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,10 +103854,6 @@ if (s = prompt('What is your name?')) {
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">
@@ -103941,10 +103895,6 @@ if (s = prompt('What is your name?')) {
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 @@ if (s = prompt('What is your name?')) {
<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 @@ interface <span>HTMLTableElement</span> {
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 @@ interface <span>HTMLDocument</span> {
<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 @@ interface <span>HTMLDocument</span> {
<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

0 comments on commit 7d36a2f

Please sign in to comment.
Something went wrong with that request. Please try again.