Skip to content

Commit 4f387e3

Browse files
1 parent 1ef760f commit 4f387e3

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

index.html

+18-17
Original file line numberDiff line numberDiff line change
@@ -6359,23 +6359,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
63596359
&lt;/li&gt;
63606360
63616361
&lt;/ul&gt;</pre>
6362-
<section id="conflict_resolution_presentation_none">
6363-
<h5>Presentational Roles Conflict Resolution</h5>
6364-
<p>There are a number of ways presentational role conflicts are resolved.</p>
6365-
<p>User agents MUST NOT expose <a>elements</a> having explicit or inherited presentational role in the accessibility tree, with these exceptions:</p>
6366-
<ul>
6367-
<li>If an element is focusable, or otherwise interactive, user agents MUST ignore the <code>presentation</code> role and expose the element with its implicit role, in order to ensure that the element is <a>operable</a>.</li>
6368-
<li>If a <a href="#mustContain">required owned element</a> has an explicit non-presentational role, user agents MUST ignore an inherited presentational role and expose the element with its explicit role. If the action of exposing the explicit role causes the accessibility tree to be malformed, the expected results are undefined.</li>
6369-
<li>If an element has global WAI-ARIA states or properties, user agents MUST ignore the <code>presentation</code> role and expose the element with its implicit role. However, if an element has only non-global, role-specific WAI-ARIA states or properties, the element MUST NOT be exposed unless the presentational role is inherited and an explicit non-presentational role is applied.</li>
6370-
</ul>
6371-
<p>For example, <pref>aria-describedby</pref> is a global attribute and would always be applied; <pref>aria-level</pref> is not a global attribute and would therefore only apply if the element was not in a presentational state.</p>
6372-
<pre class="example highlight">
6373-
<span class="comment">&lt;!-- 1. [role="presentation"] is ignored due to the global aria-describedby property. --&gt;</span>
6374-
&lt;h1 role="presentation" aria-describedby="comment-1"&gt; Sample Content &lt;/h1&gt;
6375-
<span class="comment">&lt;!-- 2. [role="presentation"] negates both the implicit 'heading' and the non-global aria-level. --&gt;</span>
6376-
&lt;h1 role="presentation" aria-level="2"&gt; Sample Content &lt;/h1&gt;
6377-
</pre>
6378-
</section>
6362+
<p class="ednote">Information about <a href="#conflict_resolution_presentation_none">resolving conflicts in the presentation role</a> has been moved to <a href="#document-handling_author-errors">Handling Author Errors</a></p>
63796363
</div>
63806364
<table class="role-features">
63816365
<caption>Characteristics:</caption>
@@ -13583,6 +13567,23 @@ <h3>States and Properties</h3>
1358313567
</table>
1358413568
<p class="note">Implicit values for non-required states and properties appear in the characteristics table for each role. These are not considered fallback values so are not included here.</p>
1358513569
</section>
13570+
<section id="conflict_resolution_presentation_none">
13571+
<h3>Presentational Roles Conflict Resolution</h3>
13572+
<p>There are a number of ways presentational role conflicts are resolved.</p>
13573+
<p>User agents MUST NOT expose <a>elements</a> having explicit or inherited presentational role in the accessibility tree, with these exceptions:</p>
13574+
<ul>
13575+
<li>If an element is focusable, or otherwise interactive, user agents MUST ignore the <code>presentation</code> role and expose the element with its implicit role, in order to ensure that the element is <a>operable</a>.</li>
13576+
<li>If a <a href="#mustContain">required owned element</a> has an explicit non-presentational role, user agents MUST ignore an inherited presentational role and expose the element with its explicit role. If the action of exposing the explicit role causes the accessibility tree to be malformed, the expected results are undefined.</li>
13577+
<li>If an element has global WAI-ARIA states or properties, user agents MUST ignore the <code>presentation</code> role and expose the element with its implicit role. However, if an element has only non-global, role-specific WAI-ARIA states or properties, the element MUST NOT be exposed unless the presentational role is inherited and an explicit non-presentational role is applied.</li>
13578+
</ul>
13579+
<p>For example, <pref>aria-describedby</pref> is a global attribute and would always be applied; <pref>aria-level</pref> is not a global attribute and would therefore only apply if the element was not in a presentational state.</p>
13580+
<pre class="example highlight">
13581+
<span class="comment">&lt;!-- 1. [role="presentation"] is ignored due to the global aria-describedby property. --&gt;</span>
13582+
&lt;h1 role="presentation" aria-describedby="comment-1"&gt; Sample Content &lt;/h1&gt;
13583+
<span class="comment">&lt;!-- 2. [role="presentation"] negates both the implicit 'heading' and the non-global aria-level. --&gt;</span>
13584+
&lt;h1 role="presentation" aria-level="2"&gt; Sample Content &lt;/h1&gt;
13585+
</pre>
13586+
</section>
1358613587
</section>
1358713588
<section id="idl-interface" class="normative">
1358813589
<h2>IDL Interface</h2>

0 commit comments

Comments
 (0)

Follow Lee on X/Twitter - Father, Husband, Serial builder creating AI, crypto, games & web tools. We are friends :) AI Will Come To Life!

Check out: eBank.nz (Art Generator) | Netwrck.com (AI Tools) | Text-Generator.io (AI API) | BitBank.nz (Crypto AI) | ReadingTime (Kids Reading) | RewordGame | BigMultiplayerChess | WebFiddle | How.nz | Helix AI Assistant