Issue metadata
Sign in to add a comment
|
ChromeVox Accessibility Focus lost on overlay open
Reported by
hardik.s...@gmail.com,
Jun 12 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Have a html page build with a code containing a dynamic overlay opened on clicking any link. 2. As per DOM structure is concerned, we are adding the overlay at the end of the DOM structure and switching the focus on the overlay container once the overlay gets opened. What is the expected behavior? Once the link is clicked and overlay is opened the focus should be switched to the overlay container. What went wrong? When the Chrome-Vox extension is disabled, it works as expected in Chrome browser. The focus is transferred to the container containing the overlay. But when the Chrome-Vox extension is activated, the focus is left on the link which is clicked for opening the overlay. So the focus never makes up to the overlay. Note: this is only issue when the Chrome-Vox Extension is enabled. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 58.0.3029.110 Channel: stable OS Version: OS X 10.12.5 Flash Version: Note: This is issue with Windows OS as well.
,
Jun 13 2017
Removing from Mac bug queue.
,
Jun 14 2017
Thanks for filing the issue. hardik.smartguy@, Could you please provide us a sample html file/test file to triage the issue further from our end.
,
Jun 14 2017
Hi jmukthavaram@, I have tried to replicate the similar scenario what we have in our project. Our project is developed in Ember.js framework. It is basically, when we redirect to some route(Terminology of a page in Ember.js) we have a container, which gets filled up with the overlay content. But beneath the overlay we render the previous page, to give a look of the overlay being opened up on the previous page. Handling of focus is done by this way: We have an overlay(Div with class="overlay-container" in the attache file) that represents a component in Ember.js and there is hook in Ember framework, "afterRender" where we trigger to focus the div with class="overlay" in the attached example. This "afterRender" gets triggered once the DOM structure is rendered and we tend to focus the component it self.
,
Jun 14 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 15 2017
Tested the issue on Chrome #58.0.3029.110, Current Stable #59.0.3071.86 and Canary #61.0.3131.0 on Mac 10.12.5 and Windows 10.0 and was not able to reproduce the issue. Please find the screen shot for reference. @Reporter: Could you please let us know if i have missed anything. If possible, create new profile with out extensions and apps. Re-check once and let us know the observation of the issue which would help us to triage the issue further. Thanks in Advance!
,
Jun 15 2017
Hi msrchandra@, Thanks for replying and trying this. So this is something what is happening with the framework what we have Ember.js. Also, the way we have handled the overlays, i wont be able to showcase the same program for that. But I tried it in the Canary #61.0.3131.0 on Mac 10.12.5 and it is working fine in the Canary build, but not in the current stable build of Chrome. Also, one thing i noticed on the current Chrome version, that when the overlay opens, the Browser Focus gets transferred to the overlay container but the ChromeVox focus still remains on the link that was clicked which triggered the overlay.
,
Jun 15 2017
Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 20 2017
Able to reproduce the issue on Windows 10, Ubuntu 14.04 and Mac 10.12.5 using reported Stable version #58.0.3029.110, latest stable version #59.0.3071.104 and latest canary #61.0.3135.4. This is a Regression issue broken in M-51 Please find the bisect information from below: Bisect Information: ===================== Good build: 51.0.2679.0 Revision(381134) Bad Build : 51.0.2680.0 Revision(381354) Change Log URL: https://chromium.googlesource.com/chromium/src/+log/974fa818537a8d00fb3537a836db79e2539a7889..2f9367a3f1bc731e1cae19edfa3b89bc18071093 Unable to find exact suspect from Changelog Could anyone from dev team please look into it Thanks...!!
,
Aug 1 2017
,
Sep 20 2017
Setting to available since there has already been work on this bug.
,
Sep 21
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
,
Sep 21
The ChromeVox extension is only in maintenance mode. Feel free to file a bug if this repros with a native screen reader, or with ChromeVox on Chrome OS. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Jun 13 2017Labels: Needs-Milestone