Community
Participate
Working Groups
There are several SWT accessibility snippets that work correctly with NVDA, but not with JAWS. The snippets numbers are: 162, 164, 357, 363. The main problems are: 1. JAWS does not react to 'mouse over' event 2. JAWS does not read text from associated elements (e.g. 'live' label associated with text field) I tested them with SWT 3.102 (Eclipse 4.3.1) and SWT 3.103 (Eclipse 4.4 M4). Moreover snippet 334 does not work correctly with both screen readers. My environment: - Windows 7 x64 - JAWS 14.0.6005 - NVDA 2013.2
(In reply to Wojciech Sudol from comment #0) > There are several SWT accessibility snippets that work correctly with NVDA, > but not with JAWS. > The snippets numbers are: 162, 164, 357, 363. > The main problems are: > 1. JAWS does not react to 'mouse over' event > 2. JAWS does not read text from associated elements (e.g. 'live' label > associated with text field) The second problem is most likely the regression bug 421255 which is fixed in 4.4 M5. Niraj, can you please investigate the first problem mentioned above and check if that is fixed too? Thanks!
(In reply to Arun Thondapu from comment #1) > (In reply to Wojciech Sudol from comment #0) > > There are several SWT accessibility snippets that work correctly with NVDA, > > but not with JAWS. > > The snippets numbers are: 162, 164, 357, 363. > > The main problems are: > > 1. JAWS does not react to 'mouse over' event > > 2. JAWS does not read text from associated elements (e.g. 'live' label > > associated with text field) > > The second problem is most likely the regression bug 421255 which is fixed > in 4.4 M5. Unfortunately no. The problem described in bug 421255 concerned Snippet340 and does not occur in 4.3.1. I have found similar problem when testing Snippet363, but in this case it does not work in both - Eclipse 4.3.1 and 4.4 M4, so it is most likely a different bug.
Created attachment 238958 [details] Snippet that shows one of accessibility bugs. Please also take a look at the attached snippet which shows one of the problems. After sending ACC.EVENT_NAME_CHANGED event, the AccessibleListener.getName() is correctly called, but JAWS does not read the modified name. With NVDA it works correctly.
Hi Wojciech, problem that you mentioned can only be seen with AccessibilityProblem.java Sharing my observation after fix for bug 421255 targeted for 4.4 M5(to be released): With NVDA: - Every time we type in the text field, NVDA speaks up the updated text info. (NVDA responds to ACC.EVENT_NAME_CHANGED event fired from SWT) With JAWS: - Every time we type in, JAWS only speaks the letter we typed in, and not the updated text information.(It seems JAWS is not responding to ACC.EVENT_NAME_CHANGED event fired from SWT) - But when we loose the focus from this field(or regain focus), JAWS will read the updated information. With SWT: ACC.EVENT_NAME_CHANGED event is fired consistently, every-time we type in the text field of AccessibilityProblem snippet. NVDA responds on this event and JAWS doesn't. As of now this seems an issue on JAWS end.
(In reply to Niraj Modi from comment #4) > > With SWT: > ACC.EVENT_NAME_CHANGED event is fired consistently, every-time we type in > the text field of AccessibilityProblem snippet. > NVDA responds on this event and JAWS doesn't. As of now this seems an issue > on JAWS end. If this is the case, don't we need to open a bug report with JAWS? Carolyn used to have the information to open JAWS problem reports. PW
Hi, I just wanted to file a bug because the "Quick Access" does not work with Jaws (see bug 393365). As I understand, you think it's a Jaws problem, right? Have you filed a bug at Freedom Scientific for this and did you get any feedback already? Best regards, Thomas
Any update on this? This bug seems to cause an issue which makes the Quick Access (Ctrl+3) UNUSABLE for Jaws users! The issue still exists with Jaws 16 and Eclipse 4.5 (Mars Milestone 4 (4.5.0M4) Build id: 20141217-1924). Please at least open a bug report at FS to make sure something happens - at least some day... Best regards, Thomas
(In reply to Thomas Schulze zur Wiesch from comment #7) > Any update on this? > > This bug seems to cause an issue which makes the Quick Access (Ctrl+3) > UNUSABLE for Jaws users! The issue still exists with Jaws 16 and Eclipse 4.5 > (Mars Milestone 4 (4.5.0M4) Build id: 20141217-1924). > > Please at least open a bug report at FS to make sure something happens - at > least some day... > > Best regards, > Thomas Quick Access problem is already addressed in Mars via below bug fix: https://bugs.eclipse.org/bugs/show_bug.cgi?id=457045 We received the confirmation on this fix from Thomas as well: https://bugs.eclipse.org/bugs/show_bug.cgi?id=457045#c8
Hi Niraj, the bugreport you mention is about the Quick ASSIST (Ctrl+1 in a source code editor) popup. This bug is about the Quick ACCESS (Ctrl+3)! Best regards, Thomas
Created attachment 255380 [details] Details of the bug reported against JAWS@freedomscientific (In reply to Thomas Schulze zur Wiesch from comment #9) > Hi Niraj, > > the bugreport you mention is about the Quick ASSIST (Ctrl+1 in a source code > editor) popup. This bug is about the Quick ACCESS (Ctrl+3)! > > Best regards, > Thomas For issue with "Quick ACCESS" problem with JAWS, I have reported the problem against JAWS@freedomscientific. They haven't provided any bug ID for further communication yet.
(In reply to Niraj Modi from comment #10) > For issue with "Quick ACCESS" problem with JAWS, I have reported the problem > against JAWS@freedomscientific. > > They haven't provided any bug ID for further communication yet. Received an email communication from support@freedomscientific.com team: As requested by them, I confirmed that the issue is reproducible with latest JAWS® screen reading software version 16.0 release and latest JRE version 1.8.0_45.
(In reply to Niraj Modi from comment #11) > (In reply to Niraj Modi from comment #10) > > For issue with "Quick ACCESS" problem with JAWS, I have reported the problem > > against JAWS@freedomscientific. > > > > They haven't provided any bug ID for further communication yet. > > Received an email communication from support@freedomscientific.com team: > As requested by them, I confirmed that the issue is reproducible with latest > JAWS® screen reading software version 16.0 release and latest JRE version > 1.8.0_45. As per last communication from freedomscientific, they tested the issue on Win8.1(only) and it was not reproducible for them, hence it's closed from there end. Can someone confirm on this issue using Win8.1 or Win10 with latest JAWS ?
Retested on Win 8.1 with Eclipse Neon and Jaws 17.0.1806. Issue still reproducible (each time, never works on my machine)! Steps to reproduce: 1. Open Eclipse, position cursor in an editor 2. Press Ctrl+3 3. Type "Hel" -> Popup opens with suggestions 4. Press cursor down -> each time you press down, Jaws reads "Hel" -> Entries in list are not read to the user!
(In reply to Thomas Schulze zur Wiesch from comment #13) > Retested on Win 8.1 with Eclipse Neon and Jaws 17.0.1806. > > Issue still reproducible (each time, never works on my machine)! > > Steps to reproduce: > 1. Open Eclipse, position cursor in an editor > 2. Press Ctrl+3 > 3. Type "Hel" -> Popup opens with suggestions > 4. Press cursor down -> each time you press down, Jaws reads "Hel" > -> Entries in list are not read to the user! Thanks for confirming the behavior on Win8.1 Since Jaws support team is not able to reproduce this issue at their end on Win8, so this has to be pursued with JAWS support team again(by re-opening Jaws Esclations Issue: 251400)
(In reply to Niraj Modi from comment #14) > Since Jaws support team is not able to reproduce this issue at their end on > Win8, so this has to be pursued with JAWS support team again(by re-opening > Jaws Esclations Issue: 251400) From SWT end, we are doing the required due-diligence w.r.t. to firing of the Accessibility events. NVDA toolkit interprets & responds to it properly, but JAWS doesn't(more details captured in comment 4). As of now we consider this issue as Not-Eclipse, issue to be discussed and sorted with JAWS/Freedomscientific.
After reporting this issue to Freedomscientific(for exact details of the communication from our end, please refer attachment 255380 [details]) I got below ID for follow up: Jaws Esclations Issue: 251400 [last update I got is captured in comment 12]
