[Sugar-devel] [laptop-accessibility] screenreader for sugar

[Tomeu Vizoso]

On Tue, Aug 30, 2011 at 15:51, Esteban Arias <earias at plan.ceibal.edu.uy> wrote:
> What should we change in sugar?

See these:

http://library.gnome.org/users/gnome-access-guide/stable/
http://library.gnome.org/devel/accessibility-devel-guide/stable/

Regards,

Tomeu

> 2010/9/8 Tomeu Vizoso <tomeu at sugarlabs.org>
>>
>> On Tue, Sep 7, 2010 at 18:32, Peter Korn <peter.korn at oracle.com> wrote:
>> >
>> > Hi Tomeu, gang,
>> >
>> > [I'm cc-ing Joanie Diggs, co-maintainer of Orca]
>> >
>> > I believe there are 6 key things that need to be done in/for Sugar to
>> > enable use of the GNOME accessibility work for folks with vision
>> > impairments.  Others more expert in the specific details may correct/amend
>> > my comments.  I believe the 6 things are:
>> >
>> > The shift of AT-SPI from CORBA to DBUS (in process, not yet completed,
>> > but builds of at-spi2 are in the GNOME code repository and if someone would
>> > start playing and testing with it on the OLPC, that'd be great!)
>>
>> I tested the very recent bits of at-spi2 in sugar-jhbuild and they
>> seemed to work fine in that accerciser was able to navigate through
>> the controls of the desktop window and of activities (applications).
>>
>> > Implementation of ATK by the Sugar UI components (this is the
>> > accessibility API that screen readers like Orca use)
>>
>> Accerciser showed that it could not go into the HippoCanvas widget
>> that is used in some fundamental parts of the Sugar shell and also
>> inside our browser. The browser is moving from xulrunner to webkitgtk+
>> which I expect to fare much better there. About HippoCanvas, I have
>> been experimenting with replacing it with custom GtkContainers and
>> dropping Hippo completely seemed very doable.
>>
>> > Creating / adapting a magnifier service on Sugar for Orca.  This may be
>> > a fairly trivial port of gnome-mag (non-COMPOSITE edition), or it may be a
>> > complete re-write
>>
>> I have no idea of what this entails, but as we have kept quite close
>> to GNOME's architecture, I expect the fairly trivial port to suffice.
>>
>> > Porting Orca to Sugar.  This may be fairly trivial, or it may involve a
>> > new Sugar-style GUI, etc.
>>
>> Tried out Orca in Sugar and it was able to read windows titles,
>> buttons labels, etc. What GUI would it have other than a configuration
>> parameter for starting it automatically at startup?
>>
>> > Adding theme support go Sugar for vision impairments - things like a
>> > large-print theme, and inverse theme, etc.
>>
>> The Uruguayan deployment has customized their builds in this direction
>> but I believe they need help upstreaming it.
>>
>> > Ensure 100% keyboard operability of Sugar
>>
>> Hippo is also the roadblock here.
>>
>> > Tomeu - are there folks in sugar-devel who have cycles to work on these
>> > things?
>>
>> No idea, I started this thread to find out :)
>>
>> Thanks a lot for the great insights!
>>
>> Tomeu
>>
>> >
>> > Regards,
>> >
>> >
>> > Peter
>> >
>> > On 9/7/2010 12:49 AM, Tomeu Vizoso wrote:
>> >
>> > On Mon, Sep 6, 2010 at 20:15, Esteban Arias <earias at plan.ceibal.edu.uy>
>> > wrote:
>> >
>> >
>> > no, I tested with gnome desktop.
>> >
>> >
>> > Ok, I can help you get in touch with the GNOME team that works on
>> > accessibility if you want. They are very dedicated, friendly and
>> > talented bunch. Collabora and other companies also provide services
>> > related to accessibility and GNOME.
>> >
>> > But nobody else than us is going to fix accessibility in Sugar so
>> > that's why I'm asking if anybody here has interest in working on this.
>> > The first need is finding someone who can tell us what needs to be
>> > improved in Sugar so it can be used by people with no or very low
>> > vision.
>> >
>> > Thanks,
>> >
>> > Tomeu
>> >
>> >
>> >
>> > 2010/9/3 Tomeu Vizoso <tomeu at sugarlabs.org>
>> >
>> >
>> > On Thu, Sep 2, 2010 at 18:25, Esteban Arias <earias at plan.ceibal.edu.uy>
>> > wrote:
>> >
>> >
>> > xo-1.0 | F11 | Dextrose version | Gnome desktop | orca 2.26.3
>> >
>> > If I set: "run at startup"
>> > orca run correctly.
>> >
>> >
>> > Hi Esteban,
>> >
>> > to clarify, you configure orca in some way so it runs when sugar
>> > starts up and it reads what is on the screen?
>> >
>> > Thanks,
>> >
>> > Tomeu
>> >
>> >
>> >
>> > If I excecute "orca" from Terminal, shows error:
>> > /usr/lib/python2.6/site-packages/orca/mouse_review.py:189: Warning:
>> > invalid
>> > uninstantiatable type `(null)' in cast to `GdkDisplayX11'
>> >     self._mouseDwellTimeout(event.detail1, event.detail2)
>> >
>> > Displays Preferences dialog, but dont reads screen.
>> >
>> > Regards,
>> > Esteban Arias.
>> >
>> > 2010/9/2 Tomeu Vizoso <tomeu at sugarlabs.org>
>> >
>> >
>> > On Wed, Sep 1, 2010 at 14:51, Esteban Arias <earias at plan.ceibal.edu.uy>
>> > wrote:
>> >
>> >
>> > I install orca on xo 1.0 with gnome for f11.
>> > If I config to start session with orca, runs ok. But if I execute
>> > orca
>> > from
>> > terminal, dont run correctly:
>> >
>> >
>> > Hi Esteban,
>> >
>> > could be that your email arrived to us incomplete?
>> >
>> > Regards,
>> >
>> > Tomeu
>> >
>> >
>> >
>> > 2010/9/1 pbrobinson at gmail.com <pbrobinson at gmail.com>
>> >
>> >
>> > On Wed, Sep 1, 2010 at 10:24 AM, Tomeu Vizoso <tomeu at sugarlabs.org>
>> > wrote:
>> >
>> >
>> > On Fri, Aug 20, 2010 at 14:10, Tomeu Vizoso <tomeu at sugarlabs.org>
>> > wrote:
>> >
>> >
>> > On Fri, Aug 20, 2010 at 14:08, Esteban Arias
>> > <earias at plan.ceibal.edu.uy> wrote:
>> >
>> >
>> > hi,
>> > we can colaborate with this proyect.
>> >
>> >
>> > Excelent, have you tried already orca with Sugar? And with GNOME?
>> >
>> >
>> > I would say that the next step is for someone who knows how orca
>> > is
>> > used to give it a try and file tickets for the biggest issues. Not
>> > sure we can make much more until then.
>> >
>> >
>> > The gnome guys mentioned this the other day and there's going to be
>> > some more work done within gnome hopefully for F-14. So hopefully we
>> > should be looking better for that release.
>> >
>> > Peter
>> >
>> >
>> > --
>> >     Esteban Arias
>> >     Investigación y Desarrollo - Plan Ceibal
>> >     Avda. Italia 6201
>> >     Montevideo - Uruguay.
>> >     Tel.: 2601.57.73 Interno 2228
>> >     E-mail : earias at plan.ceibal.edu.uy
>> >
>> >
>> >
>> >
>> > --
>> >     Esteban Arias
>> >     Investigación y Desarrollo - Plan Ceibal
>> >     Avda. Italia 6201
>> >     Montevideo - Uruguay.
>> >     Tel.: 2601.57.73 Interno 2228
>> >     E-mail : earias at plan.ceibal.edu.uy
>> >
>> >
>> >
>> >
>> > --
>> >     Esteban Arias
>> >     Investigación y Desarrollo - Plan Ceibal
>> >     Avda. Italia 6201
>> >     Montevideo - Uruguay.
>> >     Tel.: 2601.57.73 Interno 2228
>> >     E-mail : earias at plan.ceibal.edu.uy
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > accessibility mailing list
>> > accessibility at lists.laptop.org
>> > http://lists.laptop.org/listinfo/accessibility
>> >
>> >
>> > --
>> >
>> > Peter Korn | Accessibility Principal
>> > Phone: +1 650 5069522
>> > 500 Oracle Parkway | Redwood City, CA 94065
>> > Oracle is committed to developing practices and products that help
>> > protect the environment
>> > _______________________________________________
>> > accessibility mailing list
>> > accessibility at lists.laptop.org
>> > http://lists.laptop.org/listinfo/accessibility
>> >
>
>
>
> --
>     Esteban Arias
>     Investigación y Desarrollo - Centro Ceibal para el Apoyo a la Educación
> de la Niñez y la Adolescencia - Plan Ceibal
>     Avda. Italia 6201 - Edificio Los Ceibos
>     Montevideo - Uruguay.
>     Tel.: 2601.57.73 Interno 2228
>     E-mail : earias at plan.ceibal.edu.uy
>
>