Skip to content

Some MatSelect elements have an aria-labelledby referring to a non-existent ID #12157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mikzat opened this issue Jul 11, 2018 · 2 comments
Closed

Comments

@mikzat
Copy link

mikzat commented Jul 11, 2018

Bug, feature request, or proposal:

On some MatSelect elements, aXe plugin reports, with a suggestion like this:

ARIA attributes must conform to valid values

Fix the following:
Invalid ARIA attribute value: aria-labelledby="mat-form-field-label-3"

And when inspecting the page, there really is no element with ID mat-form-field-label-3.

What is the expected behavior?

aria-labelledby on a <mat-select> refers to an existing label element with the correct ID.

aXe plugin should not show MatSelect issue ARIA attributes must conform to valid values.

What is the current behavior?

aria-labelledby on a <mat-select> sometimes refers to a non-existent ID.

aXe plugin reports issue ARIA attributes must conform to valid values.

What are the steps to reproduce?

  1. Go to https://material.angular.io/components/select/overview
  2. Run aXe
  3. Issue detected on MatSelect under the Select with 2-way value binding section

What is the use-case or motivation for changing an existing behavior?

Accessibility

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Tested with Chrome Version 67.0.3396.99 (Official Build) (64-bit)

Is there anything else we should know?

@mikzat mikzat changed the title Some MatSelect elements refer to a missing aria-labelledby Some MatSelect elements have an aria-labelledby referring to a non-existent ID Jul 11, 2018
@crisbeto
Copy link
Member

Will be resolved by #11806.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants