[e] (0) try to clarify the effect of the ARIA section based on http:/…

…/www.w3.org/mid/AANLkTikZYUgkd1Ma12mMK6ajo1DB1N9wXXEDcGYr9a0e@mail.gmail.com http://www.w3.org/mid/1300704676.2500.74.camel@shuttle and http://www.w3.org/mid/4D874B52.9060604@intertwingly.net git-svn-id: http://svn.whatwg.org/webapps@6225 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jun 14, 2011 · 4f64fb0 · 4f64fb0
1 parent 7ec2437
commit 4f64fb0
Show file tree

Hide file tree

Showing 3 changed files with 45 additions and 10 deletions.
diff --git a/complete.html b/complete.html
@@ -12000,9 +12000,21 @@ <h4 id=wai-aria><span class=secno>3.2.7 </span><dfn>WAI-ARIA</dfn></h4>
   <div class=impl>
 
   <p>User agents are required to implement ARIA semantics on all
-  <a href=#html-elements>HTML elements</a>, as defined in the ARIA
-  specifications. The <span>implicit ARIA semantics</span> defined
-  below must be recognized by implementations. <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
+  <a href=#html-elements>HTML elements</a>, as defined in the ARIA specifications.
+  The <span>implicit ARIA semantics</span> defined below must be
+  recognized by implementations for the purposes of ARIA processing.
+  <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
+
+  <p class=note>The ARIA attributes defined in the ARIA
+  specifications, and the <span>strong native semantics</span> and
+  <span>default implicit ARIA semantics</span> defined below, do not
+  have any effect on CSS pseudo-class matching, user interface
+  modalities that don't use assistive technologies, or the default
+  actions of user interaction events as described in this
+  specification.</p> <!-- this is a truism, in that there are no
+  requirements that require that those attributes have such an effect,
+  and no requirements that relax the requirements on those effects
+  such that they could be affected by those attributes -->
 
   </div>
 

diff --git a/index b/index
@@ -11990,9 +11990,21 @@ plaintext     = *( %x0000-2029 / %x202F-10FFFF )
   <div class=impl>
 
   <p>User agents are required to implement ARIA semantics on all
-  <a href=#html-elements>HTML elements</a>, as defined in the ARIA
-  specifications. The <span>implicit ARIA semantics</span> defined
-  below must be recognized by implementations. <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
+  <a href=#html-elements>HTML elements</a>, as defined in the ARIA specifications.
+  The <span>implicit ARIA semantics</span> defined below must be
+  recognized by implementations for the purposes of ARIA processing.
+  <a href=#refsARIAIMPL>[ARIAIMPL]</a></p>
+
+  <p class=note>The ARIA attributes defined in the ARIA
+  specifications, and the <span>strong native semantics</span> and
+  <span>default implicit ARIA semantics</span> defined below, do not
+  have any effect on CSS pseudo-class matching, user interface
+  modalities that don't use assistive technologies, or the default
+  actions of user interaction events as described in this
+  specification.</p> <!-- this is a truism, in that there are no
+  requirements that require that those attributes have such an effect,
+  and no requirements that relax the requirements on those effects
+  such that they could be affected by those attributes -->
 
   </div>
 

diff --git a/source b/source
@@ -12575,10 +12575,21 @@ plaintext     = *( %x0000-2029 / %x202F-10FFFF )
   <div class="impl">
 
   <p>User agents are required to implement ARIA semantics on all
-  <span>HTML elements</span>, as defined in the ARIA
-  specifications. The <span>implicit ARIA semantics</span> defined
-  below must be recognized by implementations. <a
-  href="#refsARIAIMPL">[ARIAIMPL]</a></p>
+  <span>HTML elements</span>, as defined in the ARIA specifications.
+  The <span>implicit ARIA semantics</span> defined below must be
+  recognized by implementations for the purposes of ARIA processing.
+  <a href="#refsARIAIMPL">[ARIAIMPL]</a></p>
+
+  <p class="note">The ARIA attributes defined in the ARIA
+  specifications, and the <span>strong native semantics</span> and
+  <span>default implicit ARIA semantics</span> defined below, do not
+  have any effect on CSS pseudo-class matching, user interface
+  modalities that don't use assistive technologies, or the default
+  actions of user interaction events as described in this
+  specification.</p> <!-- this is a truism, in that there are no
+  requirements that require that those attributes have such an effect,
+  and no requirements that relax the requirements on those effects
+  such that they could be affected by those attributes -->
 
   </div>