Hello!
Giuseppe Penone has written on Friday, 6 September, at 23:25:
>On Fri, Sep 6, 2013 at 2:17 AM, Andrej N. Gritsenko <and...@rep.kiev.ua>wrote:
>> If you have some time and desire it would be very wonderful if you
>> could make lxpanel accessible, a lot of blind people constantly asking
>> for this. If you need hints then just ask, it is not so hard. :)
>I will not have a lot of free time in the next weeks but anyway if you give
>me an idea about what work should be done (I have really no idea) I will
>see what I can do.
Well, there is a lot of docs around, short one is on KDE developers
site - http://accessibility.kde.org/developer/atk.php, and detailed one
is on GNOME site - https://developer.gnome.org/accessibility-devel-guide
Those docs still aren't simple to follow. So below is step-by-step rules
how to implement it.
1) If the application contains no custom widgets but only standard ones
then developer should satisfy GNOME guide, no implementation is required.
2) If the application introduces own widget but widget does not add any
elements user may interact with but contains some standard GTK widgets,
then improvement for accessibility means widget should receive correct
description and role. I may be wrong on this though and description and
role still may be hidden until ATK widget is implemented but I cannot
check this. Well, contained widgets will interact with user in any case.
3) Otherwise widget should implement some ATK functions. Let see them
more detailed what should be implemented:
a) any accessible GTK widget should contain "mirror" ATK widget, link
between them is established via ATK registry;
b) most of widgets contains some elements, each of those elements should
be represented as instance of AtkObject-derived class;
c) relations between widget and its elements, as well as relations with
screen, should be implemented as AtkComponent interface calls;
d) widget that contains some image to present to user should implement
the AtkImage interface calls to describe image to blind people;
e) widget that contains some complex or editable text should implement
the AtkText interface calls to represent that text;
f) widget that handles user input (keyboard or mouse) should implement
the AtkAction interface calls to receive input from ATK too;
g) widget that handles selection should implement the AtkSelection
interface calls so ATK can receive and change selection.
You can also look into any existing implementations, they will show
you many things, as they did to me.
>Cheers,
>Giuseppe.
Cheers!
Andriy.
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
