New issue
Advanced search Search tips

Issue 629829 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 28
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Focus on fixed elements in talkback mode not as expected.

Reported by ashli...@samsung.com, Jul 20 2016

Issue description

Example URL:
naver.com

Steps to reproduce the problem:
1. Enable talkback from accessibility settings. 
2. Fetch naver.com and scroll the page to bottom.
3. Click on the page up button present in the bottom right corner of the screen.
4. Now that the button is focused with a blue rect, scroll the page again. 

What is the expected behavior?
The blue rect (focus) for the button should not move i.e should stay with the button which is fixed.

What went wrong?
The blue focus rect moves with page while scrolling

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? N/A 

Chrome version: 51.0.2704.81  Channel: n/a
OS Version: Android L
Flash Version: 

The issue is observed for all fixed elements. Browser doesn't understand fixed elements in talkback mode and as a result when fixed elements are focused and then moved, the focus rect moves along with the scroll.
 

Comment 1 by e...@chromium.org, Jul 21 2016

Components: -Blink UI>Accessibility
Cc: krav...@chromium.org
Labels: triage-te
Cc: -krav...@chromium.org
Labels: -triage-te M-52
Owner: dmazz...@chromium.org
Status: Assigned (was: Unconfirmed)
Status: Available (was: Assigned)
Owner: ----
Labels: NewComponent-Accessibility-Compatibility
Labels: NewComponent-Accessibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Labels: triage-android-remaining
Project Member

Comment 11 by sheriffbot@chromium.org, Aug 8

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
I couldn't reproduce this on chrome 69. Closing for now, feel free to reopen if it's still an issue!

Sign in to add a comment