Distinction between none and generic (#1959)

ariellalgilmore · web-flow · commit 051ed84f7861 · 2023-06-20T08:56:17.000+02:00
diff --git a/index.html b/index.html
@@ -6003,7 +6003,7 @@ <h5>Presentational Role Inheritance</h5>
 				<p>When an explicit or inherited role of <rref>none</rref>/<rref>presentation</rref> is applied to an element with the implicit semantic of a <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role that has <a href="#mustContain">Allowed Accessibility Child Roles</a>, in addition to the element with the explicit role of <rref>none</rref>/<rref>presentation</rref>, the user agent MUST apply an inherited role of <rref>none</rref> to any owned elements that do not have an explicit role defined. Also, when an explicit or inherited role of <rref>none</rref>/<rref>presentation</rref> is applied to a host language element which has specifically allowed children as defined by the host language specification, in addition to the element with the explicit role of <rref>none</rref>/<rref>presentation</rref>, the user agent MUST apply an inherited role of <rref>none</rref> to any specifically allowed children that do not have an explicit role defined.</p>
 				<p>For any element with an explicit or inherited role of <rref>none</rref>/<rref>presentation</rref> and which is not focusable, user agents MUST ignore role-specific <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> states and properties for that element. For example, in HTML, a <code>ul</code> or <code>ol</code> element with a role of <rref>none</rref>/<rref>presentation</rref> will have the implicit native semantics of its <code>li</code> elements removed because the <rref>list</rref> role to which the <code>ul</code> or <code>ol</code> corresponds has an <a href="#mustContain">Allowed Accessibility Child Role</a> of <rref>listitem</rref>. Likewise, the implicit native semantics of an HTML <code>table</code> element's <code>thead</code>/<code>tbody</code>/<code>tfoot</code>/<code>tr</code>/<code>th</code>/<code>td</code> descendants will also be removed, because the HTML specification indicates that these are required structural descendants of the <code>table</code> element.</p>
 				<p class="note">Only the implicit native semantics of elements that correspond to <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a href="#mustContain">Allowed Accessibility Child Roles</a> are removed. All other content remains intact, including nested tables or lists, unless those elements also have an explicit role of <rref>none</rref>/<rref>presentation</rref> specified.</p>
-				<p>For example, according to an accessibility <abbr title="Application Programing Interface">API</abbr>, the following markup elements would appear to have identical role semantics (no roles) and identical content.</p>
+				<p>For example, according to an accessibility <abbr title="Application Programing Interface">API</abbr>, the following markup elements might have identical or very similar role semantics (generic or none role) and identical content.</p>
 				<pre class="example highlight"><span class="comment">&lt;!-- 1. [role="none"] negates the implicit 'list' and 'listitem' role semantics but does not affect the contents. --&gt;</span>
 &lt;ul role="none"&gt;
   &lt;li&gt; Sample Content &lt;/li&gt;
