Re: [orca-list] What the actual status with GNOME Shell 3.2 accessibility support?

[Janina Sajka <janina rednote net>]

Hi, Attila:

I don't have the latest development news, but what you report is very
much what I've been seeing with gnome-shell 3.2. It seems the only thing
I can do is Alt-F2 and type in the name of some application to run.

The fact that GNOME would release this shell when it's known to have
virtually no working a11y support is highly troubling. It rather
suggests that they don't care about this class of users.

Janina

Hammer Attila writes:
> Hy,
>
> I tryed GNOME Shell 3.2, but I perhaps I using wrong with new GNOME
> Shell with Orca.
> If I press for example Alt+F1 key, I only hear "Owerview" text if I
> remember right, and not see any menu items, for example I impossible
> to access awailable applications.
> If I try mowing panels to use for example activities part and
> navigating panel components with TAB or SHIFT+TAB key, I only hear
> "Panel" text with lot of objects.
> I doing anything wrong? Sorry the possible beginner questions, but I
> not known GNOME shell usage tips and tricks for a11y related, but
> very interesting the new interface.
> I looked GNOME Shell 3.2 version with my Ubuntu Oneiric system,
> perhaps other distributions this type issues is not happening?
> Anybody using GNOME Shell with Orca 3.2?
>
> Usual I using GNOME 3.2 with fallback session, but I need doed some
> customizations, because default the third system menue is not
> accessible with keyboard if I activating main menue with ALT+F1 key
> combination. I deleted the top panel, created a new panel and add
> basic applets and the GNOME main menu applet.
> This change resulted me an one column drowdowned menue, and the
> system menue is full accessible, for example I possible change my
> account related awailibility status, possible shutdown, logout or
> restart the system with general Shutdown and Logout menu items
> related dialogs.
> I prewious reported this problem with GNOME fallback session
> related, but perhaps wrong component, because developers not wrote
> any answer this bugreport related:
> https://bugzilla.gnome.org/show_bug.cgi?id=654224
>
> Have a chance to GNOME developers fix this issue with next 3.4
> release in fallback session?
>
> Attila
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> http://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp

-- 

Janina Sajka,   Phone:  +1.443.300.2200
                sip:janina asterisk rednote net

Chair, Open Accessibility       janina a11y org 
Linux Foundation                http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative    http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)