Community
Participate
Working Groups
We have multiple ways of showing error messages in dialogs. I'm wondering if some of these techniques have accessibility problems. For example: - JFace InputDialog uses a read-only text to show error messages, so that users can tab to it and the screen reader will read it - JFace TitleAreaDialog uses the new animated error message for errors and warnings. Is this accessible? (Non-error and warning messages are shown in a read-only text, so I think we are okay there) - SelectionDialog creates a label for its message area - SelectionStatusDialog creates a MessageLine (subclass of CLabel) for its message area - StatusDialog creates a different MessageLine (inner class, still a subclass of CLabel) for its message area So I believe that the selection and status dialogs are not accessible. Not sure about the new animated error dialog. Also not sure if I've covered all the cases, there may be other dialogs with their own message implementation. Also, I don't know if the Eclipse internal dialogs all need to be accessible, or if only API dialogs need to be accessible (so that products built on Eclipse can be accessible). That is, I don't know if Eclipse itself has to be fully compliant.
Assigning this bug to myself, but cc'ing Karice because I'll need some guidance on what we are supposed to do for accessibility.
- JFace InputDialog uses a read-only text to show error messages, so that users can tab to it and the screen reader will read it What is the issue here? - JFace TitleAreaDialog uses the new animated error message for errors and warnings. Is this accessible? (Non-error and warning messages are shown in a read-only text, so I think we are okay there) Yes you can tab to it - SelectionDialog creates a label for its message area Is this a direct child of the shell? If so it is OK - SelectionStatusDialog creates a MessageLine (subclass of CLabel) for its message area - StatusDialog creates a different MessageLine (inner class, still a subclass of CLabel) for its message area These are likely an issue. Susan you should get inspect32 to verify
No issue with InputDialog, I was giving that as an example of our inconsistency. I think the others probably need to be read-only text.
See also bug #78746. If we have an accessible solution for dialogs, and it handles ampersand characters correctly, we could use it as a solution for Bug 78746.
removing milestone. I never got around to doing a cleanup of the different message implementations.
It would be nice to have a common status message area implementation for our dialogs.
Retitling dialog to reflect the issue. There are a number of different complaints/issues regarding our presentation of warning and info messages in dialogs. I will mark them dependent on this bug to tie them all together...
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
