New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 909767 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Talkback does not work with W3C standard sliders

Reported by joshua.g...@gmail.com, Nov 28

Issue description

Steps to reproduce the problem:
1. Turn on Talkback
2. Navigate to https://www.w3.org/TR/wai-aria-practices/examples/slider/multithumb-slider.html
3. Attempt to interact with the sliders by using gestures or volume controls

What is the expected behavior?
The sliders should move when the appropriate Talkback actions are performed

What went wrong?
The sliders do not change. In some cases there may be a hint of interaction being aborted.

Did this work before? N/A 

Chrome version: 66.0.3359.15B  Channel: n/a
OS Version: 9
Flash Version: 

Attempted to open a bug for Android but was directed to file this here: https://issuetracker.google.com/issues/119995981

Tested using an AVD emulating Nexus 9 API 28 with the currently available Talkback from Github, as well as a Samsung S8 with Talkback version 6.2.0.199837370
 
Labels: Needs-triage-Mobile
Cc: chelamcherla@chromium.org
Components: -UI UI>Browser>Mobile UI>Accessibility>Compatibility
Labels: Target-70 Target-71 Target-72 M-72 Triaged-Mobile FoundIn-71 FoundIn-70 FoundIn-72
Status: Untriaged (was: Unconfirmed)
Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1. Enabled talkback , navigated to  https://www.w3.org/TR/wai-aria-practices/examples/slider/multithumb-slider.html
2. Sliders doesn't change on using volume controls.

Chrome versions tested:
60.0.3112.113 , 72.0.3624.0

OS:
Android 9.0.0

Android Devices:
Pixel 2 XL

Issue is seen from older M-60 builds. Hence considering this as Non-Regression and marking as Untriaged for further inputs from dev team.

Thanks!
Components: UI>Input Blink>Input
Labels: -Needs-triage-Mobile android-fe-triaged
Status: Available (was: Untriaged)
Labels: a11y-required
Cc: -chelamcherla@chromium.org sindhu.chelamcherla@chromium.org dmazz...@chromium.org
dmazzoni@ - is this supposed to have the UI>Browser>Mobile component? It seems like an issue interacting with web contents.
Components: -UI>Input -Blink>Input -UI>Browser>Mobile
Agreed, updated component. This should belong just to our team.

Sign in to add a comment