Software accessibility is an extension of usability, although the line that divides the two can be a source of some controversy in regulatory contexts. In design....Making interfaces accessible is an extension of making them usable. Intuitive layouts, clear site architecture, and other good design principles translate to a better foundation for assistive technologies (AT) to access and interpret. AT could be screen readers like Jaws, screen magnifiers included with the popular operating systems, or any number of optimized input devices. Accessibility is most often perceived as an issue for people with some degree of a sight impairment, but the reality is much broader and also includes other disabilities and the aging population. They increasingly need to access applications, websites, and hardware while faced with challenging motor or cognitive disabilities. A brief introduction to disabilities is offered by trace.wisc.edu, led by one of the chief (and most prolific) advocates, Gregg C. Vanderheiden, Ph.D.
Oracle's Accessibility Website states the corporate policy with regard to Oracle's investment and commitment: "Successful access to information by people with disabilities is known as "accessibility." Accessibility is a significant issue for a growing user population and includes not only those born disabled, but those who have experienced incapacitation through accident, illness, or aging."
Oracle's goal is to ensure that products and services are accessible to the disabled community with excellent usability. Industry standards will continue to evolve over time, and Oracle is actively engaged with other market leading technology vendors in addressing technical obstacles.
Oracle's emphasis on achieving accessible solutions hinges on following industry standards. One organization that presses on with harmonization and standardization is the JTC 1, bridging IEC and ISO in the realm of accessibility. Oracle chairs a US based group at INCITS. I have been briefed by colleagues who participated in the W3c WCAG 2.0 (Web Content Accessibility Guidelines) process. I am one of the US representatives for a series of ISO meetings, where ISO 9241-151 and 171 (originating from the HFES sanctioning body) are discussed, and I have recently started contributing to TEITAC's Section 508 Refresh (US Regulation). Since there are a few of these, and they need to be in the context of specific geopolitical landscapes the industry sees strategic value behind harmonization. I have done one such exercise by mapping a portion of the ISO standard to the existing Section 508 language. This will make it easier for vendors of software and hardware to create products that follow best practices and recommendations. Not too mention that the acronym soup gets confusing very fast.
Ope Source standards consortia also play a crucial role in the process of making technology accessible by promoting guidelines and coordinating with government policy. One such initiative emerged recently, led by Richard Schwerdtfeger. It involved IBM Corporation's donation of code to the Free Standards Group Accessibility effort. The work donated complements Microsoft's earlier work on MSAA.
The new code will go a long way to making rich client user interfaces more accessible on the platforms like Firefox. Design points for this contribution are harmonized with the W3C ARIA specification (Roadmap for Rich Client Interfaces in the Formats and Protocols area). Oracle endorsed this initiative recently with the following statement: "Oracle applauds IBM's contribution of IAccessible2 accessibility technology to the Free Standards Group, significantly advancing accessibility for enterprise applications. This effort is consistent with Oracle's commitment to serving customer requirements with open standards and our work in open standards forums such as W3C to address IT solutions for those with disabilities. As a platinum FSG member, we look forward to working with industry partners and the accessibility community to evolve the IAccessible2 standard and improve the quality and usability of AJAX-style user interfaces."
There is more to come in this arena. Industry consortia, regulatory bodies, advocates, and academia are all contributing to this evolving intersection of technology and social policy.
Oracle will continue its investment to make the interfaces more accessible, to communicate their state via VPATs (Voluntary Product Accessibility Templates), and we will continue to work internally and with our partners to make sure that technology is an aid, and not a hindrance in our industry leading applications. The end result will be applications usable by all...
An Example of a VPAT
Just a reminder that what I am providing herein is for informational purposes. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.
This document is for informational purposes only and may not be incorporated into a contract or agreement.
