Tests 596-599 all expect the browser to return an accessible name on a generic div, even though name is prohibited in these cases. I think it's important to know that the name is prohibited on certain roles for reasons that affect end users. Some screen readers can't cope with the important text of a structural element being on the accessible name instead of in the contents.
This testable statement / expectation currently prevents Chrome from trying to repair the content, e.g. by moving the name to the description of the element.
Example of test:
https://www.w3.org/wiki/AccName_1.1_Testable_Statements#Name_test_case_597
@accdc @scottaohara WDYT?
Tests 596-599 all expect the browser to return an accessible name on a generic div, even though name is prohibited in these cases. I think it's important to know that the name is prohibited on certain roles for reasons that affect end users. Some screen readers can't cope with the important text of a structural element being on the accessible name instead of in the contents.
This testable statement / expectation currently prevents Chrome from trying to repair the content, e.g. by moving the name to the description of the element.
Example of test:
https://www.w3.org/wiki/AccName_1.1_Testable_Statements#Name_test_case_597
@accdc @scottaohara WDYT?