Discussion of the goals of the accessibility team in the Oneiric cycle
What the Accessibility Team will be working on during Oneiric. This should include how to get the community more involved with accessibility in all areas.
Blueprint information
- Status:
- Not started
- Approver:
- Kate Stewart
- Priority:
- Medium
- Drafter:
- Charlie Kravetz
- Direction:
- Approved
- Assignee:
- Accessibility
- Definition:
- Drafting
- Series goal:
- Accepted for precise
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
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: POSTPONED
[themuso] Investigate getting the Java ATK wrapper packaged (low priority): DONE
[themuso] Investigate latest work on dasher to work with at-spi2, and update Ubuntu package: DONE
[alanbell] Contact upstream Compiz Enhanced zoom maintainer to check on progress: DONE
Set up Accessibility Testing / Bug filing classes in ubuntu-classroom: POSTPONED
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: POSTPONED
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
pitti, 2011-10-11: most items were postponed/todo, moving to Precise.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
