GNOME 3.0 Accessibility: State of the Union (Desktop Summit 2011)

  • 74 views
Uploaded on

By Alejandro Piñeiro. …

By Alejandro Piñeiro.

In GNOME, accessibility is a core value that touches all aspects of the system.

From the infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days. As a result, GNOME 2.0 not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work.

This year (2011) was released GNOME 3.0, the first major release of GNOME since GNOME 2.0 on 2002.

As a major relase GNOME 3.0 involves several changes on the technology layers of GNOME affecting the accessibility support in several aspects. Some examples: bonobo deprecation, new desktop (GNOME Shell) using a new technology (Clutter), etc.

Since the annoucement of GNOME 3.0 and those technologies changes the accessibility community was working in order to get the best support on this major release, including two accessibility hackfests during 2010.

In general, the purpose of this presentation is:

Introduce accessibility on GNOME.
Briefly explain the technologies changes between GNOME 2.0 and GNOME 3.0
How this affects accessibility support?
Community reaction?
Briefly explain the status of GNOME 3.0
What works?
What doesn't works?
Plans towards GNOME 3.2

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
74
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
3
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. GNOME 3.0 Accessibility: State of the Union Alejandro Piñeiro (apinheiro@igalia.com)
  • 2. Let's introduce it ...
  • 3. Accessibility? ● Means helping people with disabilities to participate in any life activity ● Like computer stuff. That involves ● … programmatic access ● … keyboard navigation ● … themes
  • 4. AT ? ● AT == Assistive Technologie ● Screen readers ● On screen keyboards ● Magnifiers ● Ok
  • 5. what needs an AT ? ● Know which apps are running ● Know the active app ● Know the focus object ● Be able to interact with the app
  • 6. AT-SPI ? ● “Assistive Technologie Service Provider Interface” ● Daemon providing the functionality that requires those ATs ● “out of the process” ● Using CORBA/bonobo on the old times
  • 7. And the apps? ● How they expose the data? ● Direct CORBA calls to AT-SPI? ● It would be doing stuff really similar … ● But apps are heterogeneous ...
  • 8. ATK ● ATK = Accessibility ToolKit ● Common interface ● The atk-bridge uses ATK calls to know that to expose to AT-SPI ● Toolkits and apps implement ATK ● “in process”
  • 9. How this stuff was implemented? ● Not in time for GNOME 2.X ● Isolated on runtime loadable modules ● At-spi provided at-bridge ● Gail provided an ATK implementation ● Isolated since the beginning ● Extension and access to private data nightmares
  • 10. That old GNOME 2.0
  • 11. Stories from the past Bill Haneman, March Mulhany, GUADEC 2004: “Where we are today” ● ● ● ● 8 critical bugs, ~50 serious bugs Assessment: ● 2.6 : Can be made to work, with some effort ● Need some HEAD components for better results ● 2.8 : Reasonable level of functionality “out of the box” : (still at risk) ● GOAL: disabled users can do all key tasks ● Depends on regression control and attention by packagers, community
  • 12. GNOME 3.0 is coming! (First introduced at Istanbul 2008)
  • 13. Changes, changes! ● CORBA is dead, long live DBUS ● AT-SPI (major piece) CORBA based ● Nokia fund initial move on 2008 ● Gsettings VS GConf ● Desktops: GNOME Shell, Unity ● Clutter, Gtk3 ● CSUN 2010 Accessibility Summit
  • 14. Hey, why so serious? ● We worked to get the a11y pieces on GNOME 2.0 Why just keep sync with GNOME 3.0 is so ● a big problem … ? ● Lets talk about that later ...
  • 15. GNOME 3.0 is here! (April 2011)
  • 16. GNOME 3.0.1 improved ● A11y community started to use a testing distro based on Frederic Crozat one ● Major functionality issues were solved ● GNOME “classic” is still the solution for a11y users
  • 17. So, what we have here? ● Infrastructure: ATK, AT-SPI Toolkit implementations: GAIL, Cally, Java ● Apps: LibreOffice ● Ats: Orca, Caribou, GNOME Voice Control, ● VEDICS, Dasher, OpenGazer, MouseTrap ● A lot of things, right?
  • 18. Really? ● At-spi just ported, no new features ● ATK still 1.0 after 10 years. ● Less than 5 commits in last two years for GVC, Dasher, MouseTrap, etc
  • 19. What we really have? ● Infrastructure requires to be updated ● Some first citizens: Orca, Caribou, GNOME Shell built-in magnification ● Several Ats on their own ● Whats the difference? difference ● Orca has a real community behind
  • 20. Some history – good times ● 16 Oct 2000, “GNOME Accessibility Summit” ● ● ● Sun, IBM and others joined the party A11y had a really big push A lot of new stuff between 2000-2005: ● ATK, AT-SPI, GAIL, Gnopernicus, LSR,
  • 21. Some history – bad times ● 1 Jun 2007, IBM “change strategies” ● ● LSR dies, Orca survives 27 Jan 2010, Sun is acquired by Oracle ● Sun decreasing workforce is mostly removed ● Willie Walker stops to be a11y leader and Orca co-maintainer
  • 22. First conclusion? ● If GNOME a11y wants to survive requires to maintain a healthy community ● But a11y applies to all GNOME. ● Why “GNOME a11y”?, why not “GNOME”? ● And talking about that ….
  • 23. That mail … ● 2011-06-01 <snip> >From my perspective, the a11y team is far too happy to be inits own little corner, working on its 'testing distro' and its own little tools that need to work on every OS and thus end up working properly on none of them. Yet, when I try to run accerciser in a jhbuild tree on my system, it locks up solid after a few minutes every single Time... <snip>
  • 24. A11y had opposite feeling ● Some IRC examples: Jan 22 21:31:37 <anonymous> API: aha...yeah. We need support for users who don't use the mouse at all. Jan 22 21:32:14 <anonymous> Seems as though that would just be a fundamental thing to build in Jan 22 21:35:08 <anonymous> As we all know, designing for a11y helps *everyone*, not just stupid disabled chumps that nobody cares about. Jan 22 21:38:35 <anonymous> API - heh - just joshing. I wasn't poking at you. I was poking at mainstream developers who haven't embraced accessible design yet. Jan 22 21:39:33 <API> yeah, I supposed that, but sometimes there are some strange situations Jan 22 21:40:06 <API> for example, at Boston, there are some presentations, and then the time of the "complainers from ally"
  • 25. Communication breakdown ● A11y “folks” thing that the others prefer them to be isolated, and the others thinks that they are happy with that … ● Other extract from “that mail”: “I think that we have to be honest about the fact that a11y is not a first-class feature of GNOME until it is fully integrated” .
  • 26. Current work and future
  • 27. ATK/AT-SPI2 Hackfest ● Analysis of current status and future ● A lot of things to do now on ATK2 ● A lot of things would require an API breakage
  • 28. ATK/AT-SPI2 Hackfest (2) ● A lot of ATK implementors to be updated ● ● Clutter ● LibreOffice ● Unity ● ● GTK Etc. AT-SPI2 would also require some changes
  • 29. GailEctomy ● Benjamin Otte and Matthias Clasen are merging GAIL and GTK ● First Benjamin conclusions about ATK were really more radical ;)
  • 30. Performance and stability ● Target: being able to have a11y running by default without affecting performance and stability ● Mike Gorse working on that, made some changes ● Require to measure the changes
  • 31. GNOME Shell ● Awesome built-in Magnifier ● ● by Joseph Scheuhammer On screen keyboard based on Caribou ● by Nohemi Fernandez GNOME 3.0 included some ATK patches ● ● Still not really usable with Orca ● Work in progress
  • 32. A summary?
  • 33. Current status
  • 34. Current status ● An accessibility framework ● Bad: Not enough ATs or people ● ● Bus factor of one in several cases Good: GTK+ developers are taking care of GAIL ● What we need: improve the base, more ATs, more people
  • 35. Questions?