Skip to content
Permalink
Browse files

[ac] (0) Discourage cargo-cult authoring that would lead to poor acce…

…ssibility.

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

git-svn-id: http://svn.whatwg.org/webapps@6040 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Apr 28, 2011
1 parent 92269e3 commit 8d9ed709410bbb72b8779b339f4a7fa7d63e2a69
Showing with 84 additions and 70 deletions.
  1. +26 −22 complete.html
  2. +26 −22 index
  3. +32 −26 source
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
</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
<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
48 index
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
</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
<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
58 source
@@ -12091,11 +12091,24 @@ plaintext = *( %x0000-2029 / %x202F-10FFFF )
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 @@ plaintext = *( %x0000-2029 / %x202F-10FFFF )
</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>

</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>

0 comments on commit 8d9ed70

Please sign in to comment.
You can’t perform that action at this time.