From 8895933e2bba848c4b969d373ad374f603493b58 Mon Sep 17 00:00:00 2001 From: JAWS-test2 <> Date: Sun, 26 Jan 2020 15:46:58 +0100 Subject: [PATCH] Update F103.html --- techniques/failures/F103.html | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/techniques/failures/F103.html b/techniques/failures/F103.html index 18be3bc43e..8976fd6375 100644 --- a/techniques/failures/F103.html +++ b/techniques/failures/F103.html @@ -34,9 +34,8 @@

Description

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 before the dynamic content is added, this also predicts a failure.

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.

@@ -71,7 +70,7 @@

Procedure

  • the progress of a process
  • the existence of errors
  • -
  • Check that the element containing the new content does not have a pre-existing aria role of status, alert, log, or progressbar, or an aria-live attribute
  • +
  • Check that the element containing the new content does not have a pre-existing aria role of status, alert, or log, or an aria-live attribute
  • Check that the status message is not surfaced (i.e., announced) by assistive technology