diff --git a/techniques/failures/F103.html b/techniques/failures/F103.html index aabec5461e..4c365aaa64 100644 --- a/techniques/failures/F103.html +++ b/techniques/failures/F103.html @@ -35,10 +35,9 @@

Description

  • the HTML output element
  • role="status"
  • role="alert"
    • -
  • the use of an aria-live attribute on an element, set to either "polite" or "assertive"
  • role="log"
    • -
  • role="progressbar"
    • - +
  • the use of an aria-live attribute on an element, set to either "polite" or "assertive"
    • + 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.

    @@ -73,7 +72,7 @@

    Procedure

  • 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