Mac accessibility support

Having problems with building or using CEF's C/C++ APIs? This forum is here to help. Please do not post bug reports or feature requests here.

Mac accessibility support

Postby starkos » Fri Aug 08, 2014 7:17 am

I'm having a look at getting OS X VoiceOver support working. Setting the --force-renderer-accessibility flag was all I needed to get basic pages working, but the accessibility object tree doesn't seem to be getting updated when the DOM changes, like when Javascript pops up a new <div> for a menu, for instance.

I saw the NSAccessibility protocol mentioned here: http://www.magpcss.org/ceforum/viewtopic.php?f=10&t=3133&p=6537&hilit=voiceover#p6537, but I'm unclear on how it should be wired up. I'm digging through the Chromium code to try and understand, but any pointers would be much appreciated. Thanks!

(I'm using the CEF3 1750 branch).
starkos
Techie
 
Posts: 18
Joined: Mon Jun 24, 2013 12:35 pm

Re: Mac accessibility support

Postby magreenblatt » Fri Aug 08, 2014 7:22 am

See https://code.google.com/p/chromium/code ... dr=C&l=538

The client NSWindow can implement this functionality, but then CEF will likely need to expose content::BrowserAccessibilityState so that the application can (indirectly) call content::BrowserAccessibilityState::GetInstance()->OnScreenReaderDetected();.
magreenblatt
Site Admin
 
Posts: 12409
Joined: Fri May 29, 2009 6:57 pm

Re: Mac accessibility support

Postby starkos » Sat Aug 09, 2014 9:50 am

Perfect, thanks! I did notice that popup content is working better in the newer builds (2062 and dev); I am upgrading my framework from 1750 now.
starkos
Techie
 
Posts: 18
Joined: Mon Jun 24, 2013 12:35 pm


Return to Support Forum

Who is online

Users browsing this forum: No registered users and 110 guests