Accessibility issues in CEF 2924 on Mac

[mic]

I'm using CEF3 branch 2924 on macOS, and I find that I cannot get VoiceOver to work without setting the "force-renderer-accessibility" option. As I understand it, the way things are supposed to work is that Chromium turns on or off accessibility support based on whether it sees that a client, such as VoiceOver, has set the "AXEnhancedUserInterface" attribute on the main application window. This doesn't seem to be working.

Moreover, if I set the "force-renderer-accessibility" option, the macOS "speak selected text" feature stops working properly. Without the option it works as expected, but with the option it always reads the whole page, rather than just the selected text.

My testing with the Xcode Accessibility Inspector indicates that with CEF, there is no recognition of objects on the rendered page, only the page as a whole, unless the "force-renderer-accessibility" option is set. Even when it is, not all of the expected accessibility attributes appear to be present.

My web research, including CEF and Chromium forums and bug lists, *seems* to indicate that this issue is part of a general accessibility design omission in CEF that was identified back in 2012, but won't be fixed until a version of CEF released later this year:

* viewtopic.php?f=6&t=12023&p=22311&hilit=accessibility+mac#p22311
* http://www.magpcss.org/ceforum/viewtopi ... over#p6537
* https://bitbucket.org/chromiumembedded/ ... -to-report
* https://bitbucket.org/chromiumembedded/ ... essibility
* https://bitbucket.org/chromiumembedded/ ... pport/diff

Is my conclusion accurate, that the issue I am seeing is caused by the issue associated with the links above? If so, what branch will include this fix?

If my conclusion does not seem accurate, can you reproduce the behavior I describe and recommend a solution?

Thanks in advance for any help you can provide.

[magreenblatt]

You can star https://bitbucket.org/chromiumembedded/cef/issues/1217 to be notified on the fix and related revisions.

[mic]

Thanks. Would you say, then, that issue #1217 is the cause of the problem I describe?

If so, would you also say that once the fix is available, a macOS application embedding CEF that wants accessibility to work will have to upgrade to that branch, as well as add custom application code to support what appears to be a new accessibility API? Is there some piece of the solution that requires participation from the embedding app, or can the CEF browser object behave accessibly on its own? Is there some fix for earlier branches that the embedding application can implement?

[magreenblatt]

Issue 1217 will expose accessibility functions. For windowed browsers you need to call that function as shown here: https://bitbucket.org/chromiumembedded/ ... ent_mac.mm