Community
Participate
Working Groups
I'm using an Eclipse Luna SR2 on a Windows7 Enterprise machine, JAWS 18.0.2945 version and I still do not have notifications about error messages (no matter if are in wizards or preference pages). I've checked also the corresponding snippet (Snippet363) and do not seems to work either. It seems to be related with this old bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=248410 and the same as https://bugs.eclipse.org/bugs/show_bug.cgi?id=472938 but on Eclipse Luna.
*** Bug 472938 has been marked as a duplicate of this bug. ***
The bug was originally supposed to be fixed via bug 248410 but then came back. NOTES: 1) The original fix consisted of two fixes (SWT and Platform UI). 2) We need to make sure it's fixed for dialogs and wizards. 3) The bug might depend on the JAWS version. Niraj, please have a look.
Tried with JAWS17.0 on Win7 and steps mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=248410#c0 JAWS was reading the error message 'Source folder name is empty' Also, the Error message field was accessible using both TAB switching and Mouse clicks. Tested with below Eclipse versions: Luna SR2 Build id: 20150219-0600 4.10 Build id: I20181206-0815 4.8 Build id: I20180611-0500 4.2.2 Build id: M20130204-1200 Also tried with Snippet363 with recent 4.10 Eclipse build and it was also fine with JAWS.
C(In reply to Niraj Modi from comment #3) > Tried with JAWS17.0 Could it be a JAWS issue? The bug report is for JAWS 18.0.2945. Can you get hold of that version? Oana, please provide steps that do not work for you and test using https://download.eclipse.org/eclipse/downloads/drops4/R-4.10-201812060815/.
(In reply to Dani Megert from comment #4) > C(In reply to Niraj Modi from comment #3) > > Tried with JAWS17.0 > > Could it be a JAWS issue? The bug report is for JAWS 18.0.2945. Can you get > hold of that version? Configured JAWS 18.0.5038 on my Win10 VM, tested Eclipse 4.10 & Snippet363 and I see the same behavior as JAWS 17.0 as mentioned in comment 3.
(In reply to Dani Megert from comment #4) > C(In reply to Niraj Modi from comment #3) > > Tried with JAWS17.0 > > Could it be a JAWS issue? The bug report is for JAWS 18.0.2945. Can you get > hold of that version? > > Oana, please provide steps that do not work for you and test using > https://download.eclipse.org/eclipse/downloads/drops4/R-4.10-201812060815/. Hi! I just tried to test Snippet363 with following Eclipse versions: Kepler Release Build id: 20130614-0229 Luna (4.4.2) Build id: 20150219-0600 Mars.2 (4.5.2) Build id: 20160218-0600 4.10 Build id: I20181206-0815 On my Win7 VM machine and with JAWS 18.0.5038 and error messages are not read when appears (without accessing them directly by mouse or keyboard). Isn't it this the expected behaviour? Thank you!
Niraj, please have another look.
Mass change, please reset target if you still planning to fix this for 4.11.
Moving out of 4.12
Niraj, this has been moved many times now. Please complete this for M2.
Apart from Snippet363 which is under discussion in this bug, tried Snippet340 which takes a different approach to tell a screen reader about updates to a non-focused descriptive area. Snippet340 seems to give desired result with JAWS18 screen reader. Will try to investigate a fix based on Snippet340 for the scenario mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=248410#c0
Too late for 4.16. Removing target milestone.
(In reply to Niraj Modi from comment #11) > Apart from Snippet363 which is under discussion in this bug, tried > Snippet340 which takes a different approach to tell a screen reader about > updates to a non-focused descriptive area. Snippet340 seems to give desired > result with JAWS18 screen reader. > > Will try to investigate a fix based on Snippet340 for the scenario mentioned > in https://bugs.eclipse.org/bugs/show_bug.cgi?id=248410#c0 Since the Dialog live-region is not on the bottom of the dialog/page, JAWS is not reading out the message/error message. Currently investigating a solution how to make JAWS read the live region when not on bottom of dialog/page.
Created attachment 287294 [details] JAWS unable to read live region when not at the bottom of a dialog. Tested the scenario with JAWS 2021 and NVDA screen readers. Problem is seen only with JAWS, where-as NVDA is able to read out he live-region text correctly. So the current work-around to this problem is to use NVDA screen reader.
Reported bug with JAWS: https://github.com/FreedomScientific/VFO-standards-support/issues/580 Workaround: Use NVDA screen reader.
