IAccessible2

IAccessible2
Name	IAccessible2
Developer	IBM, Sun Microsystems
Released	2006
Programming language	C++
Operating system	Microsoft Windows
License	Mozilla Public License

IAccessible2

IAccessible2 is an accessibility application programming interface introduced to extend assistive technology support on Microsoft Windows. It was developed through collaborations involving IBM and Sun Microsystems to complement existing accessibility frameworks and to provide richer information for screen readers, magnifiers, and other assistive technologies. The initiative was influential in interoperability efforts among vendors and standards bodies during the mid‑2000s, affecting applications, toolkits, and browser integration.

Overview

IAccessible2 provides a set of COM interfaces and semantic information that augment the Microsoft Active Accessibility model used by assistive technologies such as JAWS (screen reader), NVDA, Window-Eyes, ZoomText, and other accessibility tools. It defines roles, states, and attributes that enable applications like Firefox, Thunderbird (software), LibreOffice, OpenOffice.org, IBM Lotus Symphony to expose document structure, table semantics, and text attributes. The effort aligned with initiatives by organizations including IBM, Sun Microsystems, The Mozilla Foundation, Eclipse Foundation, and accessibility consortia such as W3C working groups.

History and Development

Work on the specification began after IBM and Sun engaged with the accessibility community to address limitations in the Microsoft accessibility stack encountered by applications such as Mozilla Firefox and office suites like OpenOffice.org. Stakeholders included vendors, assistive technology developers such as Freedom Scientific, and standards participants at W3C and industry fora including ISO. The release in 2006 followed discussions about interoperability with platforms supported by GNOME and KDE projects and was influenced by prior models like Microsoft Active Accessibility and efforts around the Accessible Rich Internet Applications suite. Contributions and collaboration among corporations and nonprofits helped shape the API's evolution and specifications.

Technical Specification and Architecture

The specification describes COM interfaces implemented alongside existing Microsoft accessibility interfaces to convey richer semantics, such as table cell coordinates, column and row headers, and hyperlink relations. It defines object models for controls, text, tables, and selections that assistive technologies query via standard COM calls and events. The architecture was designed to map concepts from AT-SPI used in GNOME and the IAccessible model used in Microsoft environments, enabling translation layers implemented in toolkits like Qt, GTK+, and Mozilla XULRunner to expose accessibility trees. The API includes event models for focus, selection, and value changes used by assistive tools developed by Freedom Scientific, Serotek, and other vendors.

Implementations and Platform Support

Implementations appeared in applications and toolkits including Firefox, Thunderbird (software), OpenOffice.org, LibreOffice, and in middleware bridges for Java Swing and Mozilla Gecko. Accessibility support was integrated in Windows builds of Eclipse, IBM Lotus Symphony, and enterprise applications from vendors such as Oracle Corporation that used Java accessibility bridges. Assistive technologies like JAWS (screen reader), NVDA, and Window-Eyes included support for the API, while toolkits like Qt and GTK+ provided adaptors to map their accessibility trees to the COM interfaces specified by the API.

Relation to Other Accessibility APIs

The API was conceived as complementary to Microsoft Active Accessibility and as a means to bring parity with AT-SPI implementations used in Linux desktop environments like GNOME and applications that used GTK+. It also interfaced conceptually with W3C specifications such as WAI-ARIA from the W3C Web Accessibility Initiative to represent rich web semantics in desktop applications. Interoperability work involved projects that bridged Java Accessibility API and IAccessible models, and discussions at standards bodies including ISO aimed at harmonizing semantics across platforms and assistive technologies.

Adoption, Impact, and Criticism

Adoption by major applications and support from assistive technology vendors increased desktop accessibility on Windows for complex documents, spreadsheets, and web content rendered in desktop browsers. The specification influenced accessibility practices in projects like Mozilla and LibreOffice and encouraged toolkit vendors such as Qt to offer Windows accessibility backends. Critics pointed to fragmentation among multiple accessibility APIs, the complexity of maintaining parallel interface layers, and challenges in keeping mappings current with evolving web standards like HTML5. Nonetheless, the initiative contributed to cross‑vendor dialogue involving IBM, Sun Microsystems, The Mozilla Foundation, and assistive technology firms, and informed later interoperability efforts and standards work within W3C and ISO.

Category:Accessibility Category:Application programming interfaces