feat(MatSelect): Active state should take into account keyboard versus mouse interaction

[elenachiosa]

Feature Description

Hello,
We would like to fully implement accessibility in terms of good color contrast and visible focus states (WCAG Focus Visible).
What we use right now to achieve this is the ":focus-visible" selector. We also use FocusMonitor from the A11yModule of CDK to create accessible keyboard interaction. FocusMonitor has a neat feature - it adds classes specific to the interaction type that the user uses (e.g. on keyboard interaction, the currently focused item has the ".cdk-keyboard-focus" class).

What I'd suggest as an improvement to the Select component is to have this difference illustrated in the component, out of the box. At the moment we are styling the ".mat-active" class in order to have a visible focus state for keyboard users but this looks very odd for mouse users.

Use Case

Currently, the Select component looks exactly the same for both mouse and keyboard interaction.
Stackblitz link with current behavior: https://stackblitz.com/edit/angular-7779kz?file=src%2Fapp%2Fselect-overview-example.html

What we would like to see in the future is the following:
Keyboard interaction with visible outline:

Mouse interaction:

[crisbeto]

It works like this because focus isn't actually on the mat-option, it's on the select's trigger. We use aria-activedescendant to manage focus.

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

[iKrishnaSahu]

Any update on this feature?