Re: [g-a-devel] Coming to grips with the state of a11y in gtk
- From: Piñeiro <apinheiro igalia com>
- To: liyuan gnome org
- Cc: gnome-accessibility-devel gnome org, danw gnome org, matthias clasen gmail com, gtk-devel-list gnome org
- Subject: Re: [g-a-devel] Coming to grips with the state of a11y in gtk
- Date: Fri, 18 Feb 2011 13:57:48 +0100 (CET)
From: Li Yuan <liyuan gnome org>
> Implementing a11y interface in the widget itself may require a big change in
> as API pointed out. So maybe we can move the gail code into gtk first and do
> further integration later.
Yes, of course, take into account that I added that bug as part of the
"Towards ATK 2.0".
We view this as the opportunity to improve ATK, no matters if we break
the API. And taking into account that the hackfest is scheduled in
May, this will be a long task, and then we would require to update
gail and at-spi2.
In fact, as a outcome of the hackfest, we would require to write a
roadmap for ATK2 and the gail/at-spi2 update. And probably to make
life easier, that would fit more on gtk4. AFAIK, on the gtk hackfest
gtk developers started to create a gtk4 roadmap. In summary:
* gtk1, gtk2, gtk3 => gail implementing atk1
* gtk4 => gail implementing atk2
After this random rant ... yes, if there are resources, the current
gail should be integrated on gtk independently of the new API we are
planning for ATK2.
> On Fri, Feb 18, 2011 at 1:27 AM, Matthias Clasen
> <matthias clasen gmail com>wrote:
>> On Thu, Feb 17, 2011 at 12:23 PM, Piñeiro <apinheiro igalia com> wrote:
>> > So probably we could study that. Anyway, in the same way, right now I
>> > don't see how this would better that the option proposed by Matthias.
>> Oh, I think having the option of implementing the a11y interface in
>> the widget itself would be great for many of the simple cases.
>> For the complex widgets, we'll probably always have separate objects
>> gnome-accessibility-devel mailing list
>> gnome-accessibility-devel gnome org
API (apinheiro igalia com)
] [Thread Prev