|
|
Rank: Newbie
Groups: Member
Joined: 12/12/2019
Posts: 8
|
Context - We use EO browser within a .net/WPF app - The app is used in certain situations by visually impaired users with ADA needs - They have to login into our app using a SAML/webpage from customer side Issue - the page within the browser is NOT presenting itself as accessible page. JAWS reader doesn't work - However, if the page is directly on a browser, things work - notes from developers "The issue here is with the EO Browser, the --force-renderer-accessibility flag has no effect on it. The flag works fine with chrome. The Jaws screen reader is announcing what is pressed on the keyboard, no accessibility information is being exposed by the Browser used in our application." 
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
This is a known issue in the current version. Our next release which should come out early January should work the same as Chrome does.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 12/12/2019
Posts: 8
|
- thank you
- Is there a date for this release, so we can tell our customers?
- Was this working in any previous versions of EO Webbrowser, so we can try to downgrade in the mean time?
regards,
Raj
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
This issue was only recently brought to our attention and should only exists in version 2019. Version 2018 and before should not have this issue. We will have our new initial 2020 release in January and the new release should resolve this issue.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 12/12/2019
Posts: 8
|
Hi,
How can I get the 2018 version for download? I logged into my account but couldn't find a link. Can you help, please?
regards,
Raj
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
Please see your private message for the download location.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 12/12/2019
Posts: 8
|
Hi,
We have been using the new January 2020 version and it does correct the main issue. However, it does not work fully with JAWS (JAWS 2020.2001.70 was used for testing). Things work great with NVDA and Narrator, but with JAWS, the component is not capturing all of the entered characters. When entering values into username/password fields, some characters are missed and do not appear in the field. This test worked fine in the 2018 version of EO that we downgraded to earlier, but does not work well in this 2020 version. Can you let us know if this is a known issue, and if not, can you reproduce it and open something to have it corrected?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
Please check the latest build (2020.0.53) and see if it resolves the issue for you.
The accessibility support is directly handled by the browser engine and we do not add or modify that part. In version 2019 it was broken due to an error on our end (we passed "--disable-legacy-window" command line argument to the browser engine, which would also broke accessibility support since this "legacy window" is used to support accessibility). This error has been corrected in v2020. However beside that we do not debug into specific accessibility support since it is not practical for us to debug into every Chromium feature.
There might be other things that can affect accessibility support indirectly. For example, we intercept keyboard events route it through your .NET application in order to trigger .NET side keyboards events. The latest build fixed an issue related to keyboard events. So you may want to try it out and see if it works better for you.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 12/12/2019
Posts: 8
|
Hi,
Thank you. We will try it.
|
|
Rank: Newbie
Groups: Member
Joined: 12/12/2019
Posts: 8
|
Hi, The latest build did not resolve the issue with JAWS. Here are a couple of videos: Older EO version that does not miss keystrokes: https://www.dropbox.com/s/bsf9s5wi4ym31lw/WPA%20v2019.12.1%20-%20JAWS%20demo.mkv?dl=02020.0.53 version that does miss keystrokes: https://www.dropbox.com/s/237t6qr2vn7fxgh/WPA%20v.2020.2.18%20-%20JAWS%20demo.mkv?dl=0Please let us know if you are able to provide a build that works as before.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi, Do you mean that JAWS missing announcing letters or letters you typed on the keyboard failed to show in the textbox? If the problem is later, you can try to disable event routing all together. You can disable .NET side event routing by implementing IInputMsgFilter and then returns InputMsgTarget.WebView from your PreDispatchMsg method. See here for more details: https://www.essentialobjects.com/doc/webbrowser/advanced/input_events.aspxPlease let us know if this works for you. Thanks!
|
|