feat(aria-label): new rule to flag incorrect use of aria-label, aria-labelledby, and aria-describeby

[straker]

Closes issue: #1575

[WilcoFiers]

I'd like to see some test data on this. What is the problem we are solving with this rule?

[WilcoFiers]

We're going to need to run this rule by the JC. Can you do some testing for this to show what the problem is that comes from this? I suspect we're going to get complaints about this one.

[straker]

I think this PR is not needed and we should instead use the Prohibited States and Props from ARIA 1.2 as they cover this exact use case but in a more generic way.

Related discussions:

• Clarify use of aria-label on elements with no role w3c/aria#756
• Prohibit label on certain roles w3c/aria#985

[straker]

Note, this may not work with the <i> attribute as it doesn't have a role mapping. I will do some testing aria-label on different elements to see how screen readers handle it.

[straker]

From Scott O'Hara on asking about HTML elements with no role mapping:

no mapping = generic
generic doesn't allow naming

[straker]

Tested the following DOM in different browsers:

<div aria-label="my label">foo</div>
<span aria-label="my label">foo</span>
<i aria-label="my label">foo</i>
<p aria-label="my label">foo</p>

<div id="label">my label</div>
<div aria-labelledby="label">foo</div>
<span aria-labelledby="label">foo</span>
<i aria-labelledby="label">foo</i>
<p aria-labelledby="label">foo</p>

No browser / screen reader combination read the aria-label or the aria-labelledby attributes. All names returned as "foo"