Re: Accessibility and Documentation

[Bill Haneman <Bill Haneman Sun COM>]

It should be fairly straightforward to do this - at least, if the
accessibility information is useful and correct.

The bounding boxes of containers like "panels" (you call them 'nodes'),
"toolbars", and areas like the "timeline" in your example can be
obtained from the AT-SPI Accessibility::Component interface.  The
names/labels for those boxes can be obtained from the
Accessibility::Accessible::name property, or the Accessibility::Role of
the objects if they don't have names.  You can also get descriptions for
relevant objects.  The above information is already localized (if the
user interface has been properly translated in the .po files), so this
should speed translation of manuals as well.  Of course some tweaking
will probably be required in the real world, but it will have the
helpful side-effect of identifying gaps in the accessibility
information.

This sounds like a great, fun project.

Best regards,

Bill



On Wed, 2006-03-22 at 11:55, Sven Herzberg wrote:
> Hi all,
> 
>   I'd like to know whether it is possible to abuse the GNOME
> accessibility framework to automatically create annotated window
> screenshots [1].
> 
>   It would be great if we could make screenshot creation for
> documentation an automated task so it's easier for translators to get
> their documentation right, complete and fully localized.
> 
> [1] like http://www.k-3d.org/wiki/Image:Ngui_overview.png
> 
> Regards,
>   Sven
> 
> PS: Please CC me as I'm not subscribed to the list.
> 
> _______________________________________________
> gnome-accessibility-list mailing list
> gnome-accessibility-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list