[Blueprint community-o-accessibility-team] Discussion of the goals of the accessibility team in the Oneiric cycle

[Alan Bell]

Blueprint changed by Alan Bell:

Whiteboard changed:
  Work items:
  [themuso] Write a document that explains the architecture of the GUi accessibility framework, Orca's relationship with this architecture, and Orca's relationship with Text to Speech: INPROGRESS
  [themuso] Investigate getting the Java ATK wrapper packaged (low priority): POSTPONED
  [themuso] Investigate latest work on dasher to work with at-spi2, and update Ubuntu package: POSTPONED
- [alanbell] Contact upstream Compiz Enhanced zoom maintainer to check on progress: TODO
+ [alanbell] Contact upstream Compiz Enhanced zoom maintainer to check on progress: DONE
  [accessibility] Set up Accessibility Testing / Bug filing classes in ubuntu-classroom: TODO
+ 
+ Upstream compiz zoom text tracking is acknowledged as wishlist but not
+ being progressed, had some discussions about how to do it without making
+ at-spi2 a dependency of the plugin as a whole, setting up a dev
+ environment to work on this in the P cycle.
  
  Onscreen Keyboards
      What requirements should our onscreen keyboard meet?
      Onboard?
      Caribou?
      Would Dasher even work?
  
  GDM
      Needs keyboard shortcut for Universal Access menu
      Perhaps opening Universal Access menu should start screenreader by default
  
  Testing

-- 
Discussion of the goals of the accessibility team in the Oneiric cycle
https://blueprints.launchpad.net/ubuntu/+spec/community-o-accessibility-team