Why Accessibility
Section 508 of the Federal Rehabilitation Act of 1973 directs federal agencies to purchase electronic and information technology that is accessible to persons with disabilities. Many U.S. States and International customers have similar requirements. To make people with disabilities access OpenSolaris, and to support government efforts, OpenSolaris should support accessibility.
Community Goals
The accessibility community's goal is to make OpenSolaris accessible. We discuss OpenSolaris specific accessibility topics here. Users can ask questions and report problems about accessibility of OpenSolaris. The community work together to answer the questions and fix OpenSolaris accessibility problems.
Projects
Accessibility of installer
- Enable a person with a disability to pop in a live CD and install the operating system without assistance.
Accessibility of Java
- Migration of Java Access bridge from Bonobo/ORBit to D-Bus
Accessibility review of new projects
- Test new projects and give Go/NoGo based on section 508 requirements.
Accessibility of OpenSolaris only applications
- Accessibility for OSPM (OpenSolaris Printing Manager), GPM (GNOME Power Manager), Network Automatic GUI, nwamd, package manager, update manager, ZFS disk management etc.
eSpeak on OpenSolaris
- The plan is to retire FreeTTS in favor of eSpeak. There are many reasons for this (size, locale support, etc.), and the work is underway. See eSpeak working with Orca on Solaris Express and eSpeak 1.37 has direct Solaris audio support for more information. The eSpeak on OpenSolaris project should document this work and also provide a place for people to discuss any issues that arise specifically with Orca's use of eSpeak on OpenSolaris.
BrlTTY on OpenSolaris
- The BrlTTY on OpenSolaris project should document the unique use of BrlTTY on OpenSolaris and also provide a forum for discussing BrlTTY issues on OpenSolaris. It might also be a place to discuss autostarting BrlTTY if a braille display were detected.
Input device support on OpenSolaris
- Setup and configuration of things such as USB Switch devices and ensuring they work with applications such as GOK.
Accessibility testing
- Desktop accessibility testing covers 5 different accessibility scenario testings, including Orca screen reader, keyboard navigation, GOK(GNOME On-screen Keybaord), accessibility theme(HighContrastLargePrintInverse Theme) and Orca screen magnification. Testing will check the application accessibility implementations for 5 different kinds of accessibility users. Accessibility testing team also works on OpenSolaris Desktop Projects Section508 documentations, and promise Desktop Projects could meet the requirements of Section508. Accessibility testing also involves the automation testing work for OpenSolaris Desktop Projects. We join in the GNOME testing community, contribute LDTP OpenSolaris package and GNOME test cases to community. For more information, please refer to OpenSolaris Desktop Accessibility Testing Community, GNOME Desktop Testing Community and other related pages below.