Issue metadata
Sign in to add a comment
|
Accessibility of the sign in dialog in chrome canary is completely broken
Reported by
driemer....@gmail.com,
May 22 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. create a new person. 2. try to sign in. 3. focus lands on close (A button) when you do so. What is the expected behavior? the behavior present in chrome stable (The sign in dialog is accessible). What went wrong? The sign in dialog in chrome canary is simply not present to NVDA. The only thing present is a close button. I looked at the a11y tree (Via nvda), and there's an exact subset of what there should be in canary, the branch with the actual dialog is simply not present. Here's a log snippet from NVDA where I show the tree I see in that dialog and then I OCR the screen and show that the text I expect is there. IO - speech.speak (10:19:11.897): Speaking [u'Move focus'] IO - speech.speak (10:19:11.970): Speaking [u'Chrome document'] IO - inputCore.InputManager.executeGesture (10:19:13.285): Input: kb(laptop):shift+NVDA+downArrow DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:13.290): Resorting to WindowFromPoint on accLocation DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:13.296): Resorting to WindowFromPoint on accLocation IO - speech.speak (10:19:13.298): Speaking [u'grouping'] IO - inputCore.InputManager.executeGesture (10:19:13.709): Input: kb(laptop):shift+NVDA+downArrow DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:13.732): Resorting to WindowFromPoint on accLocation DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:13.736): Resorting to WindowFromPoint on accLocation DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:13.740): Resorting to WindowFromPoint on accLocation IO - speech.speak (10:19:13.743): Speaking [u'grouping'] IO - inputCore.InputManager.executeGesture (10:19:14.085): Input: kb(laptop):shift+NVDA+downArrow DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:14.105): Resorting to WindowFromPoint on accLocation DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:14.111): Resorting to WindowFromPoint on accLocation IO - speech.speak (10:19:14.114): Speaking [u'pane'] IO - inputCore.InputManager.executeGesture (10:19:14.276): Input: kb(laptop):shift+NVDA+downArrow IO - speech.speak (10:19:14.292): Speaking [u'No objects inside'] IO - inputCore.InputManager.executeGesture (10:19:14.796): Input: kb(laptop):NVDA+space IO - inputCore.InputManager.executeGesture (10:19:15.076): Input: kb(laptop):downArrow IO - speech.speak (10:19:15.098): Speaking [u'button', u'Close'] IO - inputCore.InputManager.executeGesture (10:19:15.493): Input: kb(laptop):downArrow IO - speech.speak (10:19:15.522): Speaking [u'button', u'Close'] IO - inputCore.InputManager.executeGesture (10:19:15.661): Input: kb(laptop):upArrow IO - speech.speak (10:19:15.681): Speaking [u'button', u'Close'] IO - inputCore.InputManager.executeGesture (10:19:16.516): Input: kb(laptop):shift+NVDA+backspace IO - speech.speak (10:19:16.525): Speaking [u'Move focus'] IO - inputCore.InputManager.executeGesture (10:19:17.236): Input: kb(laptop):shift+NVDA+leftArrow DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:17.246): Resorting to WindowFromPoint on accLocation DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:17.250): Resorting to WindowFromPoint on accLocation DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:17.255): Resorting to WindowFromPoint on accLocation IO - speech.speak (10:19:17.256): Speaking [u'grouping'] IO - inputCore.InputManager.executeGesture (10:19:18.924): Input: kb(laptop):NVDA+r IO - speech.speak (10:19:18.979): Speaking [u'Running OCR'] IO - speech.speak (10:19:19.447): Speaking [u'Done'] IO - inputCore.InputManager.executeGesture (10:19:19.740): Input: kb(laptop):NVDA+upArrow IO - speech.speak (10:19:19.760): Speaking [u'Top'] IO - speech.speak (10:19:19.762): Speaking [u'Sign in with your Google Account to get your bookmarks, '] IO - inputCore.InputManager.executeGesture (10:19:21.220): Input: kb(laptop):NVDA+downArrow IO - speech.speak (10:19:21.230): Speaking [u'history. passwords, and other settings on all your devices '] IO - inputCore.InputManager.executeGesture (10:19:22.805): Input: kb(laptop):NVDA+downArrow IO - speech.speak (10:19:22.825): Speaking [u'Enter your email '] IO - inputCore.InputManager.executeGesture (10:19:23.357): Input: kb(laptop):NVDA+downArrow IO - speech.speak (10:19:23.367): Speaking [u'Need help lihding your account? '] IO - inputCore.InputManager.executeGesture (10:19:24.469): Input: kb(laptop):NVDA+downArrow IO - speech.speak (10:19:24.476): Speaking [u'More cpm-. '] IO - inputCore.InputManager.executeGesture (10:19:25.157): Input: kb(laptop):NVDA+downArrow IO - speech.speak (10:19:25.164): Speaking [u'Google '] IO - inputCore.InputManager.executeGesture (10:19:25.525): Input: kb(laptop):NVDA+downArrow IO - speech.speak (10:19:25.539): Speaking [u'Bottom'] IO - speech.speak (10:19:25.539): Speaking [u'Google '] IO - inputCore.InputManager.executeGesture (10:19:28.150): Input: kb(laptop):NVDA+f1 DEBUGWARNING - NVDAObjects.IAccessible.IAccessible.__init__ (10:19:28.168): Resorting to WindowFromPoint on accLocation DEBUGWARNING - watchdog._watcher (10:19:29.165): Trying to recover from freeze, core stack: File "nvda.pyw", line 199, in <module> File "core.pyc", line 396, in main File "wx\_core.pyc", line 8657, in MainLoop File "wx\_core.pyc", line 7952, in MainLoop File "core.pyc", line 367, in Notify File "queueHandler.pyc", line 83, in pumpAll File "queueHandler.pyc", line 50, in flushQueue File "scriptHandler.pyc", line 145, in _queueScriptCallback File "scriptHandler.pyc", line 187, in executeScript File "globalCommands.pyc", line 1419, in script_navigatorObject_devInfo File "logging\__init__.pyc", line 1167, in info File "logHandler.pyc", line 132, in _log File "wx\_core.pyc", line 13263, in SetInsertionPointEnd INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (10:19:29.198): Developer info for navigator object: name: None role: ROLE_GROUPING states: STATE_READONLY isFocusable: False hasFocus: False Python object: <NVDAObjects.Dynamic_GroupboxIa2WebIAccessible object at 0x051C30B0> Python class mro: (<class 'NVDAObjects.Dynamic_GroupboxIa2WebIAccessible'>, <class 'NVDAObjects.IAccessible.Groupbox'>, <class 'NVDAObjects.IAccessible.ia2Web.Ia2Web'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: None location: (459, 63, 448, 612) value: u'' appModule: <'appModuleHandler' (appName u'chrome', process ID 14528) at address 56aebd0> appModule.productName: u'Google Chrome' appModule.productVersion: u'60.0.3104.0' TextInfo: <class 'NVDAObjects.IAccessible.IA2TextTextInfo'> windowHandle: 1123482 windowClassName: u'Chrome_RenderWidgetHostHWND' windowControlID: -1487226576 windowStyle: 1445986304 windowThreadID: 7508 windowText: u'Chrome Legacy Window' displayText: u'' IAccessibleObject: <POINTER(IAccessible2) ptr=0xd327e94 at 54fc7b0> IAccessibleChildID: 0 IAccessible event parameters: windowHandle=1123482, objectID=-4, childID=-11766 IAccessible accName: None IAccessible accRole: ROLE_SYSTEM_GROUPING IAccessible accState: STATE_SYSTEM_READONLY, STATE_SYSTEM_VALID (64) IAccessible accDescription: None IAccessible accValue: u'' IAccessible2 windowHandle: 0 IAccessible2 uniqueID: -11766 IAccessible2 role: ROLE_SYSTEM_GROUPING IAccessible2 states: IA2_STATE_OPAQUE (1024) IAccessible2 attributes: u'' Did this work before? Yes stable Chrome version: 60.***** Channel: stable OS Version: 10.0 Flash Version: I don't know where this regressed but this is uber serious. It's a show stopper for blind people adopting chrome if it lands.
,
May 22 2017
Thanks for the report, we will investigate and update the thread.
,
May 23 2017
Tested this issue on Windows 10 with chrome #60.0.3108.0 using NVDA 2017.1 Followed the steps as mentioned in the comment #0 Observed that on clicking sign-in button, it as readout the Input field as "Email or Phone edit" Attaching screen-cast for reference. driemer.riemer@ Could you please look into it and let us know your observations.
,
May 23 2017
Hi: I am sorry, I did not describe this issue very well. I am using a screen reader called NVDA, and it speaks the contents of the screen. The issue is that NVDA is being focused on a close button, and the actual fields in the dialog are not being exposed, even via the accessibility APIs. Is there any audio in this screen cast? I am completely blind, so I can't verify what visually was shown, but I'd be happy to provide an audio demo of what NVDA sees. Thanks.
,
May 23 2017
Thank you for providing more feedback. Adding requester "kkaluri@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
,
May 24 2017
Unable to reproduce this issue on Windows 10 with chrome Stable #58.0.3029.110, Beta #59.0.3071.61, Dev #60.0.3107.4 But observed in consistency in Canary #60.0.3109.0, After clicking on sign-in button sometimes focus is at close(X) button and sometimes focus is at input field. Unable to provide screen-cast for this issue, since laptop microphone is not catching screen reader output clearly. Untriaging this issue for further triage from accessibility dev team. Thank You...
,
May 25 2017
As per schedule, M-60 will branched today(05/25) and promoted to Beta during 1st week of June. dmazzoni@@: Since this is marked as Beta blocker, Could you please review this and help in further investigation. Thank you!
,
May 25 2017
Will try to take a look. Since it seems to have broken recently, a bisect would be really helpful.
,
May 29 2017
Unable to reproduce this issue on Windows 10 with chrome M60-Branch Build #60.0.3112.6, Canary #61.0.3114.0 Observed after clicking on sign-in button focus is at input field. In comment #6, when tested this issue on canary #60.0.3109.0, observed issue is consistent.Observed after clicking on sign-in button sometimes focus is at close(X) button and sometimes focus is at input field. Due to this inconsistent behavior, unable to provide the reliable bisect info for this issue. Removing needs-bisect label for now. feel free to add it back, once we have consistent steps to reproduce the issue. Requesting for further help
,
May 30 2017
Looks like the issue is resolved in latest Dev and canary. driemer.riemer@ could you please update the thread with your findings.
,
Jun 6 2017
Removing RBS, if the issue still persist please update.
,
Aug 4 2017
,
Aug 4 2017
Sounds like something got fixed. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 Deleted