Community
Participate
Working Groups
Build Identifier: M20100211-1343 When focus is given to the button in the top right hand corner of the Preference Dialog page, there is no indication as to what the control could possibly do. JAWS will only announce a toolbar button. Reproducible: Always Steps to Reproduce: 1.Open preference through window -> preferences 2.Tab to the button in the top right hand corner of the preference page 3.JAWS will only announce a toolbar button, no tooltip too.
Created attachment 195626 [details] snap shot of the button
*** This bug has been marked as a duplicate of bug 325899 ***
The fix in Bug 325899 (add tooltip "Menu") may not be sufficient. 1. To have JAWS identify it as a "Menu toolbar button" provides no more information to the blind user. How about use "More navigation actions" for the tooltip? 2. Can we add MSAA name to this button?
Re: comment 3 The problem is that it's in a framework that is used for properties dialogs as well as the preferences dialogs. So whatever name is used needs to be appropriate for all of those uses... unless someone wants to change the framework to allow passing that string in. ;) The framework takes the tooltip string and uses that for the MSAA name string. So this button already does have an MSAA name.
Just curious to know what happens when the user clicks "Key Scrolling" from that button? Seems nothing gets highlighted in the UI.
> what happens when the user clicks "Key Scrolling" - Go to a large-ish preference page, for example, General - Appearance. - Resize the Preferences dialog to be smaller (i.e. as if you were working on a small-screen laptop, or maybe using a very large font). You should see scrollbars. - Now try the Key Scrolling menu item again - left and right arrows scroll the "Appearance" page left and right, up and down arrows scroll up and down.
Hi Carolyn, Thanks for the response. The reason I was asking about the MSAA name is because I thought we can have both the tooltip and MSAA name defined separately, and JAWS will announce MSAA name if we don't want to change the tooltip string. Anyway, according to our Accessibility expert, let JAWS announce "tool bar menu button" is not sufficient for blind user. the proposed string change should be appropriate for both preference and property dialog, but that's just a suggestion. Maybe someone understand this menu better will have better description for it.
At the lowest level (my level... the SWT level) the tooltip and MSAA name are defined separately. However, the Eclipse UI framework (built on top of SWT) doesn't have a way to define either of those strings for this particular button. The framework was designed a long time ago, and it is unlikely that it will be changed to allow setting of either of these strings for this particular menu name. (At least, not for Eclipse 3.7, which is almost shipping). So let's see if there is a better string that fits all cases and is useful for everybody. This menu was originally added because people could not resize the tree or scroll the scrollbars using only the keyboard. So the menu itself is mostly there to improve accessibility. We added the "Menu" tooltip and MSAA name because JAWS originally just said "tool bar button". Now it says "tool bar menu button" which is a lot better. If we want to change this string (i.e. maybe change it to Navigation Menu, so that JAWS says "tool bar navigation menu button") then we need to know if this menu is ever going to be used for anything else. I'm not sure if we know that. For example, the very similar "View Menu" that can be found in a view is called "View Menu" because it can contain just about anything that the view provider wants. So that string needs to remain generic. I am going to stop talking now and let the UI folks on this bug decide whether or not the string "Navigation Menu" (or something similar) is appropriate for this tool item.
Hi Carolyn - If there any update on this issue can u please let us know. Since its a accessibility issue , we are tracking it as high priority issue and like to get it resolved sooner.
It's out of my hands - I do not choose the strings, and I do not own the framework. Reassigning to Oleg, who will be able to give you an update.
We are in RC4 now, see http://www.eclipse.org/eclipse/development/plans/freeze_plan_3_7.php . Only critical changes should go into 3.7 at this point.
This needs to be consistent with the dropdown menu that we have in views. That says View Menu. That implies this should read Dialog Menu, as in general it is to serve the same function as the view menu for a given dialog. That it contains navigation actions is a side effect of what we put there to date. PW
Created attachment 198539 [details] Patch Changing tooltip text to "Additional Dialog Actions".
Patch applied to CVS Head.
