New issue
Advanced search Search tips

Issue 864713 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 18
Cc:
lgrey@chromium.org
ellyjo...@chromium.org
aboxhall@chromium.org
dmazz...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

Web content a11y tree is only generated when VoiceOver is turned on

Project Member Reported by sdy@chromium.org, Jul 17 
Chrome Version: 69.0.3494.0
OS: macOS

What steps will reproduce the problem?
(1) With VoiceOver turned *off*, use the Accessibility Inspector or another a11y tool to explore a web page in Chrome.

What is the expected result?
The web page has an a11y tree.

What happens instead?
The UI is accessible but web content is not.

I heard about this from lgrey@. Tools other than VoiceOver may need to use the a11y tree. It seems fine for the tree to be created lazily, but it probably shouldn't be tied to VoiceOver activation.

Comment 1 by ellyjo...@chromium.org, Jul 18

Labels: -Pri-2 Pri-3
Status: WontFix (was: Untriaged)
I think this is WontFix:

There are no a11y tools that are used on Mac (so far as I know - I'll check with the a11y team) with VoiceOver turned off, although I suspect many users are using VoiceOver with speaking muted so they can get the keyboard navigation behavior. Supporting having VoiceOver all the way disabled but having other a11y technology enabled is a pretty niche case for us. Also, generating the a11y tree is quite expensive.

I think that in the absence of a concrete report of another a11y tool not working for people - in which case we can figure out how to activate when that tool is present - there's nothing we need to do here right now.
►

Sign in to add a comment