diff --git a/html-aam/index.html b/html-aam/index.html index 3941b0df8..6227fb561 100644 --- a/html-aam/index.html +++ b/html-aam/index.html @@ -16051,64 +16051,102 @@

Accessible Name and Description Computation

Accessible Name Computations By HTML Element

- `input type="text"`, `input type="password"`, `input type="number"`, `input type="search"`,` input type="tel"`, `input type="email"`, `input type="url"` and `textarea` Element Accessible + `input type="text"`, `input type="password"`, `input type="number"`, `input type="search"`,` input type="tel"`, `input type="email"`, `input type="url"` and `textarea` Elements Accessible Name Computation

  1. - If the control has an `aria-label` or an `aria-labelledby` attribute the + If the control has an `aria-label` + or an `aria-labelledby` attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
  2. - Otherwise use the associated `label` element or elements accessible name(s) - if more than one `label` is associated; concatenate by - DOM order, delimited by spaces. + If the accessible name is still empty: + use the text equivalent computation of the associated `label` element's subtree + - if more than one `label` is associated; concatenate their subtrees by DOM order, delimited by spaces. +

    + If the control is encapsulated by its `label` element, exclude the control's author specified or + user-entered value from its computed accessible name. +

    +
  3. +
  4. + If the accessible name is still empty: + use the value of the control's `title` attribute. +
  5. +
  6. + Otherwise: + use the value of the control's placeholder attribute.
  7. -
  8. If the accessible name is still empty, then: use the control's `title` attribute.
  9. -
  10. Otherwise use the control's placeholder value.
  11. If none of the above yield a usable text string there is no accessible name.
-

`input type="button"`, `input type="submit"` and `input type="reset"` Accessible Name Computation

+

`input type="button"`, `input type="submit"` and `input type="reset"` Elements Accessible Name Computation

  1. - If the control has an `aria-label` or an `aria-labelledby` attribute the + If the control has an `aria-label` + or an `aria-labelledby` attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
  2. - Otherwise use the associated `label` element(s) accessible name(s) - if more than one `label` is associated; concatenate by DOM order, - delimited by spaces. + If the accessible name is still empty: + use the text equivalent computation of the associated `label` element's subtree + - if more than one `label` is associated; concatenate their subtrees by DOM order, delimited by spaces. +

    + If the control is encapsulated by its `label` element, and the control has an author specified `value` or the lack of a `value` + has produced an implementation defined string to render, + then exclude either from the control's computed accessible name. +

    +
  3. +
  4. + If the accessible name is still empty: + use the value of the control's `value` attribute.
  5. +
  6. + For `input type=submit` and `type=reset`: + if the accessible name is still empty, and the `value` attribute is unspecified use the + implementation defined string respective to the input type. + For instance, a localized string of the word "submit" or "reset" respective to the type of `input`.
  7. -
  8. Otherwise use the `value` attribute.
  9. - For `input type=submit` and `type=reset`: if the prior steps do not yield a usable text string, and the `value` attribute is unspecified use the - implementation defined string respective to the input type. + Otherwise: + use the value of the control's `title` attribute.
  10. -
  11. Otherwise, if the control still has no accessible name use `title` attribute.
  12. If none of the above yield a usable text string there is no accessible name.
-

`input type="image"` Accessible Name Computation

+

`input type="image"` Element Accessible Name Computation

  1. - If the control has an `aria-label` or an `aria-labelledby` attribute the + If the control has an `aria-label` + or an `aria-labelledby` attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
  2. - Otherwise use the associated `label` element(s) accessible name(s) - if more than one `label` is associated; concatenate by DOM order, - delimited by spaces. + If the accessible name is still empty: + use the text equivalent computation of the associated `label` element's subtree + - if more than one `label` is associated; concatenate their subtrees by DOM order, delimited by spaces. +

    + If the control is encapsulated by its `label` element, and the control has an `alt` attribute, + then exclude the attribute's value from the control's computed accessible name. +

    +
  3. +
  4. + If the accessible name is still empty: + use the value of the control's `alt` attribute if present and its value is not the empty string.
  5. -
  6. Otherwise use `alt` attribute if present and its value is not the empty string.
  7. - - -
  8. Otherwise use `title` attribute if present and its value is not the empty string.
  9. +
  10. - Otherwise if the previous steps do not yield a usable text string, use the - implementation defined string respective to the input type (an `input` in the `image` state represents a + If the accessible name is still empty: + use the value of the control's `title` attribute if present and its value is not the empty string. +
  11. +
  12. + Otherwise, if the previous steps do not yield a usable text string: + use the implementation defined string respective to the input type (an `input` in the `image` state represents a submit button). For instance, a localized string of the word "submit" or the words "Submit Query".
  13. If none of the above yield a usable text string there is no accessible name.
  14. @@ -16118,16 +16156,28 @@

    `input type="image"` Accessible Name Computation

    `button` Element Accessible Name Computation

    1. - If the `button` element has an `aria-label` or an `aria-labelledby` attribute the + If the `button` element has an `aria-label` + or an `aria-labelledby` attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
    2. - Otherwise use the associated `label` element(s) accessible name(s) - if more than one `label` is associated; concatenate by DOM order, - delimited by spaces. + If the accessible name is still empty: + use the text equivalent computation of the associated `label` element's subtree + - if more than one `label` is associated; concatenate their subtrees by DOM order, delimited by spaces. +

      + If the `button` element is encapsulated by its `label` element, ignore the `button` element's subtree from its computed + accessible name. +

      +
    3. +
    4. + If the accessible name is still empty: + use the text equivalent computation of the element's subtree. +
    5. +
    6. + Otherwise: + use the value of the element's `title` attribute.
    7. -
    8. Otherwise use the `button` element subtree.
    9. -
    10. Otherwise use `title` attribute.
    11. If none of the above yield a usable text string there is no accessible name.