Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 40407

Summary:	ColorSelector needs an accessible listener
Product:	[Eclipse Project] Platform	Reporter:	Tod Creasey <Tod_Creasey>
Component:	UI	Assignee:	Tod Creasey <Tod_Creasey>
Status:	VERIFIED FIXED	QA Contact:
Severity:	major
Priority:	P2	CC:	grant_gayed
Version:	3.0	Keywords:	accessibility
Target Milestone:	3.0 M7
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Tod Creasey

2003-07-17 13:28:19 EDT

20030717

We need to add an accessible listener to the ColorSelector so that API that 
uses it correctly (such as GTK) can inform of its value.

Comment 1 Tod Creasey

2003-07-22 15:55:35 EDT

Fixed in build >20030722

Comment 2 Grant Gayed

2004-01-27 11:11:16 EST

Tod, does "so that API that uses it correctly (such as GTK)" imply that win32 
won't use this?  I just tried with WindowEyes and it doesn't say anything 
beyond "focused button".

Comment 3 Tod Creasey

2004-01-27 11:20:02 EST

GTK is supposed to use the accessibility info we provide - we now that 
applications like JAWS don't. What does inspect objects do?

Comment 4 Grant Gayed

2004-01-27 11:47:19 EST

The inspector says:

Name:	"Color Selector"
Value:	none [false]
Role:	push button
State:	normal
Description:	none [false]
Kbshortcut:	none [false]
DefAction:	"Press"
Parent:	"Color Selector":window

It's not reading out "Color Selector" on either windoweyes or gnopernicus, so 
I'll experiment on the gtk front a bit.  Maybe description or value should 
contain the text?

Comment 5 Tod Creasey

2004-02-11 15:25:43 EST

Verified in 20040210