| Summary: | content of tree view (projects and folders) to export to a jar is not read by some screen readers | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Sérgio Neves <sergionevess> | ||||
| Component: | UI | Assignee: | Markus Keller <markus.kell.r> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | carolynmacleod4 | ||||
| Version: | 3.7 | Keywords: | accessibility | ||||
| Target Milestone: | 3.7 M2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Sérgio Neves
Carolyn, can you advise? If this is a matter of the client code having to do something specific, then please punt back to us. Moving to JDT UI. The problem is the following 2 lines of code in method org.eclipse.jdt.internal.ui.jarpackager.JarPackageWizardPage.createInputGroup(): SWTUtil.setAccessibilityText(fInputGroup.getTree(), JarPackagerMessages.JarPackageWizardPage_tree_accessibility_message); SWTUtil.setAccessibilityText(fInputGroup.getTable(), JarPackagerMessages.JarPackageWizardPage_table_accessibility_message); When the accessible name is set for the entire Table (or the entire Tree) then that is what is answered for every TableItem and TreeItem. :) Here is an SWT snippet that shows approximately what should be done for tables and trees in the getName method: http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet291.java Please make sure that there are no other Tables, Trees, or Lists that set the accessible name for the entire control without considering the individual items. This would hold for TabFolder, too, or any control with items, although I am sure that Table, Tree, and List are the most likely to have accessible names explicitly set. Created attachment 177633 [details]
Fix
Thanks for the investigation. I've fixed this problem and a similar problem I found in the warning dialog shown by refactorings. I found no other culprits in the SDK.
Fixed in HEAD. |