From 17750f74521fb42847668b0b3dfd76a08fecd345 Mon Sep 17 00:00:00 2001 From: James Craig Date: Wed, 8 Oct 2025 17:06:32 -0700 Subject: [PATCH 1/6] Add namefrom:heading again; Will year 6 be the year? --- accname/index.html | 4 +++ index.html | 62 +++++++++++++++++++++++++++++++++++----------- 2 files changed, 52 insertions(+), 14 deletions(-) diff --git a/accname/index.html b/accname/index.html index cb4b8090a..8dd16a197 100644 --- a/accname/index.html +++ b/accname/index.html @@ -646,6 +646,10 @@

Computation steps

+
  • + Name From Heading: Otherwise, if the current node has a role that supports nameFrom: heading, + return the text alternative of the first descendant element node matching the role of heading in an depth-first search. +
  • Name From Content: Otherwise, if the current node's role allows name from content, or if the current node is referenced by aria-labelledby, aria-describedby, or diff --git a/index.html b/index.html index 0d588ae06..bc29e6a9f 100644 --- a/index.html +++ b/index.html @@ -1265,15 +1265,27 @@

    Name From

    having the lowest precedence for specifying a text alternative.
  • - contents: name comes from the text value of the element node. Although this might be allowed in addition to "author" in some roles, this is used in content only if higher - priority "author" features are not provided. Priority is defined by the Accessible Name and Description Computation [[ACCNAME-1.2]]. + heading: name comes from the text alternative of the first descendant element node (depth first search) matching the role of heading as defined in the AccName + computation algorithm for nameFrom: heading. Although "namefrom: heading" is allowed in addition to "namefrom: author" in some roles, "namefrom: heading" is used in content only + if higher priority "namefrom: author" features are not provided. Priority is defined by the Accessible Name and Description Computation + [[ACCNAME-1.2]].
    • +
  • + contents: name comes from the text value of the element node. Although this might be allowed in addition to "namefrom: author" or "namefrom:heading" in some roles, this + is used in content only if higher priority "namefrom: author" or "namefrom: heading" features are not provided. Priority is defined by the Accessible + Name and Description Computation [[ACCNAME-1.2]]. +
    • +
  • Priority is defined by the Accessible Name and Description Computation [[ACCNAME-1.2]].
  • prohibited: the element does not support name from author. Authors MUST NOT use the aria-label or aria-labelledby attributes to name the element.

    • Roles Supporting Name from Author

    +
    +

    Roles Supporting Name from Heading

    +
    +

    Roles Supporting Name from Content

    @@ -1670,7 +1682,12 @@

    Definition of Roles

    Name From: - author + + + Accessible Name Required: @@ -1886,7 +1903,12 @@

    Definition of Roles

    Name From: - author + + + Accessible Name Required: @@ -3631,7 +3653,7 @@

    Definition of Roles

    focus to dialogs. See the WAI-ARIA Authoring Practices: Dialog (modal) pattern for additional details on implementing modal dialog design patterns.

    -

    Authors SHOULD provide an accessible name for a dialog, which can be done with the aria-label or aria-labelledby attribute.

    +

    Authors SHOULD provide an accessible name for a dialog, using either namefrom: author or namefrom: heading.

    Authors SHOULD ensure that all dialogs (both modal and non-modal) have at least one focusable descendant element. Authors SHOULD focus an element in the modal dialog when it is displayed, and authors SHOULD constrain keyboard focus to focusable elements within a modal dialog, until dismissed. @@ -3721,7 +3743,12 @@

    Definition of Roles

    Name From: - author + + + Accessible Name Required: @@ -4254,9 +4281,8 @@

    Definition of Roles

    possible. If the purpose of a form is to submit search criteria, authors SHOULD use the search role instead of the generic form role.

    - Authors SHOULD give each element with role form a brief label that describes the purpose of the form. Authors SHOULD reference a visible label with - aria-labelledby if a visible label is present. Authors SHOULD include the label inside of a heading whenever possible. The heading MAY be an instance of the standard host - language heading element or an instance of an element with role heading. + Authors SHOULD give each element with role form a label that describes the purpose of the form, using either namefrom: author or + namefrom: heading.

    If an author uses a script to submit a form based on a user action that would otherwise not trigger an onsubmit event (for example, a form submission triggered by the user @@ -4320,7 +4346,12 @@

    Definition of Roles

    Name From: - author + + + Accessible Name Required: @@ -7984,9 +8015,7 @@
    Presentational Role Inheritance
    landmark roles, such as main, complementary, or navigation.

    - Authors MUST give each element with role region a brief label that describes the purpose of the content in the region. Authors SHOULD reference a visible label with - aria-labelledby if a visible label is present. Authors SHOULD include the label inside of a heading whenever possible. The heading MAY be an instance of the standard host - language heading element or an instance of an element with role heading. + Authors MUST give each element with role region a label that describes the purpose of the content in the region, using either namefrom: author or namefrom: heading.

    Assistive technologies SHOULD enable users to quickly navigate to elements with role region. [=User agents=] SHOULD treat elements with role region and @@ -8046,7 +8075,12 @@

    Presentational Role Inheritance
    Name From: - author + + + Accessible Name Required: From d0e22a59c80b58bb83db7c41068a3efc859954aa Mon Sep 17 00:00:00 2001 From: James Craig Date: Mon, 13 Oct 2025 15:24:26 -0700 Subject: [PATCH 2/6] backing out the region and form role changes based circumstances outlined in the PR comment thread --- index.html | 23 ++++++++--------------- 1 file changed, 8 insertions(+), 15 deletions(-) diff --git a/index.html b/index.html index bc29e6a9f..1e0a428b0 100644 --- a/index.html +++ b/index.html @@ -4281,8 +4281,9 @@

    Definition of Roles

    possible. If the purpose of a form is to submit search criteria, authors SHOULD use the search role instead of the generic form role.

    - Authors SHOULD give each element with role form a label that describes the purpose of the form, using either namefrom: author or - namefrom: heading. + Authors SHOULD give each element with role form a brief label that describes the purpose of the form. Authors SHOULD reference a visible label with + aria-labelledby if a visible label is present. Authors SHOULD include the label inside of a heading whenever possible. The heading MAY be an instance of the standard host + language heading element or an instance of an element with role heading.

    If an author uses a script to submit a form based on a user action that would otherwise not trigger an onsubmit event (for example, a form submission triggered by the user @@ -4346,12 +4347,7 @@

    Definition of Roles

    Name From: - -
      -
    • author
      • -
    • heading
      • -
    - + author Accessible Name Required: @@ -8015,7 +8011,9 @@
    Presentational Role Inheritance
    landmark roles, such as main, complementary, or navigation.

    - Authors MUST give each element with role region a label that describes the purpose of the content in the region, using either namefrom: author or namefrom: heading. + Authors MUST give each element with role region a brief label that describes the purpose of the content in the region. Authors SHOULD reference a visible label with + aria-labelledby if a visible label is present. Authors SHOULD include the label inside of a heading whenever possible. The heading MAY be an instance of the standard host + language heading element or an instance of an element with role heading.

    Assistive technologies SHOULD enable users to quickly navigate to elements with role region. [=User agents=] SHOULD treat elements with role region and @@ -8075,12 +8073,7 @@

    Presentational Role Inheritance
    Name From: - -
      -
    • author
      • -
    • heading
      • -
    - + author Accessible Name Required: From b19f0b91a32cc2c85401b6369606c547d3325370 Mon Sep 17 00:00:00 2001 From: James Craig Date: Mon, 20 Oct 2025 15:42:46 -0700 Subject: [PATCH 3/6] m. hyphenation Co-authored-by: Rahim Abdi --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 1e0a428b0..84fdd9b04 100644 --- a/index.html +++ b/index.html @@ -1265,7 +1265,7 @@

    Name From

    having the lowest precedence for specifying a text alternative.
  • - heading: name comes from the text alternative of the first descendant element node (depth first search) matching the role of heading as defined in the AccName + heading: name comes from the text alternative of the first descendant element node (depth-first search) matching the role of heading as defined in the AccName computation algorithm for nameFrom: heading. Although "namefrom: heading" is allowed in addition to "namefrom: author" in some roles, "namefrom: heading" is used in content only if higher priority "namefrom: author" features are not provided. Priority is defined by the Accessible Name and Description Computation [[ACCNAME-1.2]]. From 47ef93422b7d5ff9885cc5b142b9983d3651635d Mon Sep 17 00:00:00 2001 From: James Craig Date: Mon, 20 Oct 2025 15:43:35 -0700 Subject: [PATCH 4/6] m. article typo based on the prior change from IDDFS to DFS. Co-authored-by: Rahim Abdi --- accname/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/accname/index.html b/accname/index.html index 8dd16a197..2ec7e6107 100644 --- a/accname/index.html +++ b/accname/index.html @@ -648,7 +648,7 @@

    Computation steps

  • Name From Heading: Otherwise, if the current node has a role that supports nameFrom: heading, - return the text alternative of the first descendant element node matching the role of heading in an depth-first search. + return the text alternative of the first descendant element node matching the role of heading in a depth-first search.
  • Name From Content: Otherwise, if the current node's role allows From 0fcaeec9cff4073256dd42e5376df9571217b221 Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Tue, 21 Oct 2025 09:47:57 -0400 Subject: [PATCH 5/6] html aam updates for name from heading This commit supersedes PR #2215 --- html-aam/index.html | 38 +++++++++++++++++++++++++++++++++++++- 1 file changed, 37 insertions(+), 1 deletion(-) diff --git a/html-aam/index.html b/html-aam/index.html index 5e1fe5c4e..c79f90861 100644 --- a/html-aam/index.html +++ b/html-aam/index.html @@ -16816,7 +16816,43 @@

    `iframe` Element Accessible Name Computation

    • -

    Section and Grouping Element Accessible Name Computation

    +

    `dialog` Element Accessible Name Computation

    +
      +
    1. + If the `dialog` 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. +
    2. + If the accessible name is still empty, then: if the `dialog` element has a + descendant element with a role of `heading`, then use the + text equivalent computation of the element as defined in + accname: Name from Heading. +
      3. +
    3. Otherwise, use the `title` attribute.
      4. +
    4. If none of the above yield a usable text string there is no accessible name.
      5. +
    +
    +
    +

    `article` Element Accessible Name Computation

    +
      +
    1. + If the `article` 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. +
    2. + If the accessible name is still empty, then: if the `dialog` element has a + descendant element with a role of `heading`, then use the + text equivalent computation of the element as defined in + accname: Name from Heading. +
      3. +
    3. Otherwise, use the `title` attribute.
      4. +
    4. If none of the above yield a usable text string there is no accessible name.
      5. +
    +
    +
    +

    Other Section and Grouping Element Accessible Name Computation

    1. If the element has an `aria-label` or an `aria-labelledby` attribute the From 30a7f569a09e3f9f65b2ebda370e942d378106b0 Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Tue, 21 Oct 2025 21:27:43 -0400 Subject: [PATCH 6/6] Apply suggestion from @jcsteh Co-authored-by: James Teh --- html-aam/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/html-aam/index.html b/html-aam/index.html index c79f90861..dd6ac973c 100644 --- a/html-aam/index.html +++ b/html-aam/index.html @@ -16842,7 +16842,7 @@

      `article` Element Accessible Name Computation

      Accessible Name and Description: Computation and API Mappings.
    2. - If the accessible name is still empty, then: if the `dialog` element has a + If the accessible name is still empty, then: if the `article` element has a descendant element with a role of `heading`, then use the text equivalent computation of the element as defined in accname: Name from Heading.