I'm working to update the Blink accessibility code to not expose a name on roles where the name is prohibited. There is a good reason for these rules, as screen readers cannot always cope with having text both in a label and in descendant content.
(Note: I want to experiment with moving the prohibited name to a description, and logging an a11y error in developer tools

However, this causes errors in external/wpt/accname/name/comp_label.html, which seem to assume that aria-label will produce an accname on these prohibited roles. Shouldn't the test be using valid ARIA?

---- Output of test ----

This is a testharness.js-based test.
Found 5 FAIL, 0 TIMEOUT, 0 NOTRUN.
[FAIL] label valid on div with associationlist role
assert_equals:

expected "label" but got ""
[FAIL] label valid on div with associationlistitemkey role
assert_equals: expected "label" but got ""
[FAIL] label valid on div with associationlistitemvalue role
assert_equals: expected "label" but got ""
[FAIL] label valid on dd element
assert_equals:

x

expected "label" but got ""
[FAIL] label valid on dt element
assert_equals:

x

expected "label" but got ""
Harness: the test ran to completion.