Merge pull request #437 from w3c/clarify-any-role

Correction: Revisions to 'any role' term description

Author: stevefaulkner

index.html

@@ -168,7 +168,7 @@ ARIA semantics that extend and diverge from HTML
         attribute, allowing for an aural UI that will match the visual presentation of the control.
       p>
       <p>
-        In the following example, a `button` allows for a user to toggle the state of a 
+        In the following example, a `button` element allows for a user to toggle the state of a 
         setting within a web application. The `aria-pressed` attribute is used to 
         augment the `button` element. When in the "pressed" state that information can be
         exposed to users of assistive technologies.
@@ -341,10 +341,9 @@ 
         (role, states, and properties) given in the cell in  the second column of the same row. 
         The third cell in each row defines the ARIA `role` values and `aria-*` attributes which authors MAY specify
         on the element. Where a cell in the third column includes the term <dfn><strong>Anystrong> `role`dfn>
-        it indicates that any `role` value apart from the <a>implicit ARIA semanticsa> `role` value,
-        MAY be used, <span class="addition">unless it is the `generic` role or a role 
-        <a href="#docconformance-deprecated">deprecated by ARIAa>. 
-        The `generic` role and roles deprecated by ARIA SHOULD NOT be used by authorsspan>. 
+        it indicates that any `role` value <span class="addition correction">MAY be used on the element. However, 
+        it is NOT RECOMMENDED for authors to specify the implicit role of the element, the `generic` role, or a role 
+        <a href="#docconformance-deprecated">deprecated by ARIAa> on these elements.span> 
         If a cell in the third column includes the term <dfn><strong>No `role`strong>dfn> it indicates 
         that authors MUST NOT overwrite the implicit ARIA semantics, or native semantics of the HTML element. 
       p>