Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update F103 to remove progressbar as it's not an implicit live region #1021

Merged
merged 5 commits into from
Dec 13, 2024
Merged

Update F103 to remove progressbar as it's not an implicit live region #1021

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8895933
Update F103.html
Jan 26, 2020
9f4cb78
Merge branch 'main' into F103
kfranqueiro Oct 25, 2024
1116fbe
Merge branch 'main' into F103
patrickhlauke Nov 8, 2024
f088afe
Merge branch 'main' into F103
patrickhlauke Nov 22, 2024
9cf7f03
Merge branch 'main' into F103
mbgower Dec 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions techniques/failures/F103.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,9 +34,8 @@ <h2>Description</h2>
<ul>
<li><code>role="status"</code></li>
<li><code>role="alert"</code></li>
<li>the use of an <code>aria-live</code> attribute on an element, set to either "polite" or "assertive"</li>
<li><code>role="log"</code></li>
<li><code>role="progressbar"</code></li>
<li>the use of an <code>aria-live</code> attribute on an element, set to either "polite" or "assertive"</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>
Expand Down Expand Up @@ -71,7 +70,7 @@ <h3>Procedure</h3>
<li>the progress of a process</li>
<li>the existence of errors</li>
</ul>
<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>
Expand Down