A11y: Chrome://accessibility page loses focus on change with NVDA and ChromeVox |
|||||
Issue descriptionChrome: 68.0.3416.0 (Official Build) canary (64-bit) (cohort: Clang-64) NVDA: 2018.1.1 JAWS: 2018 Steps to repro: # With NVDA on, visit chrome://accessibility # Use 'x' to move to the next checkbox or 'b' to move to the next toggle button # Press space to toggle the box # Notice that focus moves to the top of the document Expected: Focus should remain on the recently toggled checkbox Actual: Focus moves to the top of the page # With JAWS on, visit chrome://accessibility # Use 'x' to move to the next checkbox or 'b' to move to the next toggle button # Press space to toggle the box # Notice that focus remains on the checkbox # Press space again # Notice that the same checkbox is toggled again Expected: Works as expected
,
Aug 24
Google Chrome 70.0.3524.2 (Official Build) dev (64-bit) Firmware Version Google_Lulu.6301.136.57 Also reproduces with ChromeVox. Focus is lost upon invoking any of the following: checking any checkbox clicking on any link such as native:true showing the accessibility tree
,
Aug 24
,
Aug 25
,
Aug 27
These actions cause a page refresh, e.g. https://cs.chromium.org/chromium/src/chrome/browser/resources/accessibility/accessibility.js?type=cs&q=toggleAccessibility&sq=package:chromium&g=0&l=39 Quite impressive that JAWS manages to maintain the focus location! Either we need to re-architect such that a page refresh doesn't occur, or we need to re-focus the checkbox in question.
,
Aug 27
,
Oct 8
I'm working on a fix for issue 877705 , the page refresh when ToggleAccessibility is called (from clicking links within a row like native:true). That leaves two issues: page refresh when global accessibility mode options are changed (setGlobalFlag), and lost focus upon showing the tree (not because the page is refreshed but because the row is rewritten). - For the "Global Accessibility mode" options, I think we should keep the refresh and then refocus the checkbox. Otherwise I think the correct alternative would be to go through each row and update the mode for each page, and then request new trees if any are shown? - For lost focus on showing the tree, I think we can just focus each <pre> tree element when it first appears in createAccessibilityModeElement. I believe that's blocked on issue 884966, though; I couldn't get this part to work by calling .focus(). |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by leberly@chromium.org
, Aug 10