Bug 80570 - [Dialogs] Low Vision test - hover test is not present for icons in MessageDialogs
Summary: [Dialogs] Low Vision test - hover test is not present for icons in MessageDia...
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 3.1 M7   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2004-12-08 23:24 EST by Doug MacDonald CLA
Modified: 2005-05-10 13:53 EDT (History)
1 user (show)

See Also:


Attachments
Patch with new listener (2.45 KB, patch)
2005-05-04 11:33 EDT, Tod Creasey CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Doug MacDonald CLA 2004-12-08 23:24:18 EST
Our testers found that MessageDialog (org.eclipse.jface.dialogs.MessageDialog) 
dialogs do not conform to Low Vision compliance quidelines (T&M 162A). There is 
no hover text for the icons is these dialogs. See below for test case of Low 
Vision Compliance.

High Contrast:  Under Control Panel_accessibility_display tab change to high 
contrast white or yellow on a black background.  This test will remove color 
and render everything on screen in black and white.  These settings are used by 
low vision users who can only see text when there is a high degree of contrast 
between the foreground and background colors, as well as some color blind 
users.  Text must not be illegible, gray, or any other color other than black 
and white (or yellow depending on the settings you chose).  "Bleed through" 
(the text behind a control shows within the control) on any controls or text 
should also be reported.  Check that alt text is present on each icon by using 
the mouse to "hover over" the icon.
Comment 1 Tod Creasey CLA 2005-05-02 08:39:24 EDT
I am not sure what standard you are referring to but it is a standard
accessibility guideline to require that no icon is suffecient for information -
we either have to give text somewhere (which is the title of the message dialog)
and give hover text as a last resort.

In the case of the MessageDialog this is redundant information. Making this a
requirement for all dialogs would be redundant except in cases where there is no
other source of textual information.

We generally use icons as a hint for users but using it as the only source of
information is a bug.
Comment 2 Tod Creasey CLA 2005-05-03 08:11:44 EDT
It is not unreasonable for users of this dialog to expect we would handle the
error, info or warning status so we should fix this for 3.1.
Comment 3 Cori Ryan CLA 2005-05-03 08:33:30 EDT
Just for any other readers of this bug report so they are following what Tod 
and I have been talking about (we are talking about the informational popups 
provided by Eclipse, though a warning / error dialog would have the same 
requirements) ...

Labeling an Icon: Development Techniques
------------------------------------------
Use one or more of the following techniques to meet Checkpoint [n.n] from the 
IBM Software Accessibility Checklist:

* Use the standard Windows tooltip control to apply a label to each image. 
* Use MSAA to programmatically expose the name and description of each label. 
* Place text labels immediately to the left or immediately above the control 
Comment 4 Tod Creasey CLA 2005-05-04 11:33:34 EDT
Created attachment 20688 [details]
Patch with new listener
Comment 5 Tod Creasey CLA 2005-05-04 15:42:58 EDT
Fix released for build >20050504. We now support the 4 image supported in
IconAndMessageDialog but we need a more general solution (with new API) post 3.1.

See Bug 93709 for more details
Comment 6 Tod Creasey CLA 2005-05-10 13:53:15 EDT
Verified in 20050510