Re: [g-a-devel] Possible UI freeze break: acccessibility menu in panel

[Piñeiro <apinheiro igalia com>]

From: Luca Ferretti <lferrett gnome org>

> 2011/3/7 Owen Taylor <otaylor redhat com>
> 
>>   - Accessibility needs to be turned on with a logout and log back in
>>     for these to work.
> 
> 
> I remember the initial plan was "a11y turned on by default in GNOME 3"

There are still technical aspects that prevents this, like the bad
performance of of the treeview with a11y enabled when the model is
heavily updated and so on.

Recently, as part of the discussions of the ATK/AT-SPI hackfest, we
started to debate about solutions to try to migitate this:

https://mail.gnome.org/archives/gnome-accessibility-devel/2011-February/msg00037.html

Although what it is clear is that any final solution will not be ready
for GNOME 3.0.

>>   - Caribou doesn't integrate properly with GNOME3; it can't handle the
>>     overview of GNOME Shell, etc. And doesn't match the design we want
>>     https://live.gnome.org/GnomeShell/Design/Whiteboards/ScreenKeyboard
> 
> 
> Not sure about it (while I haven't tested caribou lately). An "assistive
> tool for mobility impaired people" and a "keyboard on screen" are not the
> same thing. Do you remember GOK? It is a powerful a11y tool, that allows you
> to entry text, focus windows, select menu entries and toolbar items even if
> the only action you can perform is push a switch[1]. And it was poorly
> (visually) integrated in GNOME 2[2]. If integration means to simply have
> a stylish keyboard for tablet, I've to disagree.

As I said in other mail, I agree here. Right now Caribou is a
assistive technology and not the integrated keyboard on screen for
gnome shell. See the Overview here:

http://live.gnome.org/Caribou

BR

===
API (apinheiro igalia com)