Bug 204657 - [Presentations] [Accessibility] View Menu drop down buttons don't have accessible name in RCP applications
Summary: [Presentations] [Accessibility] View Menu drop down buttons don't have access...
Status: RESOLVED DUPLICATE of bug 160543
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.4   Edit
Assignee: Eric Moffatt CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2007-09-26 05:07 EDT by Romain Deltour CLA
Modified: 2008-05-09 14:21 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Romain Deltour CLA 2007-09-26 05:07:11 EDT
Build ID: I20070621-1340

The triangle drop down button used to access a view menu in the default presentation does not have an accessible name.

You can see this using a screen reader or inspect32.


More information:
The problem seems to come from org.eclipse.ui.internal.presentations.util.AbstractTabFolder implementations (such as org.eclipse.ui.internal.presentations.r33.DefaultTabFolder) where the pull-down button is constructed without a name or an  AccesibleListener.

A temporary workaround is to provide a custom presentation factory extending the internal WorkbenchPresentationFactory and setting an AccessibleListener in the createViewPresentation factory method.
Comment 1 Romain Deltour CLA 2007-09-26 05:17:02 EDT
It seems to be duplicating part of <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=160543">bug #160543</a>, but it seems it's not fixed or should be reopened.

At least it doesn't work on:
Version: 3.3.0
Build id: I20070621-1340

and on RCP apps built from this platform.
Comment 2 Eric Moffatt CLA 2007-09-28 15:24:47 EDT
I'll check with SWT as to whether the listener should be added directly in SWT or whether the platform UI should be adding it...
Comment 3 Eric Moffatt CLA 2008-05-09 14:21:02 EDT


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