Review roles with name from author and clarify expectations

[scottaohara]

There are two separate but related issues pertaining to roles which allow name from author.

1. Some roles which presently allow name from author, e.g., heading and listitem, potentially others, demonstrate inconsistent behavior when being named via aria-label or aria-labelledby and whether or not they even expose their name from these attributes - or if they do, then they may not expose their subtree content - which leads into the next issue
2. whether it be a non-interactive element, but especially with interactive elements, if named by author any elements with meaningful roles can be ignored due to the parent element's name from author.

For instance,

<span role=heading aria-level=2 aria-label=whatever>
  whatever text <button aria-expanded=...>...</button>
</span>

see nvaccess/nvda#13296

or

<a href=# aria-label=concise>
  <h2>intro</h2>
  <p>yada yada yada</p>
</a>

In the first example, NVDA has issues exposing the subtree content of the heading in scan mode.
In the second, JAWS ignores all the child content of the link. In discussions about this with both teams, this seems to be more author error as if these elements are named, why should the AT still have to look into these elements to get their subtrees?

It seems that in some cases - headings, list items, author naming should be treated more like paragraphs. These items are meant to represent their content, they aren't generally expected to be treated as container elements, like group/article, that can have their own names separate from their content.

In the case of something like a link, it is a bit trickier. Should author naming suppress the subtree and any semantics elements within have? Or does this need to be more clearly called out in the spec that the subtree content a11y properties should still be exposed?

[JAWS-test]

Related: w3c/accname#59, w3c/html-aam#160, #683

[spectranaut]

Discussed in: https://www.w3.org/2024/05/09-aria-minutes.html#t06
While discussing: #2160

Decision was to wait on this change until there is a clear path forward for interactive list items.

[scottaohara]

the decision was specifically to wait on changing name from author for listitems - the larger topic of other roles where name from author doesn't really make sense, was only alluded to.