[html5] r6040 - [ac] (0) Discourage cargo-cult authoring that would lead to poor accessibility. [...]
whatwg at whatwg.org
whatwg at whatwg.org
Thu Apr 28 14:51:41 PDT 2011
Author: ianh
Date: 2011-04-28 14:51:40 -0700 (Thu, 28 Apr 2011)
New Revision: 6040
Modified:
complete.html
index
source
Log:
[ac] (0) Discourage cargo-cult authoring that would lead to poor accessibility.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=11557
Modified: complete.html
===================================================================
--- complete.html 2011-04-28 19:34:13 UTC (rev 6039)
+++ complete.html 2011-04-28 21:51:40 UTC (rev 6040)
@@ -11641,11 +11641,19 @@
and <code title=attr-aria-*>aria-*</code> attributes on <a href=#html-elements>HTML
elements</a>, in accordance with the requirements described in
the ARIA specifications, except where these conflict with the
- <span>strong native semantics</span> described below. These
+ <span>strong native semantics</span> or are equal to the
+ <span>default implied ARIA semantics</span> described below. These
exceptions are intended to prevent authors from making assistive
technology products report nonsensical states that do not represent
the actual state of the document. <a href=#refsARIA>[ARIA]</a></p>
+ <p>Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
+ conflicts with the semantics described in the following table,
+ except that the <code title=attr-aria-role-presentation>presentation</code> role may
+ always be used. Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes to values that match
+ the <span>default implicit ARIA semantics</span> defined in the
+ following two tables.</p>
+
<div class=impl>
<p>User agents are required to implement ARIA semantics on all
@@ -11656,21 +11664,16 @@
</div>
<p>The following table defines the <span>strong native
- semantics</span> <span class=impl>and corresponding <span>implicit
- ARIA semantics</span></span> that apply to <a href=#html-elements>HTML
- elements</a>. Each language feature (element or attribute) in a
- cell in the first column implies the ARIA semantics (role, states,
- and/or properties) given in the cell in the second column of the
- same row. Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
- conflicts with the semantics described in the following table,
- except that the <code title=attr-aria-role-presentation>presentation</code> role may
- always be used. <span class=impl>When multiple rows apply to an
- element, the role from the last row to define a role must be
- applied, and the states and properties from all the rows must be
- combined.</span></p>
+ semantics</span> and corresponding <span>default implicit ARIA
+ semantics</span> that apply to <a href=#html-elements>HTML elements</a>. Each
+ language feature (element or attribute) in a cell in the first
+ column implies the ARIA semantics (role, states, and/or properties)
+ given in the cell in the second column of the same row. <span class=impl>When multiple rows apply to an element, the role from
+ the last row to define a role must be applied, and the states and
+ properties from all the rows must be combined.</span></p>
<table id=table-aria-strong><thead><tr><th>Language feature
- <th>Strong native semantics <span class=impl>and implied ARIA semantics</span>
+ <th>Strong native semantics and default implied ARIA semantics
<tbody><tr><td><code><a href=#the-area-element>area</a></code> element that creates a <a href=#hyperlink>hyperlink</a>
<td><code title=attr-aria-role-link>link</code> role
@@ -11886,14 +11889,15 @@
<td>The <code title=title-aria-invalid>aria-invalid</code> state set to "true"
</table><p>Some <a href=#html-elements>HTML elements</a> have native semantics that can be
- overridden. The following table lists these elements<span class=impl> and their <span>implicit ARIA semantics</span></span>,
- along with the restrictions that apply to those elements. Each
- language feature (element or attribute) in a cell in the first
- column implies, unless otherwise overridden, the ARIA semantic (role,
- state, or property) given in the cell in the second column of the
- same row, but this semantic may be overridden under the conditions
- listed in the cell in the third column of that row. In addition, any
- element may be given the <code title=attr-aria-role-presentation>presentation</code> role,
+ overridden. The following table lists these elements and their
+ <span>default implicit ARIA semantics</span>, along with the
+ restrictions that apply to those elements. Each language feature
+ (element or attribute) in a cell in the first column implies, unless
+ otherwise overridden, the ARIA semantic (role, state, or property)
+ given in the cell in the second column of the same row, but this
+ semantic may be overridden under the conditions listed in the cell
+ in the third column of that row. In addition, any element may be
+ given the <code title=attr-aria-role-presentation>presentation</code> role,
regardless of the restrictions below.</p>
<table id=table-aria-weak><thead><tr><th>Language feature
Modified: index
===================================================================
--- index 2011-04-28 19:34:13 UTC (rev 6039)
+++ index 2011-04-28 21:51:40 UTC (rev 6040)
@@ -11661,11 +11661,19 @@
and <code title=attr-aria-*>aria-*</code> attributes on <a href=#html-elements>HTML
elements</a>, in accordance with the requirements described in
the ARIA specifications, except where these conflict with the
- <span>strong native semantics</span> described below. These
+ <span>strong native semantics</span> or are equal to the
+ <span>default implied ARIA semantics</span> described below. These
exceptions are intended to prevent authors from making assistive
technology products report nonsensical states that do not represent
the actual state of the document. <a href=#refsARIA>[ARIA]</a></p>
+ <p>Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
+ conflicts with the semantics described in the following table,
+ except that the <code title=attr-aria-role-presentation>presentation</code> role may
+ always be used. Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes to values that match
+ the <span>default implicit ARIA semantics</span> defined in the
+ following two tables.</p>
+
<div class=impl>
<p>User agents are required to implement ARIA semantics on all
@@ -11676,21 +11684,16 @@
</div>
<p>The following table defines the <span>strong native
- semantics</span> <span class=impl>and corresponding <span>implicit
- ARIA semantics</span></span> that apply to <a href=#html-elements>HTML
- elements</a>. Each language feature (element or attribute) in a
- cell in the first column implies the ARIA semantics (role, states,
- and/or properties) given in the cell in the second column of the
- same row. Authors must not set the ARIA <code title=attr-aria-role>role</code> and <code title=attr-aria-*>aria-*</code> attributes in a manner that
- conflicts with the semantics described in the following table,
- except that the <code title=attr-aria-role-presentation>presentation</code> role may
- always be used. <span class=impl>When multiple rows apply to an
- element, the role from the last row to define a role must be
- applied, and the states and properties from all the rows must be
- combined.</span></p>
+ semantics</span> and corresponding <span>default implicit ARIA
+ semantics</span> that apply to <a href=#html-elements>HTML elements</a>. Each
+ language feature (element or attribute) in a cell in the first
+ column implies the ARIA semantics (role, states, and/or properties)
+ given in the cell in the second column of the same row. <span class=impl>When multiple rows apply to an element, the role from
+ the last row to define a role must be applied, and the states and
+ properties from all the rows must be combined.</span></p>
<table id=table-aria-strong><thead><tr><th>Language feature
- <th>Strong native semantics <span class=impl>and implied ARIA semantics</span>
+ <th>Strong native semantics and default implied ARIA semantics
<tbody><tr><td><code><a href=#the-area-element>area</a></code> element that creates a <a href=#hyperlink>hyperlink</a>
<td><code title=attr-aria-role-link>link</code> role
@@ -11906,14 +11909,15 @@
<td>The <code title=title-aria-invalid>aria-invalid</code> state set to "true"
</table><p>Some <a href=#html-elements>HTML elements</a> have native semantics that can be
- overridden. The following table lists these elements<span class=impl> and their <span>implicit ARIA semantics</span></span>,
- along with the restrictions that apply to those elements. Each
- language feature (element or attribute) in a cell in the first
- column implies, unless otherwise overridden, the ARIA semantic (role,
- state, or property) given in the cell in the second column of the
- same row, but this semantic may be overridden under the conditions
- listed in the cell in the third column of that row. In addition, any
- element may be given the <code title=attr-aria-role-presentation>presentation</code> role,
+ overridden. The following table lists these elements and their
+ <span>default implicit ARIA semantics</span>, along with the
+ restrictions that apply to those elements. Each language feature
+ (element or attribute) in a cell in the first column implies, unless
+ otherwise overridden, the ARIA semantic (role, state, or property)
+ given in the cell in the second column of the same row, but this
+ semantic may be overridden under the conditions listed in the cell
+ in the third column of that row. In addition, any element may be
+ given the <code title=attr-aria-role-presentation>presentation</code> role,
regardless of the restrictions below.</p>
<table id=table-aria-weak><thead><tr><th>Language feature
Modified: source
===================================================================
--- source 2011-04-28 19:34:13 UTC (rev 6039)
+++ source 2011-04-28 21:51:40 UTC (rev 6040)
@@ -12091,11 +12091,24 @@
and <code title="attr-aria-*">aria-*</code> attributes on <span>HTML
elements</span>, in accordance with the requirements described in
the ARIA specifications, except where these conflict with the
- <span>strong native semantics</span> described below. These
+ <span>strong native semantics</span> or are equal to the
+ <span>default implied ARIA semantics</span> described below. These
exceptions are intended to prevent authors from making assistive
technology products report nonsensical states that do not represent
the actual state of the document. <a href="#refsARIA">[ARIA]</a></p>
+ <p>Authors must not set the ARIA <code
+ title="attr-aria-role">role</code> and <code
+ title="attr-aria-*">aria-*</code> attributes in a manner that
+ conflicts with the semantics described in the following table,
+ except that the <code
+ title="attr-aria-role-presentation">presentation</code> role may
+ always be used. Authors must not set the ARIA <code
+ title="attr-aria-role">role</code> and <code
+ title="attr-aria-*">aria-*</code> attributes to values that match
+ the <span>default implicit ARIA semantics</span> defined in the
+ following two tables.</p>
+
<div class="impl">
<p>User agents are required to implement ARIA semantics on all
@@ -12107,27 +12120,20 @@
</div>
<p>The following table defines the <span>strong native
- semantics</span> <span class="impl">and corresponding <span>implicit
- ARIA semantics</span></span> that apply to <span>HTML
- elements</span>. Each language feature (element or attribute) in a
- cell in the first column implies the ARIA semantics (role, states,
- and/or properties) given in the cell in the second column of the
- same row. Authors must not set the ARIA <code
- title="attr-aria-role">role</code> and <code
- title="attr-aria-*">aria-*</code> attributes in a manner that
- conflicts with the semantics described in the following table,
- except that the <code
- title="attr-aria-role-presentation">presentation</code> role may
- always be used. <span class="impl">When multiple rows apply to an
- element, the role from the last row to define a role must be
- applied, and the states and properties from all the rows must be
- combined.</span></p>
+ semantics</span> and corresponding <span>default implicit ARIA
+ semantics</span> that apply to <span>HTML elements</span>. Each
+ language feature (element or attribute) in a cell in the first
+ column implies the ARIA semantics (role, states, and/or properties)
+ given in the cell in the second column of the same row. <span
+ class="impl">When multiple rows apply to an element, the role from
+ the last row to define a role must be applied, and the states and
+ properties from all the rows must be combined.</span></p>
<table id="table-aria-strong">
<thead>
<tr>
<th>Language feature
- <th>Strong native semantics <span class="impl">and implied ARIA semantics</span>
+ <th>Strong native semantics and default implied ARIA semantics
<tbody>
@@ -12409,15 +12415,15 @@
</table>
<p>Some <span>HTML elements</span> have native semantics that can be
- overridden. The following table lists these elements<span
- class="impl"> and their <span>implicit ARIA semantics</span></span>,
- along with the restrictions that apply to those elements. Each
- language feature (element or attribute) in a cell in the first
- column implies, unless otherwise overridden, the ARIA semantic (role,
- state, or property) given in the cell in the second column of the
- same row, but this semantic may be overridden under the conditions
- listed in the cell in the third column of that row. In addition, any
- element may be given the <code
+ overridden. The following table lists these elements and their
+ <span>default implicit ARIA semantics</span>, along with the
+ restrictions that apply to those elements. Each language feature
+ (element or attribute) in a cell in the first column implies, unless
+ otherwise overridden, the ARIA semantic (role, state, or property)
+ given in the cell in the second column of the same row, but this
+ semantic may be overridden under the conditions listed in the cell
+ in the third column of that row. In addition, any element may be
+ given the <code
title="attr-aria-role-presentation">presentation</code> role,
regardless of the restrictions below.</p>
More information about the Commit-Watchers
mailing list