[Blueprint community-q-accessibility-community-team-plans] Accessibility Community Team Plans

[Penelope Stowe]

Blueprint changed by Penelope Stowe:

Whiteboard changed:
- Things that we need to look at and decide where the focus needs to be:
+ Precise release has significant improvements, particularly with accessible strings on the indicators and installer improvements still plenty of room for improvement
+ only desktop with accessible network connections
  
- - Documentation
- - Testing
- - Recruiting more people
- - Advocacy
+ Unity2d will be discontinued in the Q cycle so the focus will be on unity 3d
+ working to target the next LTS 14.04
+ 
+ Upstream needs help
+ - The OpenJDK IcedTea team found the gnome codebase hard to debug. a lot of crashes in the gnome screenreader support this ended up that all java swing applications dropped screenreader support for the precise release still unfixed
+ https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/935296 -  java-atk-wrapper prevents java applications from starting
+ it would be great to get the gnome community and java community to discuss the api to prevent crashes
+ 
+ https://launchpad.net/~andyrock/+archive/unity-a11y
+ 
+ Typical issues that blind users report to developers:
+ - the screenreader never stops speaking  the old focus when you switch focus  - the endless talking machine issue.   the worst case is when the screenreader have to spell out complete sentences before starting to describe the next focus item, its slows down productivity and if you navigate quickly  the output queues up and the user have to wait some minutes before geting to the "idle" state
+ - do i need to add more context?  i guess this is a kind of bug thart can show up on application per application

-- 
Accessibility Community Team Plans
https://blueprints.launchpad.net/ubuntu/+spec/community-q-accessibility-community-team-plans