Status Update
Comments
al...@thatgamecompany.com <al...@thatgamecompany.com> #2
Android build
Which Android build are you using? (e.g. PPP5.180610.010)
We tested this bug on Pixel devices and observed, it says:
"a% with valuetext slider".
Please confirm if you have also observed the same.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Screen record of the issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Note: Please avoid uploading directly to the issue using attachments. Please upload to google drive and share the folder to android-bugreport@google.com, then share the link here.
uc...@google.com <uc...@google.com>
al...@thatgamecompany.com <al...@thatgamecompany.com> #3
Yes - it says (for example) "50% (pause) with value text (pause) slider"
ar...@google.com <ar...@google.com>
em...@google.com <em...@google.com> #4
em...@google.com <em...@google.com> #5
I would expect it to read the value of aria-valuetext not the % as the author has specifically determined that this is the value that should be read. So in the example above it would read "5000 (pause) with value text (pause) slider"
Often in these cases the value is not even numeric. For example 2 of the sliders at
al...@thatgamecompany.com <al...@thatgamecompany.com> #6
em...@google.com <em...@google.com> #7
W3C ARIA APG working group is creating the slider examples with role slider. According to multiple talkback testing reports, role slider does not work in reading the slider value or the changed value.
Review/talkback testing results comments:
https://github.com/w3c/aria-practices/pull/1746#issuecomment-774498523 https://github.com/w3c/aria-practices/pull/1746#pullrequestreview-600408013 https://github.com/w3c/aria-practices/pull/1755#issuecomment-778638021 https://github.com/w3c/aria-practices/pull/1755#issuecomment-782607921 https://github.com/w3c/aria-practices/pull/1746#issuecomment-784788395 https://github.com/w3c/aria-practices/pull/1746#issuecomment-787642775 https://github.com/w3c/aria-practices/pull/1746#issuecomment-787662740 - I had video recording of talk back for the example in the issue. But I cannot find it. sorry.
Related ARIA APG slider role PR
al...@thatgamecompany.com <al...@thatgamecompany.com> #8
em...@google.com <em...@google.com> #9
em...@google.com <em...@google.com> #10
al...@thatgamecompany.com <al...@thatgamecompany.com> #11
Actual: “50% (pause) with value text (pause) slider”
Expected: “50000 (pause) with valuetext (pause) slider”
(The "50000" is the aria-valuetext" and "with valuetext" is the label of the control).
I agree that we aren't matching ARIA usability expectations. Using aria-valuetext needs to override any reporting of a number or percentage.
For example, a slider could be used for "low", "medium", "high" or days of the week. The percentage would not make sense.
Please reference
"If aria-valuetext is specified, assistive technologies SHOULD render that value instead of the value of aria-valuenow." (the current slider value is equivalent to aria-valuenow).
Note: the reporter in this case is the chair of the ARIA WG, so he knows what he's talking about. Please don't close without further discussion from an engineer.
al...@thatgamecompany.com <al...@thatgamecompany.com> #12
Tested this with TalkBack 9.1 and Chrome 92.0.4515.159 (both latest versions as far as I could tell) and can confirm that the error is still present - input type range is still announcing values in percents. It's even happening for "barebones" input type range;
<label for="d">Select your donation from 100$ to 1000$</label> <input id="d" type="range" step="100" min="100" max="1000" value="100">
This bug is preventing usage of input type range for many other scenarios that need other ranges than 0-100%
Other screen-readers (on PC and iPhone) pronounce the values provided by developers.
Test page with 2 input type range examples :
al...@thatgamecompany.com <al...@thatgamecompany.com> #13
em...@google.com <em...@google.com> #14
Re-tested with latest Google Chrome Canary and it seems that bug still persist - TalkBack is still announcing percents instead of values.
- tested with
https://codepen.io/jnurthen/pen/qBajpGz - all sliders announced % - tested with my example on
https://jsfiddle.net/mdu8903f/1/show - both sliders announced %
Chrome Canary 96.0.4659.3
OS: Android 9; SM-G950F Build/PPR1.180610.011
Talkback 9.1 (12.1.0.397273305)
Description
AI-201.8743.12.41.6858069, JRE 1.8.0_242-release-1644-b3-6222593x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.15.7, screens 1536x960; Retina
AS: 4.1; Kotlin plugin: 1.4.10-release-Studio4.1-1; Android Gradle Plugin: 4.1.0; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: 3.19.0
IMPORTANT: Please read
The lldb debugger and variables view won't display strings when they are (signed char*). They are displayed as individual characters instead. What is the workaround to fix this?