Skip to content
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

progress-spinner: indeterminate state not correctly exposed to screen readers #15018

Closed
mfairchild365 opened this issue Jan 30, 2019 · 1 comment · Fixed by #15052
Closed
Assignees
Labels
Accessibility This issue is related to accessibility (a11y) help wanted The team would appreciate a PR from the community to address this issue P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@mfairchild365
Copy link

What is the expected behavior?

The indeterminate state of a progress spinner must be conveyed to users that are using screen reader software.

What is the current behavior?

Users hear something like '0%'. This does not convey an indeterminate state.

What are the steps to reproduce?

  1. Using VoiceOver for IOS (12.1.3) + Safari
  2. Open the progress spinner example
  3. swipe right until you reach the 'indeterminate' radio button
  4. double tap the screen to select the 'indeterminate' radio button
  5. swipe right until you reach the progress spinner
  6. Observe that the progress spinner is announced as '0%'.

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

Is there anything else we should know?

The ARIA spec states that authors should omit the aria-valuenow attribute to convey the indeterminate state. The attribute is set to aria-valuenow="50" after switching to the indeterminate in the example.

@crisbeto crisbeto self-assigned this Jan 30, 2019
crisbeto added a commit to crisbeto/material2 that referenced this issue Feb 1, 2019
Clears the `aria-valuenow` attribute when the progress spinner is in indeterminate mode, [based on the a11y spec](https://www.w3.org/TR/wai-aria-1.1/#progressbar).

Fixes angular#15018.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent Accessibility This issue is related to accessibility (a11y) has pr labels Feb 1, 2019
@jelbourn jelbourn added the help wanted The team would appreciate a PR from the community to address this issue label Feb 6, 2019
jelbourn pushed a commit that referenced this issue Feb 22, 2019
)

Clears the `aria-valuenow` attribute when the progress spinner is in indeterminate mode, [based on the a11y spec](https://www.w3.org/TR/wai-aria-1.1/#progressbar).

Fixes #15018.
@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 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Accessibility This issue is related to accessibility (a11y) help wanted The team would appreciate a PR from the community to address this issue P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants