From a9cfa2e946b0b4516fd8b32ba54d763f391f55df Mon Sep 17 00:00:00 2001 From: Nolan Lawson Date: Fri, 26 May 2023 15:57:08 -0700 Subject: [PATCH] fix: revert whitespace changes --- index.html | 300 ++++++++++++++++++++++++++--------------------------- 1 file changed, 150 insertions(+), 150 deletions(-) diff --git a/index.html b/index.html index 0c43e6b..ad80993 100644 --- a/index.html +++ b/index.html @@ -1,48 +1,48 @@ - Accessible Name and Description Computation 1.2 - - - - - - - + + + + + preProcess: [ linkCrossReferences ], + postProcess: [ addPlatformMaintainers ], + //Pointing to the 1.2 versions but should remove the version in the publishing branch + xref: ["dom", "core-aam-1.2", "wai-aria-1.2", "infra"] + } +
@@ -161,23 +161,23 @@

Introduction

The terms "accessible name" and "accessible description" are used to emphasize that they are properties of accessible objects as exposed by Accessibility APIs. However, they are frequently referred to hereafter as simply "name" and "description".

-

Important Terms

-
-

While some terms are defined in place, the following definitions are used throughout this document.

-
+

Important Terms

+
+

While some terms are defined in place, the following definitions are used throughout this document.

+
Accessible Description
-
-

An accessible description provides additional information, related to an interface element, that complements the accessible name. The accessible description might or might not be visually perceivable.

-
-
Accessible Name
-
-

The accessible name is the name of a user interface element. Each platform accessibility API provides the accessible name property. The value of the accessible name may be derived from a visible (e.g., the visible text on a button) or invisible (e.g., the text alternative that describes an icon) property of the user interface element. See related accessible description.

-

A simple use for the accessible name property may be illustrated by an "OK" button. The text "OK" is the accessible name. When the button receives focus, assistive technologies may concatenate the platform's role description with the accessible name. For example, a screen reader may speak "push-button OK" or "OK button". The order of concatenation and specifics of the role description (e.g., "button", "push-button", "clickable button") are determined by platform accessibility APIs or assistive technologies.

-
+
+

An accessible description provides additional information, related to an interface element, that complements the accessible name. The accessible description might or might not be visually perceivable.

+
+
Accessible Name
+
+

The accessible name is the name of a user interface element. Each platform accessibility API provides the accessible name property. The value of the accessible name may be derived from a visible (e.g., the visible text on a button) or invisible (e.g., the text alternative that describes an icon) property of the user interface element. See related accessible description.

+

A simple use for the accessible name property may be illustrated by an "OK" button. The text "OK" is the accessible name. When the button receives focus, assistive technologies may concatenate the platform's role description with the accessible name. For example, a screen reader may speak "push-button OK" or "OK button". The order of concatenation and specifics of the role description (e.g., "button", "push-button", "clickable button") are determined by platform accessibility APIs or assistive technologies.

+
Tooltip attribute
-
-

Any host language attribute that would result in a user agent generating a tooltip such as in response to a mouse hover in desktop user agents.

-
+
+

Any host language attribute that would result in a user agent generating a tooltip such as in response to a mouse hover in desktop user agents.

+
@@ -215,49 +215,49 @@

Description Computation

The following table provides the order of precedence for markup that can be applied to compute an accessible description. User agents MUST use the first applicable entry from the table where the listed conditions are met, as described in the last column. The user agent MUST NOT use any markup other that the first relevant markup found, even if that markup results in an empty description:

- - - - - - + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + +
PrecedenceAttributeApplicable conditionsHow used to compute description
PrecedenceAttributeApplicable conditionsHow used to compute description
1aria-describedby attributeUse on any elementText content computation on all nodes referenced by aria-describedby on the element, concatenated, and separated by a space character
2aria-description attributeUse on any elementAs a flat string
3host language features which participate in the description calculation - Unique host language features MAY participate in the description computation for an element, only if they were not already used - for the accessible name of the applicable element. See HTML AAM: Accessible Description Computation - for the HTML elements which meet this condition. - - Either a text equivalent computation of the element, or as a flat string of the attribute's value. -
4host language tooltip attribute or equivalent feature (e.g., HTML title attribute) -
    -
  • Any element
    • -
  • Only use if not already used for the accessible name of this node
    • -
- 		As a flat string
1aria-describedby attributeUse on any elementText content computation on all nodes referenced by aria-describedby on the element, concatenated, and separated by a space character
2aria-description attributeUse on any elementAs a flat string
3host language features which participate in the description calculation + Unique host language features MAY participate in the description computation for an element, only if they were not already used + for the accessible name of the applicable element. See HTML AAM: Accessible Description Computation + for the HTML elements which meet this condition. + + Either a text equivalent computation of the element, or as a flat string of the attribute's value. +
4host language tooltip attribute or equivalent feature (e.g., HTML title attribute) +
    +
  • Any element
    • +
  • Only use if not already used for the accessible name of this node
    • +
+ 		As a flat string
@@ -320,11 +320,11 @@

Computation steps

  • Computation: Compute the text alternative for the current node:
    1. Hidden Not Referenced: If the current node is [=element/hidden=] and is: -
        -
      1. Not part of an aria-labelledby or aria-describedby traversal, where the node directly referenced by that relation was hidden.
        2. -
      2. Nor part of a native host language text alternative element (e.g. label in HTML) or attribute traversal, where the root of that traversal was hidden.
        3. -
      - Return the empty string. +
        +
      1. Not part of an aria-labelledby or aria-describedby traversal, where the node directly referenced by that relation was hidden.
        2. +
      2. Nor part of a native host language text alternative element (e.g. label in HTML) or attribute traversal, where the root of that traversal was hidden.
        3. +
      + Return the empty string.
      Comment:

      It's important to clarify the broad definition of hidden for the purposes of accessible name calculation:

      @@ -371,18 +371,18 @@

      Computation steps

      Comment:

      The result of LabelledBy Recursion in combination with Hidden Not Referenced means that user agents MUST include all nodes in the subtree as part of the accessible name or accessible description, when the node referenced by aria-labelledby or aria-describedby is hidden.

      -
      - Example: -

      The following example shows the meaning of the clause "… and the current node is not already part of an aria-labelledby traversal …" .

      -
        -
      1. element1's accessible name is "hello" because this is a first traversal of its aria-labelledby, leading to element3.
        2. -
      2. element2 has no accessible name. The computation involves a first traversal of its aria-labelledby leading to element1, but element1's aria-labelledby is not subsequently followed.
        3. -
      - 
      <element1 id="el1" aria-labelledby="el3" />
+              
      
+                Example:
+                
      The following example shows the meaning of the clause "… and the current node is not already part of an aria-labelledby traversal …" .
      
+                
        
+                  
      1. element1's accessible name is "hello" because this is a first traversal of its aria-labelledby, leading to element3.
        2. 
+                  
      2. element2 has no accessible name.  The computation involves a first traversal of its aria-labelledby leading to element1, but element1's  aria-labelledby is not subsequently followed. 
        3. 
+                
      
+                
      <element1 id="el1" aria-labelledby="el3" />
 <element2 id="el2" aria-labelledby="el1" />
 <element3 id="el3"> hello </element3>
                 
      
-                
      
+
    2. Embedded Control: Otherwise, if the current node is a control embedded within the label (e.g. any element directly referenced by aria-labelledby) for another widget, where the user can adjust the embedded control's value, then return the embedded control as part of the text alternative in the following manner:
        @@ -409,8 +409,8 @@

        Computation steps

      Example: -

      The following example shows the interaction of aria-labelledby and aria-label when a [=nodes|node=] has an aria-labelledby that refers to itself. The <span role="button"> elements have the accessible names "Delete Documentation.pdf" and "Delete HolidayLetter.pdf", respectively.

      - 
      <h1>Files</h1>
+                  
      The following example shows the interaction of aria-labelledby and aria-label when a [=nodes|node=] has an  aria-labelledby that refers to itself.  The <span role="button"> elements have the accessible names "Delete Documentation.pdf" and "Delete HolidayLetter.pdf", respectively.
      
+                  
      <h1>Files</h1>
 <ul>
   <li>
     <a id="file_row1" href="./files/Documentation.pdf">Documentation.pdf</a>