[accname] “skip self” requirement is missing from the “Embedded Control” substep for accessible-name computation

[sideshowbarker]

https://wpt.fyi/results/accname/name/comp_host_language_label.html has “encapsulation” tests, from which can be induced a requirement that when computing the accessible name for a <label>-ed form control (“embedded control”), then any content (text content or attribute values) from the control itself that would otherwise be included in the accessible-name computation for it ancestor <label> must instead be skipped and not included.

But that requirement is not explicitly stated anywhere in the accname spec.

Link to the version of the specification or documentation you were looking at at.

https://w3c.github.io/accname/#comp_embedded_control

Does the issue exists in the editors draft (the editors draft is the most recent draft of the specification)? Yes

[scottaohara]

noting this should probably be referenced in the html aam naming steps for inputs, as well

[accdc]

Hi, can you please provide a code example here to demonstrate the issue?

As far as duplicate node references go, this was meant to be addressed within the following spec text.

"LabelledBy: Otherwise, if the current node has an aria-labelledby attribute that contains at least one valid IDREF, and the current node is not already part of an ongoing aria-labelledby or aria-describedby traversal, process its IDREFs in the order they occur:"

Specifically:

"and the current node is not already part of an ongoing aria-labelledby or aria-describedby traversal"

In theory this means that the same node shouldn't be processed more than once, but browsers always have done so anyway.