Todays UDS session

[Alan Bell]

Hi all,

One of todays sessions at UDS was on improving accessibility development 
and information, the raw notes from the session are included below and 
outline the themes that were discussed. We will be refining these into 
goals for the Natty cycle, but the key points seem to be an effort to 
get accessibility testing into the existing QA frameworks so nothing 
goes out of the door until it passes the accessibility tests and 
providing more information to developers so that accessibility is baked 
in to the code from the beginning. Luke Yelavich will be working 
primarily on Unity and perhaps the installer this cycle and Penelope 
will be liaising with the Gnome upstream on accessibility issues. This 
is an important cycle for accessibility and we have had strong words of 
support from Mark Shuttleworth in the keynote speech of UDS. We need to 
build on that and make Ubuntu awesome for everyone.

Tomorrows schedule is here: http://summit.ubuntu.com/uds-n/2010-10-27/
it would be great to have people raising the issue of accessibility 
either on-site or remotely via IRC in
some of the touch sessions that are on all over the place
Your guide to styling for Ubuntu at 09:00 in Bonaire 1
Improving the desktop testing program at 12:00 in Antigua 4
Ubuntu.com community on ramp at 15:00 in Bonaire 7
Public Certification Website improvements at 15:00 in Bonaire 2
Natty LoCo directory plans at 15:00 in Antigua 2
a11y support for unity at 16:15 in Antigua 2
Unity test framework at 17:10 in Bonaire 7

and also in any other sessions that sound interesting to you!

Alan.

Involving QA in Accessibility
http://qa.ubuntu.com/testing/

Install and use with no screen
Install and use with no mouse
Install and use with no keyboard (on screen keyboard)

plugging in Accessibility into the existing testing frameworks

On screen keyboards can use accessibility frameworks to operate the user 
interface

The installer ubiquity using the webkit framework is a problem as the 
integration with accessibility frameworks is not complete

Review the accessibility profiles
revise or split up further the profiles (options in the installer?)

Unity currently does not support themeing so a low vision profile can't 
be implemented

Accessibility frameworks are used for automated testing

Penelope will be liaising between the Unity/Ubuntu team and the Gnome 
team on accessibility issues.

gnome-accessibility-list at gnome.org
ubuntu-accessibility at lists.ubuntu.com
ubuntu-accessibility-devel at lists.ubuntu.com

Suggestion: Make accessibility visible on developer.ubuntu.com


Multitouch accessibility

Action item: Let people know when accessibility is ready for testing by 
sending an email to the mailing list (TheMuso)


This cycle is make or break for Ubuntu and Accessibility, it is a great 
opportunity for all to be at the core of the development effort of Unity.

Set up an accessibility blog for the team with multiple authors

Ubuntu Accessibility Team page: https://wiki.ubuntu.com/Accessibility/Team
Action item: cprofitt to involve the beginner to be aware of the ubuntu 
accessibility team.