Add generic audit for accessible names

Provide a basic description of the audit

Audit if roles that require an accessible name have one (e.g. dialog or tree)

How would the audit appear in the report?

title: Elements have an accessible name failureTitle: Elements do not have an accessible name description: When a $ROLE_NAME_HERE does not have an accessible name screen readers announce it with a generic name, making it unusable for users who rely on screen readers.

The documentation should distill https://www.w3.org/TR/wai-aria-practices-1.1/#name_calculation into a format that applies on a per-role basis. The original section is quite complex.

How is this audit different from existing ones?

• button-name only warns on buttons
• label only on form controls

Though I suspect both just check for existence of the accessible name.

What % of developers/pages will this impact?

I can’t make an estimate. Some roles with accessible name required are probably more common (dialog) while more complex widgets are likely rarer (such as tree)

How is the new audit making a better web for end users?

People using screen readers get a more meaningful announcement when navigating e.g. dialog or tree.

What is the resourcing situation?

Would like to help. I guess the biggest problem is that this new rule doesn’t interfere with existing naming audits so that users don’t get flooded with redundant errors.

Though it might be better to add audits/docs for each role instead.

Any other links or documentation that we should check out?

[connorjclark]

Dedupe #11207. watch #11661 for updates.

[eps1lon]

This sounds like a great candidate for axe-core which is what Lighthouse uses under the hood. Have you already discussed it with that team?

Tracked in dequelabs/axe-core#2421

Can be closed once lighthouse uses axe-core@^4.1.0.