James Craig

Thanks @fantasai... that and the cross-referenced section, [CSS Text: 4.3.1. Phase I: Collapsing and Transformation](https://www.w3.org/TR/css-text-4/#white-space-phase-1), seem like the most promising path forward.

FYI [WPT PR #42093](https://github.com/web-platform-tests/wpt/pull/42093) is about to be merged according to what's in the HTML-AAM spec. If this issue changes those expectations, please file a new issue on https://github.com/web-platform-tests/interop-2023-accessibility-testing/issues

> Your example is not correct, because span must not be labeled with aria-labelledby okay, I'll update that to use some non-generic, but the first heading can be labelled by...

Will add the examples in https://w3c.github.io/accname/#mapping_additional_nd_te

Thanks for the explanation... It seems like there are several ambiguities in the AccName spec. Among other things, reviewers should have stopped me from naming the step "LabelledBy Recursion" since...

The spec ambiguities as I see it so far... 1. The OP ambiguity, which can be clarified in prose to more explicitly state it'd not recursive or allowed to follow...

My understanding of the intention (now problems) was [the same as @JAWS-test listed above](https://github.com/w3c/accname/issues/209#issuecomment-1773656661)... That said, I'm not eager to increase the complexity of the implementations to allow ~infinite depth...

Another FYI @fantasai

+1 to an AccName update for first heading inside of elements with certain roles. Probably not `group` but `article` and `dialog` are obvious wins. The reason for the flexibility though...

If there's a clean choice for label or heading, great. AccName should be updated to account for any logical pattern authors use. But the reality of the Web is messy,...