Re: [g-a-devel]Accessibility for GnomeCharmap

["Padraig O'Briain" <Padraig Obriain sun com>]

> 
> Hi Padriag,
> Thanks for the suggestion.
> The GnomeStatusBar is part of the libgnomeui and I suppose that it will be
> accessible once libgnomeui is
> made accessible.
> Also, one thing which I have noticed  in the GCharmap application is that the
> status bar gets updated with
> the character and character code only when the mouse moves over the character
> buttons. No information
> is available on the status bar when the character buttons are navigated using 
the
> keyboard only.
> Should this be fixed ???

Yes. It sounds like the status bar ought to be updated when a button receives a 
focus_in_event and a focus_out_event.

Padraig

> 
> Thanks and Regards
> Muktha
> 
> Padraig O'Briain wrote:
> 
> > Muktha,
> >
> > My preference would be to implement an AtkObject for GnomeStatusBar in a 
similar
> > way as is done in gail/gailstatusbar.c for GtkStatusbar. One reason for this 
is
> > that I believe that this accessible object will be useful in other 
applications.
> >
> > If we do this I do not see the need for tooltips for the character buttons.
> >
> > Padraig
> >
> > >
> > > Padraig,
> > >
> > > I assume you've seen this app and might have a better idea what makes 
sense
> > > here, can you make a recommendation to Muktha on this?
> > >
> > > Thanks,
> > >
> > > Marc
> > >
> > > At 11:10 AM 2/20/2002 +0530, muktha wrote:
> > > >Hi ,
> > > >
> > > >Will you please let me know if I should go ahead and provide the tooltips
> > > >for the
> > > >character buttons.
> > > >
> > > >
> > > >Thanks and Regards
> > > >Muktha
> > > >
> > > >Marc Mulcahy wrote:
> > > >
> > > > > If we take Padraig's approach, and make an AtkObject for 
GnomeStatusBar
> > > > > with a role of ATK_ROLE_STATUSBAR then we wouldn't necesssarily have 
to
> > add
> > > > > tooltips to all the buttons.   We could rely on the assistive 
technology
> > to
> > > > > do the right thing and read status bar changes.  As Padraig suggests, 
the
> > > > > text is available now without any modifications, but it is not obvious 
to
> > > > > an assistive technology that the text is contained in a statusbar.
> > > > >
> > > > > Marc
> > > > >
> > > > > At 01:53 PM 2/18/2002 +0000, Padraig O'Briain wrote:
> > > > > >Hi,
> > > > > >
> > > > > >I would regard the gnome status bar (GnomeAppBar) as either 
accessible or
> > > > > >easy
> > > > > >to make accessible. In general, if not in this application, there 
will
> > > > > >probably
> > > > > >be a requirement for GnomeAppBar to be accessible. The GnomeAppBar 
has a
> > > > > >child
> > > > > >(GtkFrame) which has a child which is a GtkLabel. The text of the
> > > > GrkLabel is
> > > > > >the text which is displayed in the status bar.
> > > > > >
> > > > > >One might consider implementing accessibility for GnomeAppBar in a
> > similar
> > > > > >way
> > > > > >as for GtkStatus, i.e. set role to ATK_ROLE_STATUSBAR, report no
> > > > children and
> > > > > >its name as the text on the label; when the text on the label changes
> > > > > >report a
> > > > > >change in accessible-name.
> > > > > >
> > > > > >As you suggest, you could specify the text which appears in the 
status
> > bar
> > > > > >for a
> > > > > >button as the tooltip for the button. This will increase the size of 
the
> > > > > >application as a tooltip must be stored for each button.
> > > > > >
> > > > > >Padraig
> > > > > >
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > The status bar used in gcharmap is the gnome status bar and not
> > > > > > GtkStatusbar
> > > > > > > and hence it is not
> > > > > > > accessible  as of now. As the mouse moves on the character 
buttons,
> > the
> > > > > > > character as well as the
> > > > > > > character code appears on the status bar. Presently, the character
> > > > > > buttons do
> > > > > > > not have any tooltips.
> > > > > > > So, instead of just giving the characters as the tooltip to the
> > > > character
> > > > > > > buttons I thought that I could give
> > > > > > > the information(which includes the character code) that appears on 
the
> > > > > > status
> > > > > > > bar as a tooltip to the character buttons.
> > > > > > >
> > > > > > > Would like to know your opinion regarding this.
> > > > > > >
> > > > > > > Thanks and regards
> > > > > > > Muktha
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Marc Mulcahy wrote:
> > > > > > >
> > > > > > > > Hi Muktha,
> > > > > > > >
> > > > > > > > Why is the status bar not accessible?  Otherwise, your proposal
> > > > > > sounds good.
> > > > > > > >
> > > > > > > > Marc
> > > > > > > >
> > > > > _______________________________________________
> > > > > Gnome-accessibility-devel mailing list
> > > > > Gnome-accessibility-devel gnome org
> > > > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
> > > >
> > > >**************************Disclaimer************************************
> > > >
> > > >Information contained in this E-MAIL being proprietary to Wipro Limited
> > > >is 'privileged' and 'confidential' and intended for use only by the
> > > >individual or entity to which it is addressed. You are notified that any
> > > >use, copying or dissemination of the information contained in the E-MAIL
> > > >in any manner whatsoever is strictly prohibited.
> > > >
> > > >
> > > >  ********************************************************************
> > >
> > > _______________________________________________
> > > Gnome-accessibility-devel mailing list
> > > Gnome-accessibility-devel gnome org
> > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
>