From e598908842e83eddc5472d4b8a7e153f1e90e4a6 Mon Sep 17 00:00:00 2001
From: "Patrick H. Lauke" <redux@splintered.co.uk>
Date: Thu, 13 Aug 2020 08:03:19 +0100
Subject: [PATCH 1/2] Add PHL as co-editor

---
 index.html | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 6e37efbc..c2b2b534 100644
--- a/index.html
+++ b/index.html
@@ -12,14 +12,20 @@
           url: "https://www.paciellogroup.com",
           company: "The Paciello Group",
           companyURL: "https://www.paciellogroup.com",
-          w3cid: "35007",
+          w3cid: "35007"
         },
         {
           name: "Scott O'Hara",
           url: "https://www.paciellogroup.com",
           company: "The Paciello Group",
           companyURL: "https://www.paciellogroup.com",
-          w3cid: "103856",
+          w3cid: "103856"
+        },
+        { name: "Patrick H. Lauke",
+          url: "https://tetralogical.com",
+          company: "TetraLogical",
+          companyURL: "https://tetralogical.com/",
+          w3cid: '35129'
         },
       ],
       previousMaturity: "WD",

From e19a413ef75a9d7b4844131282ecd5b9baa938f3 Mon Sep 17 00:00:00 2001
From: Scott O'Hara <scottaohara@users.noreply.github.com>
Date: Fri, 14 Aug 2020 07:14:47 -0400
Subject: [PATCH 2/2] Update index.html

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

diff --git a/index.html b/index.html
index 0a6205ea..2d3b6f7b 100644
--- a/index.html
+++ b/index.html
@@ -69,11 +69,11 @@ <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 <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> of
-        a given HTML element. These constraints are intended to prevent
+        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> 
+        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
         of the document.
@@ -98,7 +98,8 @@ <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 more verbose, and incorrectly signaling to other developers that this practice is useful.
+        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>
@@ -115,7 +116,10 @@ <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, otherwise.
+        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>
@@ -142,9 +146,9 @@ <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 [[html-aam-1.0|HTML
-        Accessibility API Mappings 1.0]] specification.
+        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>
         Each language feature (element or attribute) in a cell in the first column implies the
@@ -159,7 +163,8 @@ <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, in 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">