Need clarity on computation involving first traversal

[devarshipant]

Example (after 2nd bullet under 2 B) -- http://www.w3.org/TR/accname-aam-1.1/#mapping_additional_nd_te is not clear because only element3 has innertext. The calculation changes when element1 and element2 have innertext (or acc name derived from another aria attribute).

It says: "element2 has no accessible name. The computation involves a first traversal of its aria-labelledby leading to element1, but element1's aria-labelledby is not subsequently followed."

Here is a modified example using buttons:

<button type="button" id="el1" aria-labelledby="el3">test1</button>
<button type="button" id="el2" aria-labelledby="el1">test 2</button>
<button type="button" id="el3"> hello </button>

• Results (based on above example):

1. JAWS 18 and NVDA (IE11): The accessible name of button#2 is test1 (aria-labelledby of button#2 references button#1, returns the acc name 'test1', and stops the traversal).

2. VO and Chrome: The accessible name of button#2 is hello (aria-labelledby of button#2 references button#1, traverses to button#3, and returns the acc name 'hello').

[accdc]

Hi, the spec is clear that aria-labelledby references are not recursive, meaning that only the root node can be followed when this is the case. E.G only the aria-labelledby reference on the button you want the label for is valid, but no other instance of aria-labelledby discovered after that in the computation is applicable. This is needed to prevent infinite loops. So if Chrome is doing this, then this is a bug in Chrome and it needs to be fixed.