From 4a88a5b119ff103548b68f7fb6410c06864846ec Mon Sep 17 00:00:00 2001 From: James Nurthen Date: Thu, 3 Aug 2023 16:27:20 -0700 Subject: [PATCH] add normative authors MUST NOT statement --- index.html | 1 + 1 file changed, 1 insertion(+) diff --git a/index.html b/index.html index 5b35ad17f..5a89b6534 100644 --- a/index.html +++ b/index.html @@ -10699,6 +10699,7 @@

Definitions of States and Properties (all aria-* attributes)

  • The value of aria-braillelabel does not contain any characters in Unicode Braille Patterns or consists of only characters in Unicode Braille Patterns; the value does not only contain Braille Pattern dots-0.
  • The value of aria-braillelabel is not identical to the element's accessible name.
    • +

    Authors MUST NOT specify aria-braillelabel on an element which has an explicit or implicit WAI-ARIA role where aria-braillelabel is prohibited.

    Note that Assistive Technologies with braille support can convert the accessible name to Braille. In addition, assistive technologies will be able to customize such braille output according to user preferences. Using only the accessible name, e.g., from content or via aria-label is almost always the better user experience and authors are strongly discouraged from using aria-braillelabel to replicate aria-label. Instead, aria-braillelabel is meant to be used only if the accessible name cannot provide an adequate braille representation, i.e., when a specialized braille description is very different from a text description converted to Braille. It is very important to note that when using aria-braillelabel authors are solely responsible for localizing the attribute value so that it aligns with the document language. In addition, authors need to design a way to clearly communicate the use of this attribute to the user. For example, this could be done in the product documentation. This is even more important when the value consists of Unicode Braille Patterns because Assistive Technologies will pass such content directly to the user without applying user specific braille translations; in general, authors are strongly discouraged from using Unicode Braille Patterns in aria-braillelabel.

    Assistive technologies SHOULD use the value of aria-braillelabel when presenting the accessible name of an element in Braille, but SHOULD NOT change other functionality. For example, an assistive technology that provides aural rendering SHOULD use the accessible name.