Issue metadata
Sign in to add a comment
|
UIA Accessibility broken (no tree beneath Chrome Legacy Window pane)
Reported by
alexval...@gmail.com,
Jul 17 2016
|
||||||||||||||||||||
Issue descriptionChrome Version : 49.0.2623 URLs (if applicable) : any Other browsers tested: Chromium 49.0.2618: OK What steps will reproduce the problem? (1) Show any web page (example.com is fine) (2) Verify Global Accessibility Mode is on (3) Use Inspect.exe or other UIA Accessibility inspection tool to attempt to inspect any element within the page What is the expected result? A full accessibility tree is available to UIA insepction What happens instead? Only a "Chrome Legacy Window" pane with no content is provided Please provide any additional information below. Attach a screenshot if possible. MSAA legacy accessibility also appears non-functional. Bisection testing isolates the change to between 49.0.2618 and 49.0.2623. The issue remains in later versions.
,
Jul 29 2016
Chrome doesn't enable accessibility unless it detects a screen reader or other advanced use of the accessibility APIs. To enable it manually, you can start Chrome with the --force-renderer-accessibility command-line flag, or visit chrome://accessibility to enable it for one session.
,
Aug 7 2016
Please see step 2, where I verify that global accessibility mode is on. I used chrome://accessibility, but I have just checked with the command line flag for completeness, and the issue is still reproduced. Please also note that the behaviour changes between the version numbers I supplied, with otherwise identical configuration.
,
Aug 8 2016
OK, thanks - I'll take a closer look at what happened between those versions. Whatever happened, it doesn't seem to be affecting JAWS, NVDA, or ZoomText, because we've been testing with those and haven't received any reports from other users of breakage in that timeframe.
,
Aug 9 2016
Thanks. I think those readers work because they can use IAccessible2, which is still working fine. It's only the UIA accessibility that broke.
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 4 2017
,
Dec 14 2017
,
Dec 17
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 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by cbiesin...@chromium.org
, Jul 25 2016