Bug 69888 - [Dialog] Message in Selection dialog is not read by JAWS screen reader
Summary: [Dialog] Message in Selection dialog is not read by JAWS screen reader
Status: RESOLVED DUPLICATE of bug 59813
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Carolyn MacLeod CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2004-07-12 20:03 EDT by Ninad Agate CLA
Modified: 2004-08-27 02:49 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ninad Agate CLA 2004-07-12 20:03:22 EDT 
Messages set using org.eclipse.ui.dialogs.SelectionDialogs setMessage method 
are not read by JAWS screen reader. This screen reader can read other text in 
this dialog eg. title , button labels etc.
To reproduce open any dialog that extends the selection dialog (eg. working 
set selection dialog). If you have JAWS screen reader installed you'll notice 
that the message is not read.
Comment 1 Wassim Melhem CLA 2004-07-12 22:20:15 EDT 
Moving to Platform/UI and cc'ing the accessibility king.
Comment 2 Tod Creasey CLA 2004-07-13 08:22:40 EDT 
JAWS is limited in its ability to read dialogs - it can only read the children 
of the shell and needs to be scripted otherwise.

Window Eyes on the other hand can read this dialog without any difficulty - I 
am not convinced that we want to make a change due to the limitations of one 
tool.
Comment 3 Carolyn MacLeod CLA 2004-08-27 02:24:46 EDT 
Taking ownership (for now) and CCing Frank and Lin.
To see this problem, click on the flashlight (Search) tool in the main eclipse 
toolbar, and then under Scope, select the 'Working set' radio button. Now 
click on the Choose... button. The text "Select working sets:" is not read.
Comment 4 Carolyn MacLeod CLA 2004-08-27 02:49:52 EDT 
Oops. This is a duplicate of 59813. Lin, I will cc you on bug 59813 instead. 
Sorry about that.

*** This bug has been marked as a duplicate of 59813 ***