Accessability problem with screen readers

Having problems with building or using the JCEF Java binding? Ask your questions here.

Accessability problem with screen readers

Postby burnyWes » Fri Jan 05, 2018 5:56 am

Hello guys,

we are trying to implement an application for visually impared people with Java-CEF. Our program opens a HTML-page in a window based on a JFrame. We are using screen readers, namly NVDA (open source) and JAWS, to test our implementation.

Now we encountered the following problem:
When we open the HTML-file inside our Java-CEF application, the behavior of the screen readers are not as expected. We can access the button in the testfile and we could access lists and input texts as well in other testfiles, but we can't get access to any header or paragraph what so ever.This content is just not visible for the screen readers. Expacted behavior would be to navigate with TAB or the arrow keys through the page and the screen reader would read out every line or element.

The example HTML-file we're using works just fine with the screen readers in all browsers we tested (Chrome, Firefox) and is perfectly accessable with them. The example looks as follows:

Code: Select all
<!DOCTYPE html>
<html>
<head>
   <meta charset="UTF-8">
    <title>Example</title>
</head>   
<body>
   <h1>Headline</h1>
   <button>click</button>
   <h2>Subsection</h2>
   <p>Paragraph</p>
 </body>
</html>


Maybe you allready encountered this problem, too or have any suggestions where the source of the problem is to find? Is there any option to fix this?

Thanks for any help allready!
burnyWes
Newbie
 
Posts: 3
Joined: Fri Jan 05, 2018 5:22 am

Re: Accessability problem with screen readers

Postby magreenblatt » Fri Jan 05, 2018 12:04 pm

What OS and CEF version are you using? How does it behave with the cefclient sample application at the same version downloaded from http://opensource.spotify.com/cefbuilds/index.html ?
magreenblatt
Site Admin
 
Posts: 12382
Joined: Fri May 29, 2009 6:57 pm

Re: Accessability problem with screen readers

Postby burnyWes » Tue Jan 09, 2018 4:49 pm

First we’re sorry for the late answer. Our OS is Windows 10. The screen readers we’re using to test our software are NVDA 2017.1 and JAWS 18. The version of CEFf is 3.3202.1686.gd665578. We picked it up from here:

https://bitbucket.org/chromiumembedded/cef.git

And Chromium version 62.0.3202.94. Corresponding link:

https://chromium.googlesource.com/chromium/src.git

We downloaded the client application archives from the link you posted and with this application the screen readers work just fine with our example HTML, but it is just CEF and not Java-CEF, isn’t it? So could java in particular JFrame be the problem? Our application is written in Java and Scala. Therefore we’d like to use Java-CEF and not CEF.

Thanks for any suggestions.
burnyWes
Newbie
 
Posts: 3
Joined: Fri Jan 05, 2018 5:22 am

Re: Accessability problem with screen readers

Postby magreenblatt » Thu Feb 01, 2018 5:19 pm

You can try passing the `--force-renderer-accessiblity` command-line flag as a workaround.

The correct implementation on Windows is for clients to detect screen readers by handling the WM_GETOBJECT message as shown here: https://bitbucket.org/chromiumembedded/ ... win.cc-558. I'm not sure what the equivalent detection code would look like for a Java application. You would need to figure that out and then expose/call the CefBrowserHost::SetAccessibilityState method. You can create an issue for this in the JCEF issue tracker, and pull requests are welcome.
magreenblatt
Site Admin
 
Posts: 12382
Joined: Fri May 29, 2009 6:57 pm

Re: Accessability problem with screen readers

Postby burnyWes » Thu Feb 01, 2018 6:32 pm

Ok, thanks for the moment. We will try that.
burnyWes
Newbie
 
Posts: 3
Joined: Fri Jan 05, 2018 5:22 am


Return to JCEF Forum

Who is online

Users browsing this forum: No registered users and 9 guests