From cbd1e1fbef443174f91d853445701648e7e17fb2 Mon Sep 17 00:00:00 2001
From: "Patrick H. Lauke" <redux@splintered.co.uk>
Date: Sat, 25 Jul 2020 12:53:08 +0100
Subject: [PATCH 01/11] Softening language around explicitly assigning implicit
 ARIA semantics

Closes #236
---
 index.html | 32 ++++++++++++++++++--------------
 1 file changed, 18 insertions(+), 14 deletions(-)

diff --git a/index.html b/index.html
index 9ff3d7da..9afe1e4b 100644
--- a/index.html
+++ b/index.html
@@ -75,9 +75,9 @@ <h2 id="rules-wd">
       <p>
         Web developers MUST NOT use the ARIA `role` and `aria-*` attributes in
         a manner that conflicts with the semantics described in the
-        [[[#docconformance]]] table. Web developers SHOULD NOT set the ARIA
-        `role` and `aria-*` attributes to values that match the <a>implicit
-        ARIA semantics</a> defined in the table.
+        [[[#docconformance]]] table. Web developers are discouraged from setting
+        the ARIA `role` and `aria-*` attributes to values that match the
+        <a>implicit ARIA semantics</a> defined in the table, as this is unnecessary.
       </p>
       <aside class="example">
         The following uses a `role=heading` on a `button` element. This is not
@@ -107,13 +107,19 @@ <h2 id="docconformance">
         used. Where a cell in the third column includes the term
         <dfn><strong>Any</strong> `role`</dfn> it indicates that any `role`
         value apart from the <a>implicit ARIA semantics</a> `role` value, MAY
-        be used. If an 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.
+        be used. If an 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>
 
       <p class="note" id="aria-usage-note">
         Setting an ARIA `role` and/or `aria-*` attribute that matches the
-        <span>implicit ARIA semantics</span> is unnecessary and is NOT
-        RECOMMENDED as these properties are already set by the browser.
+        <span>implicit ARIA semantics</span> is unnecessary, as these properties
+        are already set by the browser. However, explicitly setting these attributes
+        won't have an adverse effect (provided that they are correct and indeed
+        match the implicit semantics) - and this practice may be necessary when
+        supporting older user agents which lack specific implicit semantics, or
+        when working around browser bugs.
       </p>
 
       <table class="simple">
@@ -126,10 +132,7 @@ <h2 id="docconformance">
           </th>
           <th>
             <p id="implicit">
-              Implicit ARIA semantics -
-            </p>
-            <p>
-              SHOULD NOT be used
+              Implicit ARIA semantics <small>(no need to explicitly assign in markup)</small>
             </p>
           </th>
           <th>
@@ -1176,7 +1179,8 @@ <h2 id="docconformance">
             </td>
             <td>
               <p>
-                If not provided an author defined accessible name by other methods: <strong class="nosupport">No `role`</strong>, and <strong>no `aria-*` attributes</strong> except
+                If not provided an author defined accessible name by other methods:
+                <strong class="nosupport">No `role`</strong>, and <strong>no `aria-*` attributes</strong> except
                 `aria-hidden`.
               </p>
               <p>
@@ -2589,7 +2593,8 @@ <h2 id="docconformance">
                 <code>role=<a href="#index-aria-cell">cell</a></code> if a
                 descendant of a `table` element.
               </p>
-              <!--<p><code>role=<a href="#index-aria-cell">gridcell</a></code> if a descendant of a <code>table</code> elementwith <code>role=grid</code></p>-->
+              <!--<p><code>role=<a href="#index-aria-cell">gridcell</a></code> if a descendant
+                of a <code>table</code> elementwith <code>role=grid</code></p>-->
             </td>
             <td>
               <p>
@@ -5281,8 +5286,7 @@ <h2>
         Documents MUST NOT use any `role`
         values with elements in the [[[#docconformance]]] table, other than the
         corresponding role value (if any) as listed for that element in the
-        third column, other than those indicated in the second column, which
-        SHOULD NOT be used.
+        third column, other than those indicated in the second column.
       </p>
     </section>
 

From b0d2725c038a4a4237b1c143f7929f0cbff79255 Mon Sep 17 00:00:00 2001
From: "Patrick H. Lauke" <redux@splintered.co.uk>
Date: Sat, 25 Jul 2020 19:12:47 +0100
Subject: [PATCH 02/11] Re-hardening to still use NOT RECOMMENDED normatively

while this is synonymous with SHOULD NOT, it better conveys the intent. Still keeps the lengthier explanation of why it's not recommended, and that the "danger" of adverse effects is minimal if authors do do it.
---
 index.html | 28 ++++++++++++++++------------
 1 file changed, 16 insertions(+), 12 deletions(-)

diff --git a/index.html b/index.html
index 9afe1e4b..a919f59b 100644
--- a/index.html
+++ b/index.html
@@ -75,9 +75,12 @@ <h2 id="rules-wd">
       <p>
         Web developers MUST NOT use the ARIA `role` and `aria-*` attributes in
         a manner that conflicts with the semantics described in the
-        [[[#docconformance]]] table. Web developers are discouraged from setting
-        the ARIA `role` and `aria-*` attributes to values that match the
-        <a>implicit ARIA semantics</a> defined in the table, as this is unnecessary.
+        [[[#docconformance]]] table. It is NOT RECOMMENDED for web developers
+        to set the ARIA `role` and `aria-*` attributes to values that match the
+        <a>implicit ARIA semantics</a> defined in the table, as this is unnecessary
+        and can potentially lead to unintended consequences when elements are changed
+        or used in a different context that may lead to elements having different
+        implicit semantics.
       </p>
       <aside class="example">
         The following uses a `role=heading` on a `button` element. This is not
@@ -107,19 +110,19 @@ <h2 id="docconformance">
         used. Where a cell in the third column includes the term
         <dfn><strong>Any</strong> `role`</dfn> it indicates that any `role`
         value apart from the <a>implicit ARIA semantics</a> `role` value, MAY
-        be used. If an cell in the third column includes the term 
+        be used. 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>
 
       <p class="note" id="aria-usage-note">
         Setting an ARIA `role` and/or `aria-*` attribute that matches the
-        <span>implicit ARIA semantics</span> is unnecessary, as these properties
-        are already set by the browser. However, explicitly setting these attributes
-        won't have an adverse effect (provided that they are correct and indeed
-        match the implicit semantics) - and this practice may be necessary when
-        supporting older user agents which lack specific implicit semantics, or
-        when working around browser bugs.
+        <span>implicit ARIA semantics</span> is NOT RECOMMENDED. It is unnecessary,
+        as these properties are already set by the browser. However, explicitly
+        setting these attributes won't generally have an adverse effect (provided
+        that they are correct and indeed match the implicit semantics) - and this
+        practice may be necessary when supporting older user agents which lack
+        specific implicit semantics, or when working around browser bugs.
       </p>
 
       <table class="simple">
@@ -132,7 +135,7 @@ <h2 id="docconformance">
           </th>
           <th>
             <p id="implicit">
-              Implicit ARIA semantics <small>(no need to explicitly assign in markup)</small>
+              Implicit ARIA semantics <small>(explicitly assigning these in markup is NOT RECOMMENDED)</small>
             </p>
           </th>
           <th>
@@ -5286,7 +5289,8 @@ <h2>
         Documents MUST NOT use any `role`
         values with elements in the [[[#docconformance]]] table, other than the
         corresponding role value (if any) as listed for that element in the
-        third column, other than those indicated in the second column.
+        third column, other than those indicated in the second column (whose
+        explicit use in markup is NOT RECOMMENDED).
       </p>
     </section>
 

From c135e3e1634e04d29498b95782c5d419a9d2f0ac Mon Sep 17 00:00:00 2001
From: "Patrick H. Lauke" <redux@splintered.co.uk>
Date: Thu, 30 Jul 2020 21:47:39 +0100
Subject: [PATCH 03/11] Change dash to comma

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index a919f59b..54203f50 100644
--- a/index.html
+++ b/index.html
@@ -120,7 +120,7 @@ <h2 id="docconformance">
         <span>implicit ARIA semantics</span> is NOT RECOMMENDED. It is unnecessary,
         as these properties are already set by the browser. However, explicitly
         setting these attributes won't generally have an adverse effect (provided
-        that they are correct and indeed match the implicit semantics) - and this
+        that they are correct and indeed match the implicit semantics), and this
         practice may be necessary when supporting older user agents which lack
         specific implicit semantics, or when working around browser bugs.
       </p>

From a3bbf44d70f179489137d13c4f2bd109562404de Mon Sep 17 00:00:00 2001
From: scottaohara <scottaohara@gmail.com>
Date: Mon, 10 Aug 2020 10:42:29 -0400
Subject: [PATCH 04/11] add examples

---
 index.html | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/index.html b/index.html
index 0a120e4a..2923c2e9 100644
--- a/index.html
+++ b/index.html
@@ -90,6 +90,33 @@ <h2 id="rules-wd">
           &lt;button role="heading"&gt;search&lt;/button&gt;
         </pre>
       </aside>
+
+      <aside class="example">
+        The following uses a `role=group` on a `fieldset` element. This is unnecessary,
+        because the `fieldset` element is implicitly exposed as a `role=group`.
+        <pre class="HTML">
+          &lt;fieldset role="group"&gt;...&lt;/fieldset&gt;
+        </pre>
+      </aside>
+
+      <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 would generally not be recommended.
+        <pre class="HTML">
+          &lt;ul role="list"&gt;...&lt;/ul&gt;
+        </pre>
+      </aside>
+
+      <aside class="example">
+        The following uses a `role=button` on a `summary` element. This is unnecessary and can cause cross-platform issues. Setting `role=button` to the `summary` element can actually prevent correctly exposing this element to assistive technologies.
+        <pre class="HTML">
+          &lt;details>
+            &lt;summary role="button"&gt;more information&lt;/summary&gt;
+            ...
+          &lt;/details>
+        </pre>
+      </aside>
+
     </section>
     <section>
       <h2 id="docconformance">

From 59b977f3848aa58617aeb430fb0870027817d95d Mon Sep 17 00:00:00 2001
From: scottaohara <scottaohara@gmail.com>
Date: Mon, 10 Aug 2020 10:44:52 -0400
Subject: [PATCH 05/11] document formatting updates

---
 index.html | 25 ++++++++++++-------------
 1 file changed, 12 insertions(+), 13 deletions(-)

diff --git a/index.html b/index.html
index 2923c2e9..0d8d782f 100644
--- a/index.html
+++ b/index.html
@@ -48,7 +48,7 @@
         ARIA in HTML is a [[HTML]] specification module. Any HTML features,
         conformance requirements, or terms that this specification module makes
         reference to, but does not explicitly define, are defined in the
-        [[HTML]] specification.
+        [[HTML|HTML specification]].
       </p>
       <p class="advisement">
         This is a draft document and its contents are subject to change without
@@ -126,19 +126,17 @@ <h2 id="docconformance">
         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 HTML
-        Accessibility API Mappings 1.0 [[html-aam-1.0]] specification.
+        "html/dom.html#elements">HTML elements</a> as defined in the [[html-aam-1.0|HTML
+        Accessibility API Mappings 1.0 ]] specification.
       </p>
       <p>
-        Each language feature (element or attribute) in a cell in the first column
-        implies the ARIA semantics (any role, states, and properties) given in
-        the cell in the second column of the same row. The third cell in each
-        row defines which ARIA role values and aria-* attributes which MAY be
-        used. Where a cell in the third column includes the term
-        <dfn><strong>Any</strong> `role`</dfn> it indicates that any `role`
-        value apart from the <a>implicit ARIA semantics</a> `role` value, MAY
-        be used. If a cell in the third column includes the term 
-        <dfn><strong>No `role`</strong></dfn> it indicates that authors MUST NOT
+        Each language feature (element or attribute) in a cell in the first column implies the
+        ARIA semantics (any role, states, and properties) given in the cell in the second column
+        of the same row. The third cell in each row defines which ARIA role values and `aria-*`
+        attributes which MAY be used. Where a cell in the third column includes the term
+        <dfn><strong>Any</strong> `role`</dfn> it indicates that any `role` value apart from the
+        <a>implicit ARIA semantics</a> `role` value, MAY be used. 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>
 
@@ -162,7 +160,8 @@ <h2 id="docconformance">
           </th>
           <th>
             <p id="implicit">
-              Implicit ARIA semantics <small>(explicitly assigning these in markup is NOT RECOMMENDED)</small>
+              Implicit ARIA semantics
+              <small>(explicitly assigning these in markup is NOT RECOMMENDED)</small>
             </p>
           </th>
           <th>

From 6de78370206de3b9a42b6d418991d22cf908af0a Mon Sep 17 00:00:00 2001
From: scottaohara <scottaohara@gmail.com>
Date: Mon, 10 Aug 2020 10:46:33 -0400
Subject: [PATCH 06/11] remove list notes per new example provided

---
 index.html | 15 ---------------
 1 file changed, 15 deletions(-)

diff --git a/index.html b/index.html
index 0d8d782f..f2e00d2e 100644
--- a/index.html
+++ b/index.html
@@ -1833,11 +1833,6 @@ <h2 id="docconformance">
             </td>
             <td>
               <code>role=<a href="#index-aria-list">list</a></code>
-              <p>
-                <strong>Note:</strong> some user agents suppress a list's
-                <a>implicit ARIA semantics</a> if list markers are removed.
-                Authors can use `role=list` to reinstate the role if necessary.
-              </p>
             </td>
             <td>
               <p>
@@ -1956,11 +1951,6 @@ <h2 id="docconformance">
             </td>
             <td>
               <code>role=<a href="#index-aria-list">list</a></code>
-              <p>
-                <strong>Note:</strong> some user agents suppress a list's
-                <a>implicit ARIA semantics</a> if list markers are removed.
-                Authors can use `role=list` to reinstate the role if necessary.
-              </p>
             </td>
             <td>
               <p>
@@ -2720,11 +2710,6 @@ <h2 id="docconformance">
             </td>
             <td>
               <code>role=<a href="#index-aria-list">list</a></code>
-              <p>
-                <strong>Note:</strong> some user agents suppress a list's
-                <a>implicit ARIA semantics</a> if list markers are removed.
-                Authors can use `role=list` to reinstate the role if necessary.
-              </p>
             </td>
             <td>
               <p>

From dcc889423685ef6d6208ddcfba20b3067f2985f7 Mon Sep 17 00:00:00 2001
From: scottaohara <scottaohara@gmail.com>
Date: Mon, 10 Aug 2020 10:52:06 -0400
Subject: [PATCH 07/11] cut down this text per the added examples which call
 this out.

---
 index.html | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/index.html b/index.html
index f2e00d2e..053a6a92 100644
--- a/index.html
+++ b/index.html
@@ -77,10 +77,8 @@ <h2 id="rules-wd">
         a manner that conflicts with the semantics described in the
         [[[#docconformance]]] table. It is NOT RECOMMENDED for web developers
         to set the ARIA `role` and `aria-*` attributes to values that match the
-        <a>implicit ARIA semantics</a> defined in the table, as this is unnecessary
-        and can potentially lead to unintended consequences when elements are changed
-        or used in a different context that may lead to elements having different
-        implicit semantics.
+        <a>implicit ARIA semantics</a> defined in the table. Doing so is unnecessary
+        and can potentially lead to unintended consequences.
       </p>
       <aside class="example">
         The following uses a `role=heading` on a `button` element. This is not

From 0ad16b1b74f7bd7db96005fe1eb804690d166cf7 Mon Sep 17 00:00:00 2001
From: scottaohara <scottaohara@gmail.com>
Date: Mon, 10 Aug 2020 11:28:05 -0400
Subject: [PATCH 08/11] note updates
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

remove the bit about bugs, as that’s unfortunately not always accurate.
also removed the “older” bit, as there may still be some modern user agents which do not properly expose all elements.
---
 index.html | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/index.html b/index.html
index 053a6a92..cbe56712 100644
--- a/index.html
+++ b/index.html
@@ -139,13 +139,8 @@ <h2 id="docconformance">
       </p>
 
       <p class="note" id="aria-usage-note">
-        Setting an ARIA `role` and/or `aria-*` attribute that matches the
-        <span>implicit ARIA semantics</span> is NOT RECOMMENDED. It is unnecessary,
-        as these properties are already set by the browser. However, explicitly
-        setting these attributes won't generally have an adverse effect (provided
-        that they are correct and indeed match the implicit semantics), and this
-        practice may be necessary when supporting older user agents which lack
-        specific implicit semantics, or when working around browser bugs.
+        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 these attributes can be helpful. For instance, if supporting user agents which lack specific implicit semantics.
       </p>
 
       <table class="simple">

From 81b2e453522e0c9139758415fd1bd0b294fdc9f1 Mon Sep 17 00:00:00 2001
From: "Patrick H. Lauke" <redux@splintered.co.uk>
Date: Mon, 10 Aug 2020 21:06:24 +0100
Subject: [PATCH 09/11] Add some fixes/corrections and extra button example

as `<button role="button">` is such a staple of the genre, worth adding an actual example...and clarifying that no there are likely no actual side effects
---
 index.html | 21 ++++++++++++++++-----
 1 file changed, 16 insertions(+), 5 deletions(-)

diff --git a/index.html b/index.html
index cbe56712..e6084b0b 100644
--- a/index.html
+++ b/index.html
@@ -89,9 +89,20 @@ <h2 id="rules-wd">
         </pre>
       </aside>
 
+      <aside class="example">
+        The following uses a `role=button` on a `button` element. This is unnecessary, this
+        is alreadt the implicit role the is exposed for the element. However,
+        in practice this will likely not have any unforeseen side effects other than unnecessarily
+        making the markup more verbose.
+        <pre class="HTML">
+          &lt;button role="button"&gt;...&lt;/button&gt;
+        </pre>
+      </aside>
+      
       <aside class="example">
         The following uses a `role=group` on a `fieldset` element. This is unnecessary,
-        because the `fieldset` element is implicitly exposed as a `role=group`.
+        because the `fieldset` element is implicitly exposed as a `role=group`. Again,
+        in practice this will likely not have any unforeseen side effects.
         <pre class="HTML">
           &lt;fieldset role="group"&gt;...&lt;/fieldset&gt;
         </pre>
@@ -106,7 +117,7 @@ <h2 id="rules-wd">
       </aside>
 
       <aside class="example">
-        The following uses a `role=button` on a `summary` element. This is unnecessary and can cause cross-platform issues. Setting `role=button` to the `summary` element can actually prevent correctly exposing this element to assistive technologies.
+        The following uses a `role=button` on a `summary` element. This is unnecessary and can cause cross-platform issues. Setting `role=button` to the `summary` element can actually this element from being correctly exposed to assistive technologies.
         <pre class="HTML">
           &lt;details>
             &lt;summary role="button"&gt;more information&lt;/summary&gt;
@@ -140,7 +151,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 these attributes can be helpful. For instance, if supporting user agents which lack specific implicit semantics.
+        <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>
 
       <table class="simple">
@@ -1201,7 +1212,7 @@ <h2 id="docconformance">
             </td>
             <td>
               <p>
-                If not provided an author defined accessible name by other methods:
+                If no author-defined accessible name is provided by other methods:
                 <strong class="nosupport">No `role`</strong>, and <strong>no `aria-*` attributes</strong> except
                 `aria-hidden`.
               </p>
@@ -2616,7 +2627,7 @@ <h2 id="docconformance">
                 descendant of a `table` element.
               </p>
               <!--<p><code>role=<a href="#index-aria-cell">gridcell</a></code> if a descendant
-                of a <code>table</code> elementwith <code>role=grid</code></p>-->
+                of a <code>table</code> element with <code>role=grid</code></p>-->
             </td>
             <td>
               <p>

From c90e327f8fcf07f74f8d3fc0dd001f92f3afefd4 Mon Sep 17 00:00:00 2001
From: Scott O'Hara <scottaohara@users.noreply.github.com>
Date: Mon, 10 Aug 2020 16:19:32 -0400
Subject: [PATCH 10/11] sentence update

---
 index.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index e6084b0b..f571d97d 100644
--- a/index.html
+++ b/index.html
@@ -117,7 +117,8 @@ <h2 id="rules-wd">
       </aside>
 
       <aside class="example">
-        The following uses a `role=button` on a `summary` element. This is unnecessary and can cause cross-platform issues. Setting `role=button` to the `summary` element can actually this element from being correctly exposed to assistive technologies.
+        The following uses a `role=button` on a `summary` element. This is unnecessary and can cause cross-platform issues. 
+        Setting `role=button` to the `summary` element can actually prevent this element from being correctly exposed to assistive technologies.
         <pre class="HTML">
           &lt;details>
             &lt;summary role="button"&gt;more information&lt;/summary&gt;

From a78d2c1b4a995bbfa36057e8ecfd0773d505910f Mon Sep 17 00:00:00 2001
From: scottaohara <scottaohara@gmail.com>
Date: Mon, 10 Aug 2020 16:46:05 -0400
Subject: [PATCH 11/11] additional wordsmithing

---
 index.html | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/index.html b/index.html
index f571d97d..6e37efbc 100644
--- a/index.html
+++ b/index.html
@@ -90,15 +90,14 @@ <h2 id="rules-wd">
       </aside>
 
       <aside class="example">
-        The following uses a `role=button` on a `button` element. This is unnecessary, this
-        is alreadt the implicit role the is exposed for the element. However,
-        in practice this will likely not have any unforeseen side effects other than unnecessarily
-        making the markup more verbose.
+        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 more verbose, and incorrectly signaling to other developers that this practice is useful.
         <pre class="HTML">
           &lt;button role="button"&gt;...&lt;/button&gt;
         </pre>
       </aside>
-      
+
       <aside class="example">
         The following uses a `role=group` on a `fieldset` element. This is unnecessary,
         because the `fieldset` element is implicitly exposed as a `role=group`. Again,
@@ -110,15 +109,17 @@ <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 would generally not be recommended.
+        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;
         </pre>
       </aside>
 
       <aside class="example">
-        The following uses a `role=button` on a `summary` element. This is unnecessary and can cause cross-platform issues. 
-        Setting `role=button` to the `summary` element can actually prevent this element from being correctly exposed to assistive technologies.
+        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
+        exposing its state, and forcing the role of `button`, when it might otherwise be exposed
+        with a different role.
         <pre class="HTML">
           &lt;details>
             &lt;summary role="button"&gt;more information&lt;/summary&gt;
@@ -137,7 +138,7 @@ <h2 id="docconformance">
         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 [[html-aam-1.0|HTML
-        Accessibility API Mappings 1.0 ]] specification.
+        Accessibility API Mappings 1.0]] specification.
       </p>
       <p>
         Each language feature (element or attribute) in a cell in the first column implies the