There is no text object model, for example, to help assistive technologies deal with complex web content. The model is based on "roles" defined a decade ago, and you cannot support new UI behaviors or merge two or more roles together. Microsoft designed the Microsoft Active Accessibility object model at about the same time as Windows 95 was released. MSAA Roles and UI Automation Control Patterns UI Automation offers a richer set of properties, as well as a set of extended interfaces called control patterns to manipulate accessible objects in ways Microsoft Active Accessibility cannot.įor more information, see UI Automation Properties Overview and UI Automation Control Patterns Overview. Microsoft Active Accessibility offers a single Component Object Model (COM) interface with a fixed, small set of properties. However, Microsoft Active Accessibility refers to the application or control offering the UI for accessibility as the server, while UI Automation refers to this as the provider. Both refer to the accessibility tool or software automation program as the client. Microsoft Active Accessibility represents individual UI elements as accessible objects, and UI Automation represents them as automation elements. Developers of accessibility tools can use this information to create software that makes applications running on Windows more accessible to people with vision, hearing, or motion disabilities.īoth Microsoft Active Accessibility and UI Automation expose the UI object model as a hierarchical tree, rooted at the desktop. The purpose of both technologies is to expose rich information about the UI elements used in Windows applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |