Re: [g-a-devel]RE: (no subject)

[Bill Haneman <bill haneman sun com>]

On Thu, 2003-05-15 at 16:58, Peter Korn wrote:
> Hi guys,
> 
> I'm sorry if I missed this part of the discussion, but... where is the
> gtkhtml widget used, what is it used to render, and for how long will it be
> used (before we move to something else)?

This is the Evolution html widget.  It's also been oft-proposed as the
"official" GNOME HTML widget.

At the moment it's mostly used in Evo, where CSS and DOM are arguably
less important as you point out.  However the lack of CSS and DOM do
limit the range of situations where it could accessibly extend.  It's
unlikely to be superceded anytime soon, given the fact that the Evo team
prefers this widget and has just ported it to GTK+-2.

I think the answer for our "real HTML" needs is gecko, though there are
divergent opinions on this too.

- Bill

> If it is not being used to render web sites in general, but rather a
> restricted set of documents (e.g. help files), then CSS support (and W3C WAI
> UAG support) is a lot less important for accessibility.  Likewise, if this
> widget will soon be superceeded, then "dotting all of the i's and crossing
> all of the t's" is likewise less important.
> 
> Regards,
> 
> Peter Korn
> Sun Accessibility team
> 
> 
> Bill Haneman wrote:
> > 
> > On Thu, 2003-05-15 at 03:32, Gilbert Fang wrote:
> > 
> > > Yes, gtkhtml does not support CSS, but I donot see the essential
> > > relationship between CSS and accessibility.
> > 
> > It's there if you look at the w3c User Agent Guidelines.  We can
> > accomplish a lot without it, but the w3c spec is one that people will be
> > asking about and which may become a requirement in some quarters.
> > 
> > CSS is important for users with various vision problems, both in the
> > sense that we must be able to apply stylesheets via a standard
> > mechanism, and also because we need to be able to get stylesheet info
> > about the DOM (and the DOM too :-( )
> > 
> > So the w3c WAI UAG (user agent guidelines) put a lot of additional
> > requirements on us - at least given our current understanding.  All the
> > implications haven't been worked out yet, but it seems likely that DOM
> > and CSS will both be important to meeting these requirements in the
> > future.
> > 
> > regards,
> > 
> > - Bill
> > 
> > > Now gtkhtml has a testing tool -- "testgtkhtml", and we do use at-poke
> > > get many information of that.  So, I do not think CSS-support is the
> > > prerequisite condition of accessibility.
> > >
> > > And York, how do you think about it?
> > >
> > > Gilbert
> > >
> > >
> > > > Either way work is needed.  Personally I'd rather deal with the gtkhtml2
> > > > codebase, but the Evo guys may not agree ;-)
> > > >
> > > > - Bill
> > > >
> > > > > Luis
> > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Gilbert Fang [mailto:gilbert fang sun com]
> > > > > > > Sent: Monday, May 12, 2003 6:31 PM
> > > > > > > To: Bill Haneman
> > > > > > > Cc: gnome-accessibility-list gnome org;
> > > > > > > gnome-accessibility-devel gnome org
> > > > > > > Subject: (no subject)
> > > > > > >
> > > > > > >
> > > > > > > Hi, Bill
> > > > > > >
> > > > > > > I plan to make the atk implementation of  the Gal and gtkhtml module.
> > > > > > >
> > > > > > > I read the "GNOME Accessibilityf or Developers(CVS draft)". ( I could
> > > > > > > not find it at gnome website now, is it deleted?) . It is said that
> > > > > > > "programs that make sue of GAIL are written as GTK modules".
> > > > > > > And I found
> > > > > > > that the exsting a11y codes of Gal and gtkhtml are built as  modules.
> > > > > > >
> > > > > > > But I found two kind of modules. One is GTK module with its
> > > > > > > init entry.
> > > > > > > And other is as I name it Accessibilty module which has an different
> > > > > > > entry .
> > > > > > >
> > > > > > > The following is from libgnome/gnome-program.c
> > > > > > > ======================================
> > > > > > >  static gboolean
> > > > > > > accessibility_invoke_module (GnomeProgram *program,
> > > > > > >                            const char   *libname,
> > > > > > >                            gboolean      init)
> > > > > > > {
> > > > > > >       GModule    *handle;
> > > > > > >       void      (*invoke_fn) (void);
> > > > > > >       const char *method;
> > > > > > >       gboolean    retval = FALSE;
> > > > > > >       char       *module_name;
> > > > > > >
> > > > > > >       if (init)
> > > > > > >               method = "gnome_accessibility_module_init";
> > > > > > >       else
> > > > > > >               method = "gnome_accessibility_module_shutdown";
> > > > > > >
> > > > > > >       module_name = find_accessibility_module (program, libname);
> > > > > > >
> > > > > > >       if (!module_name) {
> > > > > > >               g_warning ("Accessibility: failed to find
> > > > > > > module '%s' which "
> > > > > > >                          "is needed to make this application
> > > > > > > accessible",
> > > > > > >                          libname);
> > > > > > >
> > > > > > >       } else if (!(handle = g_module_open (module_name,
> > > > > > > G_MODULE_BIND_LAZY)))
> > > > > > > {
> > > > > > >               g_warning ("Accessibility: failed to load
> > > > > > > module '%s': '%s'",
> > > > > > >                          libname, g_module_error ());
> > > > > > >
> > > > > > >       } else if (!g_module_symbol (handle, method, (gpointer
> > > > > > > *)&invoke_fn)) {
> > > > > > >               g_warning ("Accessibility: error library '%s'
> > > > > > > does not include "
> > > > > > >                          "method '%s' required for
> > > > > > > accessibility support",
> > > > > > >                          libname, method);
> > > > > > >               g_module_close (handle);
> > > > > > >
> > > > > > >       } else {
> > > > > > >               retval = TRUE;
> > > > > > >               invoke_fn ();
> > > > > > >       }
> > > > > > >
> > > > > > >       g_free (module_name);
> > > > > > >
> > > > > > >       return retval;
> > > > > > > }
> > > > > > > =================
> > > > > > > It seems the accessibility module should have the
> > > > > > > "gnome_accessibility_module_init" function as the entry function.
> > > > > > >
> > > > > > >
> > > > > > > Then what is the better one? Which way should I do for the future?
> > > > > > >
> > > > > > >
> > > > > > > Thanks a lot.
> > > > > > > Gilbert
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > gnome-accessibility-list mailing list
> > > > > > > gnome-accessibility-list gnome org
> > > > > > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> > > > > > >
> > > > > > _______________________________________________
> > > > > > Gnome-accessibility-devel mailing list
> > > > > > Gnome-accessibility-devel gnome org
> > > > > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > 
> > _______________________________________________
> > gnome-accessibility-list mailing list
> > gnome-accessibility-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list