GNOME 3 accessibility:
State of the union

Alejandro Piñeiro Iglesias
apinheiro@igalia.com
Introduction
Accessibility 101

●

Equal access to software & information for all users

●

Modified or alternative interaction and pre...
Why?
●

Right thing to do for us and for our users

●

Required to fulfill accessibility guidelines

●

It increases your ...
“If you’re not accessible, you lose sales and
reputation”
Marco Zehe, accessibility developer

http://www.marcozehe.de/201...
GNOME 3.X
GNOME 3.2
●

Accessibility was still work in progress

●

Improvements at the low level

●

Accessibility bugs in core app...
ATK/AT-SPI2 Hackfest

Photo by Mario Sánchez (License CC BY-SA 2.0)
ATK/AT-SPI2 Hackfest 2012
●

Cross-desktop hackfest

●

Augmented, consistently-implemented accessibility
●

●

Stop to us...
GNOME 3.4
●

First one that Orca users could use GNOME Shell
●

Orca users reporting bugs

●

Orca noticeable more perform...
GNOME 3.4
●

Team still small, but stable

●

Roadmap
●

Performance improvement

●

ATK support improved on GNOME-Shell a...
Demo
GNOME 3.6
●

Brightness, contrast and inversion

●

Focus and caret tracking in GNOME-Shell Magnifier

●

Accessibility al...
GNOME 3.6
●

Team remains small, but high motivation

●

Roadmap:
●

Augmented accessibility

●

BUT: continued lack of AT...
Magnifier features
Accessibility always on
●

Was a setting change, became a library

●

Not an add-on but an add-in

●

For users: It JustWo...
GNOME 3.X: What we need
to succeed
●

No significant core changes

●

Continued present investment in accessibility

●

Ad...
GUADEC 2012 - A11yCamp

Photo by Alberto García (License CC BY-SA 2.0)
GUADEC 2012 - A11yCamp
●

Two day unconference, but with some agenda
●

●

Day2: mostly accessibility team work

●

●

Day...
Relationship with the
community
Old times
●

Usual suspects: just a bunch of people were doing

accessibility work

●

Usual suspects2: just a bunch of pe...
Lately: Awareness
●

Toolkits/module maintainers not only reviewing,

they are also providing accessibility related code

...
Poster boy
Friends of GNOME

“Help make 2012 the Year of Accessibility for
GNOME!”
THANKS!!
A summary?
Conclusions
●

We have a running GNOME accessibility framework

●

We have users and a motivated team

●

All the GNOME co...
Contact and links
●

gnome-accessibility-list at gnome.org

●

gnome-accessibility-devel at gnome.org

●

https://live.gno...
Questions?

Alejandro Piñeiro Iglesias
apinheiro@igalia.com
Upcoming SlideShare
Loading in...5
×

GNOME 3 accessibility: State of the Union (GUADEC 2012)

164

Published on

By Alejandro Piñeiro Iglesias.

When GNOME 3.0 was released in April 2011, it had lots of shine but very little accessibility, despite the best efforts of the GNOME developers. In the year since that release, the GNOME Foundation and the Accessibility Team have been working hard to address these problems and to make GNOME 3 at least as accessible as GNOME 2 -- and hopefully even better.

In April 2012 GNOME 3.4 was released with greatly enhanced accessibility support in GNOME Shell along with improved performance and stability of Orca and other components.

This presentation will provide attendees with:
* A brief introduction to GNOME accessibility
* An explanation of the improvements made since GNOME 3.0
* The status of GNOME 3.4
* The results of the two ATK/AT-SPI2 hackfests
* Our plans for GNOME 3.6 and beyond
* ATK/AT-SPI2 implementations in other free desktop environments

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
164
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

GNOME 3 accessibility: State of the Union (GUADEC 2012)

  1. 1. GNOME 3 accessibility: State of the union Alejandro Piñeiro Iglesias apinheiro@igalia.com
  2. 2. Introduction
  3. 3. Accessibility 101 ● Equal access to software & information for all users ● Modified or alternative interaction and presentation
  4. 4. Why? ● Right thing to do for us and for our users ● Required to fulfill accessibility guidelines ● It increases your user base
  5. 5. “If you’re not accessible, you lose sales and reputation” Marco Zehe, accessibility developer http://www.marcozehe.de/2012/01/16/if-youre-not-accessible-you-lose-sales-and-reputation/
  6. 6. GNOME 3.X
  7. 7. GNOME 3.2 ● Accessibility was still work in progress ● Improvements at the low level ● Accessibility bugs in core applications still present ● Accessibility team small, but regrouping ● Fallback mode was usable, GNOME-Shell not ● Roadmap: Good progress on the 3.0 goals
  8. 8. ATK/AT-SPI2 Hackfest Photo by Mario Sánchez (License CC BY-SA 2.0)
  9. 9. ATK/AT-SPI2 Hackfest 2012 ● Cross-desktop hackfest ● Augmented, consistently-implemented accessibility ● ● Stop to use the bridge as a module/plugin ● ● Best practices guide Debate/prioritize tasks Defined the work to be done for following releases
  10. 10. GNOME 3.4 ● First one that Orca users could use GNOME Shell ● Orca users reporting bugs ● Orca noticeable more performant ● Magnifier configuration dialog added
  11. 11. GNOME 3.4 ● Team still small, but stable ● Roadmap ● Performance improvement ● ATK support improved on GNOME-Shell and toolkits
  12. 12. Demo
  13. 13. GNOME 3.6 ● Brightness, contrast and inversion ● Focus and caret tracking in GNOME-Shell Magnifier ● Accessibility always on
  14. 14. GNOME 3.6 ● Team remains small, but high motivation ● Roadmap: ● Augmented accessibility ● BUT: continued lack of ATs for users with other disabilities ● BUT: some core apps still lack proper support
  15. 15. Magnifier features
  16. 16. Accessibility always on ● Was a setting change, became a library ● Not an add-on but an add-in ● For users: It JustWorks(tm) ● For developers: ● App accessibility gets tested by everyone ● Dragons ahead ● Start testing NOW!
  17. 17. GNOME 3.X: What we need to succeed ● No significant core changes ● Continued present investment in accessibility ● Additional investment: ● Fix current accessibility bugs in core apps ● Prevent future accessibility regressions ● Create and/or port tools for users with other disabilities
  18. 18. GUADEC 2012 - A11yCamp Photo by Alberto García (License CC BY-SA 2.0)
  19. 19. GUADEC 2012 - A11yCamp ● Two day unconference, but with some agenda ● ● Day2: mostly accessibility team work ● ● Day1: mostly cross team collaboration Regardless of your schedule, show up! Where and when? ● Room 2.0a ● Jul 30th (Monday) and Jul 31th (Tuesday)
  20. 20. Relationship with the community
  21. 21. Old times ● Usual suspects: just a bunch of people were doing accessibility work ● Usual suspects2: just a bunch of people were taking care of accessibility status ● Accessibility team was like the “accessibility police”
  22. 22. Lately: Awareness ● Toolkits/module maintainers not only reviewing, they are also providing accessibility related code ● Interest to know how to report accessibility bugs ● Accessibility took into account since the early stages of new features and designs
  23. 23. Poster boy
  24. 24. Friends of GNOME “Help make 2012 the Year of Accessibility for GNOME!”
  25. 25. THANKS!!
  26. 26. A summary?
  27. 27. Conclusions ● We have a running GNOME accessibility framework ● We have users and a motivated team ● All the GNOME community involved ● BUT: Not enough ATs, small team
  28. 28. Contact and links ● gnome-accessibility-list at gnome.org ● gnome-accessibility-devel at gnome.org ● https://live.gnome.org/Accessibility
  29. 29. Questions? Alejandro Piñeiro Iglesias apinheiro@igalia.com
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×