Skip to content

Native select examples are missing programatic labels #15022

Closed
@mfairchild365

Description

@mfairchild365

What is the expected behavior?

The purpose of the native select elements in the select example must be conveyed to users of screen reader software.

What is the current behavior?

The purpose of the native select elements in the select example is not conveyed to users of screen reader software.

What are the steps to reproduce?

  1. Using either of the following screen readers
    • NVDA 2018.4.1 + Firefox 64
    • VoiceOver for IOS (12.1.3) + Safari
  2. Open the select example
  3. Navigate to one of the native select elements in the examples.
    • In NVDA you can press the tab key until you reach a select element
    • In VoiceOver for iOS you can swipe right until you reach a select element
  4. Observe that the purpose of the select element is not conveyed by the screen reader.

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

Is there anything else we should know?

Select elements must have a meaningful programmatic label. This does not appear to be an issue with the component itself, but rather with the way that the examples are implemented. The examples should be updated to demonstrate accessible implementations.

Metadata

Metadata

Assignees

Labels

AccessibilityThis issue is related to accessibility (a11y)P4A relatively minor issue that is not relevant to core functionsdocsThis issue is related to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions