From 25fa6ebf24786c05435f55992332ae8e246d1a1f Mon Sep 17 00:00:00 2001 From: ariellalgilmore Date: Mon, 19 Jun 2023 10:14:02 -0700 Subject: [PATCH 1/2] Distinction between none and generic --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 83253a707..209f117ac 100644 --- a/index.html +++ b/index.html @@ -6003,7 +6003,7 @@
Presentational Role Inheritance

When an explicit or inherited role of none/presentation is applied to an element with the implicit semantic of a WAI-ARIA role that has Allowed Accessibility Child Roles, in addition to the element with the explicit role of none/presentation, the user agent MUST apply an inherited role of none to any owned elements that do not have an explicit role defined. Also, when an explicit or inherited role of none/presentation 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 none/presentation, the user agent MUST apply an inherited role of none to any specifically allowed children that do not have an explicit role defined.

For any element with an explicit or inherited role of none/presentation and which is not focusable, user agents MUST ignore role-specific WAI-ARIA states and properties for that element. For example, in HTML, a ul or ol element with a role of none/presentation will have the implicit native semantics of its li elements removed because the list role to which the ul or ol corresponds has an Allowed Accessibility Child Role of listitem. Likewise, the implicit native semantics of an HTML table element's thead/tbody/tfoot/tr/th/td descendants will also be removed, because the HTML specification indicates that these are required structural descendants of the table element.

Only the implicit native semantics of elements that correspond to WAI-ARIA Allowed Accessibility Child Roles are removed. All other content remains intact, including nested tables or lists, unless those elements also have an explicit role of none/presentation specified.

-

For example, according to an accessibility API, the following markup elements would appear to have identical role semantics (no roles) and identical content.

+

For example, according to an accessibility API, the following markup elements may have identical or very similar role semantics (generic or none role) and identical content.

<!-- 1. [role="none"] negates the implicit 'list' and 'listitem' role semantics but does not affect the contents. -->
 <ul role="none">
   <li> Sample Content </li>

From bddd58a96db64b5c4281ded2a8933ad59ff2d84d Mon Sep 17 00:00:00 2001
From: ariellalgilmore 
Date: Mon, 19 Jun 2023 10:26:21 -0700
Subject: [PATCH 2/2] change to might to avoid using errant RFC-2119

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

diff --git a/index.html b/index.html
index 209f117ac..11a03ea1c 100644
--- a/index.html
+++ b/index.html
@@ -6003,7 +6003,7 @@ 
Presentational Role Inheritance

 				
When an explicit or inherited role of none/presentation is applied to an element with the implicit semantic of a WAI-ARIA role that has Allowed Accessibility Child Roles, in addition to the element with the explicit role of none/presentation, the user agent MUST apply an inherited role of none to any owned elements that do not have an explicit role defined. Also, when an explicit or inherited role of none/presentation 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 none/presentation, the user agent MUST apply an inherited role of none to any specifically allowed children that do not have an explicit role defined.

 				
For any element with an explicit or inherited role of none/presentation and which is not focusable, user agents MUST ignore role-specific WAI-ARIA states and properties for that element. For example, in HTML, a ul or ol element with a role of none/presentation will have the implicit native semantics of its li elements removed because the list role to which the ul or ol corresponds has an Allowed Accessibility Child Role of listitem. Likewise, the implicit native semantics of an HTML table element's thead/tbody/tfoot/tr/th/td descendants will also be removed, because the HTML specification indicates that these are required structural descendants of the table element.

 				
Only the implicit native semantics of elements that correspond to WAI-ARIA Allowed Accessibility Child Roles are removed. All other content remains intact, including nested tables or lists, unless those elements also have an explicit role of none/presentation specified.

-				
For example, according to an accessibility API, the following markup elements may have identical or very similar role semantics (generic or none role) and identical content.

+				
For example, according to an accessibility API, the following markup elements might have identical or very similar role semantics (generic or none role) and identical content.

 				
<!-- 1. [role="none"] negates the implicit 'list' and 'listitem' role semantics but does not affect the contents. -->
 <ul role="none">
   <li> Sample Content </li>