Update F103 to remove progressbar as it's not an implicit live region (…

…#1021) Fixes #892 Co-authored-by: JAWS-test2 <> Co-authored-by: Kenneth G. Franqueiro <[email protected]> Co-authored-by: Patrick H. Lauke <[email protected]> Co-authored-by: Mike Gower <[email protected]>
w3c · Dec 13, 2024 · 3e93786 · 3e93786
1 parent b9cd498
commit 3e93786
Showing 1 changed file with 3 additions and 4 deletions.
diff --git a/techniques/failures/F103.html b/techniques/failures/F103.html
@@ -35,10 +35,9 @@ <h2>Description</h2>
 						<li>the HTML <code class="language-html">output</code> element</li>
 						<li><code class="language-html">role="status"</code></li>
 						<li><code class="language-html">role="alert"</code></li>
-						<li>the use of an <code class="language-html">aria-live</code> attribute on an element, set to either "<code class="language-html">polite</code>" or "<code class="language-html">assertive</code>"</li>
 						<li><code class="language-html">role="log"</code></li>
-						<li><code class="language-html">role="progressbar"</code></li>
-						</ul>
+						<li>the use of an <code class="language-html">aria-live</code> attribute on an element, set to either "<code class="language-html">polite</code>" or "<code class="language-html">assertive</code>"</li>
+					</ul>
 				The absence of all of these techniques predicts a failure for the status message be announced to the user. Additionally, if the role or property is not set <em>before</em> the dynamic content is added, this also predicts a failure.</p>
 				<p>Since additional techniques may exist to alert an assistive technology, the final step of this failure technique is confirming whether an assistive technology (such as a screen reader) detects the dynamic content and exposes the information to users. Where a status message exists but is not surfaced by assistive technology, it is confirmation that a failure has taken place.</p>
 
@@ -73,7 +72,7 @@ <h3>Procedure</h3>
 							<li>the existence of errors</li>
 						</ul>
 					</li>
-					<li>Check that the element containing the new content does not have a pre-existing aria role of <code>status</code>, <code>alert</code>, <code>log</code>, or <code>progressbar</code>, or an <code>aria-live</code> attribute</li>
+					<li>Check that the element containing the new content does not have a pre-existing aria role of <code>status</code>, <code>alert</code>, or <code>log</code>, or an <code>aria-live</code> attribute</li>
 					<li>Check that the status message is not surfaced (i.e., announced) by assistive technology</li>
 				</ol>
 			</section>