IAccessible2

Whereas UI Automation marks a radical break from Microsoft Active Accessibility (MSAA) to create a more flexible accessibility API, IAccessible2 fills in perceived omissions in MSAA to match the Java Accessibility API and Assistive Technology Service Provider Interface (AT-SPI).[4] By extending the MSAA interface, rather than replacing it, IAccessible2 allows "application developers to leverage their investment in MSAA while also providing an Assistive Technology (AT) access to rich document applications."[5] It is also advantageous for Microsoft's commercial competitors, Sun and IBM, to promote an alternative accessibility interface to the Windows platform standard, which explains both their focus on developing non-MSAA/UIA interfaces and their promotion of cross-platform support despite the lack of any AT that is cross-platform that might use it.

Project Missouri was started when the State of Massachusetts, in the process of adopting the OpenDocument format for its public records, required that the format be made accessible.[6] Increasing the accessibility of dynamic web applications, for example by exposing custom controls for use with assistive technology and by filtering streams of new information by type and importance, became a second major focus for the project.[7]

Support for IAccessible is present in LibreOffice as of version 4.2.[8][9] It is in development for Apache OpenOffice,[10] Mozilla Application Suite,[11] NonVisual Desktop Access[12] and the Opera web browser.[13] Although IAccessible2 was introduced as a Windows accessibility API, Qt Development Frameworks is treating IAccessible2 as a potential alternative to AT-SPI on Linux too, and planning to add preliminary support to Qt 4.3.[14] As of 2019, Qt uses MSAA and IAccessible2 on Windows, and continues to use AT-SPI for Unix/X11 systems.[15]