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

fix(material/slider): some screen readers announcing long decimal values #20721

Merged
merged 1 commit into from
Oct 7, 2020

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Oct 5, 2020

It looks like some screen readers announce the value of a slider by calculating the percentage themselves using the aria-valuemin, aria-valuemax and aria-valuenow. The problem is that they don't round down the decimals so for a slider between 0 and 1 with a step of 0.1, they end up reading out values like 0.20000068. These changes work around the issue by setting aria-valuetext to the same value that we shown in the thumb which we truncate ourselves.

Fixes #20719.

@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) target: patch This PR is targeted for the next patch release labels Oct 5, 2020
@crisbeto crisbeto requested a review from mmalerba as a code owner October 5, 2020 15:04
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 5, 2020
@crisbeto crisbeto changed the title fix(slider): some screen readers announcing long decimal values fix(material/slider): some screen readers announcing long decimal values Oct 5, 2020
It looks like some screen readers announce the value of a slider by calculating the
percentage themselves using the `aria-valuemin`, `aria-valuemax` and `aria-valuenow`.
The problem is that they don't round down the decimals so for a slider between 0 and 1
with a step of 0.1, they end up reading out values like 0.20000068. These changes work
around the issue by setting `aria-valuetext` to the same value that we shown in the thumb
which we truncate ourselves.

Fixes angular#20719.
@crisbeto crisbeto force-pushed the 20719/slider-long-decimals branch from c8c9a21 to b60607e Compare October 5, 2020 15:08
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mmalerba mmalerba added the action: merge The PR is ready for merge by the caretaker label Oct 5, 2020
@wagnermaciel wagnermaciel merged commit d93e16f into angular:master Oct 7, 2020
wagnermaciel pushed a commit that referenced this pull request Oct 7, 2020
…ues (#20721)

It looks like some screen readers announce the value of a slider by calculating the
percentage themselves using the `aria-valuemin`, `aria-valuemax` and `aria-valuenow`.
The problem is that they don't round down the decimals so for a slider between 0 and 1
with a step of 0.1, they end up reading out values like 0.20000068. These changes work
around the issue by setting `aria-valuetext` to the same value that we shown in the thumb
which we truncate ourselves.

Fixes #20719.

(cherry picked from commit d93e16f)
wagnermaciel added a commit that referenced this pull request Oct 8, 2020
wagnermaciel added a commit that referenced this pull request Oct 8, 2020
wagnermaciel added a commit that referenced this pull request Oct 8, 2020
…imal values (#20721)" (#20753)

This reverts commit d93e16f.

(cherry picked from commit a217509)
@wagnermaciel
Copy link
Contributor

@crisbeto I had to revert this change because it overrides custom aria-values

@crisbeto
Copy link
Member Author

crisbeto commented Oct 8, 2020

No problem, I hadn't accounted for that. I'll resubmit it.

@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 Nov 8, 2020
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) action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(Slider): Jaws and NVDA incorrectly announcing decimal numbers
4 participants