Re: [g-a-devel]Nautilus menu labels



Long long ago Peter Korn wrote:
...
...
> Do you know what the AccessibleStateSet is for this menu?  (you can check it
> with at-poke)  Objects that are aren't "visible" and "showing" should not be
> rendered to the user via an AT.  If an AT is doing that, it is probably a
> bug.

Actually there are some explicit exceptions, particularly for GOK. 
Since GOK is about providing a high-efficiency interface for users who
can't readily enter keyboard commands, GOK exposes certain kinds of
'hidden' UI elements rather than forcing the user to simulate the
keyboard shortcuts for posting them.  The primary example is menus;
menus are displayed even if they are not posted, as long as they have
state ENABLED.  If an actionable item is 'enabled' then it's advertising
the fact that it in theory can be activated from its present state.

- Bill

> 
> Regards,
> 
> Peter Korn
> Sun Accessibility team
> 
> 
> > On Thu, 2003-07-17 at 18:54, Mario Lang wrote:
> > > Dave Camp <dave ximian com> writes:
> > >
> > > > Hrm, that UI file is only be merged for the desktop window, not the
> > > > normal windows.  Are you seeing this problem for all windows?
> > > No.  I only observe it for the Desktop frame.  Adding label="File" and
> > > so on makes the labels appear again, but I did not verify if this
> > > activates shortcuts.
> > >
> > > > On Thu, 2003-07-17 at 17:19, Mario Lang wrote:
> > > >> HI.  While poking around in AT-SPI I realized that Nautilus is the
> > > >> only app I've found so far which has no names for it's menus.  Actual
> > > >> menu-items and submenus are labeled, but the top menus aren't.
> > > >>
> > > >> I now found that /usr/share/gnome-2.0/ui/nautilus-desktop-icon-view-ui.xml
> > > >> is the reason for this, quoting the file:
> > > >>
> > > >> <menu>
> > > >>         <!-- By re-labelling these submenus to names without underscores, we
> > > >>              prevent the user from bringing up the otherwise-invisible menu bar
> > > >>              menus on the desktop from the keyboard. Setting the labels to "" in
> > > >>              code does not work (presumably Bonobo bug), but doing so here does.
> > > >>         -->
> > > >>         <submenu name="File" label=""/>
> > > >>         <submenu name="Edit" label=""/>
> > > >>         <submenu name="View" label=""/>
> > > >>         <submenu name="Go" label=""/>
> > > >>         <submenu name="Bookmarks" label=""/>
> > > >>         <submenu name="Profiler" label=""/>
> > > >>         <submenu name="Help" label=""/>
> > > >>         <submenu name="Preferences" label=""/>
> > > >> </menu>
> > > >>
> > > >> Now, this looks like bad behaviour from an accessibility standpoint to me.
> > > >>
> > > >> First of all, isn't the comment wrong?  If the intention of this
> > > >> piece of XML is to suppress shortcuts, shouldn't it just really define
> > > >> the label without using _?
> > > >>
> > > >> Like:
> > > >>
> > > >>         <submenu name="File" label="File"/>
> > > >>
> > > >> What do people suggest to deal with such a thing?  I am trying
> > > >> to find my way around about how to help fix accessibility related bugs,
> > > >> so a short intro on how to resolve such issues would be great. File a bug?
> > > >>
> > > >> Or is this actually a valid way of doing things, and the assistive
> > > >> technologies need to obtain menu labels other than calling
> > > >> Accessible_getName?
> > > >
> > 
> > _______________________________________________
> > Gnome-accessibility-devel mailing list
> > Gnome-accessibility-devel gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]