Merge branch 'gh-pages' into patch-2

scottaohara · web-flow · commit 8df3f14ec14a · 2020-10-20T07:49:29.000-04:00
diff --git a/.travis.yml b/.travis.yml
@@ -17,5 +17,5 @@ script:
   - npx respec-validator --manifest=echidna-manifest.txt --gh-user=$GH_USER --gh-token=$GH_TOKEN index.html
 
 after_success:
-  - CC="mcaceres@mozilla.com,faulkner.steve@gmail.com"
+  - CC="marcos@marcosc.com,faulkner.steve@gmail.com"
   - '[ "${TRAVIS_PULL_REQUEST}" = "false" ] && curl "https://labs.w3.org/echidna/api/request" --data "cc=$CC" --data "url=$URL" --data "decision=$DECISION" --data "token=$TOKEN"'
diff --git a/index.html b/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <title>ARIA in HTML</title>
-    <script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
+    <script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove" defer></script>
     <script class="remove">
     var respecConfig = {
       editors: [
@@ -33,10 +33,8 @@
       maxTocLevel: 2,
       shortName: "html-aria",
       specStatus: "ED",
-      wg: "Web Applications Working Group",
-      wgPatentURI: "https://www.w3.org/2004/01/pp-impl/114929/status",
+      group: "webapps",
       wgPublicList: "public-html",
-      wgURI: "https://www.w3.org/2019/webapps/",
       xref: true
     };
     </script>
@@ -69,10 +67,10 @@ <h2 id="rules-wd">
         Web developers MAY use the ARIA `role` and `aria-*` attributes on
         <a data-cite="html/dom.html#elements">HTML elements</a>, in accordance
         with the requirements described in [[wai-aria-1.1]], except where these
-        conflict with the 
+        conflict with the
         <dfn><a data-cite="wai-aria-1.1#host_general_conflict">strong native semantics</a></dfn>
-        or are equal to the 
-        <dfn><a data-cite="wai-aria-1.1#implicit_semantics">implicit ARIA semantics</a></dfn> 
+        or are equal to the
+        <dfn><a data-cite="wai-aria-1.1#implicit_semantics">implicit ARIA semantics</a></dfn>
         of a given HTML element. These constraints are intended to prevent
         developers from making assistive technology products report nonsensical
         user interface (UI) information that does not represent the actual UI
@@ -98,7 +96,7 @@ <h2 id="rules-wd">
       <aside class="example">
         The following uses a `role=button` on a `button` element. This is unnecessary, as "button"
         is already exposed as the implicit role for the element. In practice this redundancy will
-        likely not have any unforeseen side effects, other than unnecessarily making the markup 
+        likely not have any unforeseen side effects, other than unnecessarily making the markup
         more verbose, and incorrectly signaling to other developers that this practice is useful.
         <pre class="HTML">
           &lt;button role="button"&gt;...&lt;/button&gt;
@@ -116,9 +114,9 @@ <h2 id="rules-wd">
 
       <aside class="example">
         The following uses a `role=list` on an `ul` element. This is generally unnecessary,
-        because the `ul` element is implicitly exposed as a `role=list`. However, some 
-        user agents suppress a list's implicit ARIA semantics if list markers are removed. 
-        Authors can use `role=list` to reinstate the role if necessary, though this practice 
+        because the `ul` element is implicitly exposed as a `role=list`. However, some
+        user agents suppress a list's implicit ARIA semantics if list markers are removed.
+        Authors can use `role=list` to reinstate the role if necessary, though this practice
         would generally not be recommended, otherwise.
         <pre class="HTML">
           &lt;ul role="list"&gt;...&lt;/ul&gt;
@@ -127,7 +125,7 @@ <h2 id="rules-wd">
 
       <aside class="example">
         The following uses a `role=button` on a `summary` element. This is unnecessary and can
-        result in cross-platform issues, For instance, preventing the element from correctly
+        result in cross-platform issues. For instance, preventing the element from correctly
         exposing its state, and forcing the role of `button`, when it might otherwise be exposed
         with a different role.
         <pre class="HTML">
@@ -146,8 +144,8 @@ <h2 id="docconformance">
       <p>
         The following table provides normative per-element document-conformance
         requirements for the use of ARIA markup in HTML documents and describes
-        the <a>implicit ARIA semantics</a> that apply to 
-        <a data-cite="html/dom.html#elements">HTML elements</a> as defined in 
+        the <a>implicit ARIA semantics</a> that apply to
+        <a data-cite="html/dom.html#elements">HTML elements</a> as defined in
         the [[html-aam-1.0|HTML Accessibility API Mappings 1.0]] specification.
       </p>
       <p>
@@ -163,7 +161,7 @@ <h2 id="docconformance">
 
       <p class="note" id="aria-usage-note">
         While setting an ARIA `role` and/or `aria-*` attribute that matches the
-        <span>implicit ARIA semantics</span> is NOT RECOMMENDED, in some situations explicitly setting 
+        <span>implicit ARIA semantics</span> is NOT RECOMMENDED, in some situations explicitly setting
         these attributes can be helpful. For instance, in user agents which lack specific implicit semantics.
       </p>
 
@@ -2636,12 +2634,12 @@ <h2 id="docconformance">
             </td>
             <td>
               <p>
-                <code>role=<a href="#index-aria-cell">cell</a></code> if a
-                descendant of a `table` element.
+                <code>role=<a href="#index-aria-cell">cell</a></code> if the ancestor
+                `table` element is exposed as a `role=table`.
               </p>
               <p>
-                <code>role=<a href="#index-aria-gridcell">gridcell</a></code> if a
-                descendant of a `table` element with `role=grid` or `treegrid`.
+                <code>role=<a href="#index-aria-gridcell">gridcell</a></code> if the ancestor
+                `table` element is exposed as a `role=grid` or `treegrid`.
               </p>
             </td>
             <td>
@@ -2663,12 +2661,14 @@ <h2 id="docconformance">
             </td>
             <td>
               <p>
-                If a descendant of a `table` element, <code>role=<a href="#index-aria-columnheader">columnheader</a></code> or
-                <a href="#index-aria-rowheader">`rowheader`</a> or <a href="#index-aria-rowheader">`cell`</a> (if not a header).
+                If the ancestor `table` element is exposed as a `role=table`: <code>role=<a href="#index-aria-columnheader">columnheader</a></code>,
+                <a href="#index-aria-rowheader">`rowheader`</a> or <a href="#index-aria-rowheader">`cell`</a> according to
+                <a data-cite="html-aam-1.0#html-element-role-mappings">HTML AAM</a>.
              </p>
               <p>
-                If a descendant of a `table` element with `role=grid` or `treegrid`, <code>role=<a href="#index-aria-columnheader">columnheader</a></code> or
-                <a href="#index-aria-rowheader">`rowheader`</a> or <a href="#index-aria-rowheader">`gridcell`</a> (if not a header).
+                If the ancestor `table` element is exposed as a `role=grid` or `treegrid`: <code>role=<a href="#index-aria-columnheader">columnheader</a></code>,
+                <a href="#index-aria-rowheader">`rowheader`</a> or <a href="#index-aria-rowheader">`gridcell`</a> according to
+                <a data-cite="html-aam-1.0#html-element-role-mappings">HTML AAM</a>.
              </p>
             </td>
             <td>
