🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BSI PD ISO/IEC TR 13066-2:2016

BSI PD ISO/IEC TR 13066-2:2016

$215.11

Information technology. Interoperability with assistive technology (AT) – Windows accessibility application programming interface (API)

Published By Publication Date Number of Pages
BSI 2016 98
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Categories: ,

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

This part of ISO/IEC 13066 specifies services provided in the Microsoft Windows platform to enable assistive technologies (AT) to interact with other software. One goal of this part of ISO/IEC 13066 is to define a set of application programming interfaces (APIs) for allowing software applications to enable accessible technologies on the Microsoft Windows platform. Another goal of this part of ISO/IEC 13066 is to facilitate extensibility and interoperability by enabling implementations by multiple vendors on multiple platforms.

This part of ISO/IEC 13066 is applicable to the broad range of ergonomics and how ergonomics apply to human interaction with software systems.

PDF Catalog

PDF Pages PDF Title
7 Foreword
8 Introduction
9 1 Scope
2 Terms and definitions
15 3 General description and architecture of the Microsoft Windows Automation API
3.1 General description
3.1.1 Microsoft Active Accessibility overview
16 3.1.2 UI Automation overview
17 3.1.3 IAccessibleEx interface
18 3.2 Architecture
20 4 Using the API
4.1 Using the Microsoft Active Accessibility API
21 4.1.1 Types of Microsoft Active Accessibility support
4.1.2 Retrieving an accessible object
4.1.3 The WM_GETOBJECT message
22 4.1.4 Special values of Object Identifier
23 4.2 Using the UI Automation API
4.2.1 UI Automation model
24 4.2.2 UI Automation tree
4.2.3 UI Automation control patterns, control types, properties, and events
29 4.3 Using the IAccessibleEx interface
4.3.1 The IAccessibleEx interface implementation
32 5 Exposing User Interface Element Information
5.1 General
33 5.2 Exposing UI Elements with Microsoft Active Accessibility
5.2.1 How an MSAA Server exposes relevant properties
34 5.2.2 Provide support for the Accessible Object structure
35 5.2.3 Support hit testing
5.2.4 Generate appropriate WinEvents
5.2.5 Object identifier
36 5.2.6 How MSAA clients access exposed UI elements
5.3 Exposing UI Elements with UI Automation
5.3.1 Types of providers
5.3.2 UI Automation provider concepts
37 5.3.3 Provider interfaces
38 5.3.4 Property values
5.3.5 Provider navigation
39 5.3.6 Provider reparenting
5.3.7 Provider repositioning
40 5.3.8 How UI Automation clients access exposed UI Elements
41 6 Exposing UI Element actions
6.1 Exposing UI Element actions in MSAA
6.2 Exposing UI Element actions in UI Automation
6.2.1 UI Automation control pattern components
42 6.2.2 Control patterns in providers and clients
6.2.3 Dynamic control patterns
6.2.4 Control patterns and related interfaces
44 7 Keyboard focus
7.1 MSAA keyboard focus and selection
7.1.1 Focus and selection properties and methods
45 7.1.2 Events triggered in menus
7.2 UI Automation keyboard focus and selection
7.2.1 Focus
46 7.2.2 Selection
52 8 Events
8.1 WinEvents
8.1.1 USER’s role in WinEvents
53 8.1.2 Receiving event notifications
8.1.3 Sending events
8.1.4 The allocation of WinEvent IDs
54 8.2 UI Automation events
55 8.2.1 How providers raise events
56 8.2.2 How clients register for and process events
9 Programmatic modifications of states, properties, values, and text
9.1 UI Automation specifications
9.1.1 Introduction
57 9.1.2 UI Automation elements
9.1.3 UI Automation tree
58 9.1.4 UI Automation properties
9.1.5 UI Automation control patterns
9.1.6 UI Automation control types
9.1.7 UI Automation events
59 10 Design considerations
10.1 UI Automation design considerations
10.1.1 UI Automation clients
62 10.1.2 UI Automation providers
65 10.1.3 Coexistence and interoperability with Microsoft Active Accessibility
66 10.2 IAccessibleEx design considerations
10.2.1 Design consideration for providers before implementing the IAccessibleEx interface
10.2.2 IAccessibleEx interface for providers
67 10.2.3 IAccessibleEx interface for clients
71 11 Further Information
11.1 Microsoft Active Accessibility and Extensibility
11.2 UI Automation extensibility features
11.2.1 Registration of custom UI Automation properties, events, and control patterns
72 11.2.2 How clients and providers support custom control patterns
73 Annex A (informative) Microsoft Active Accessibility to Automation Proxy
80 Annex B (informative) UI Automation to Microsoft Active Accessibility Bridge
85 Annex C (informative) UI Automation for W3C Accessible Rich Internet Applications (ARIA) Specification
89 Annex D (informative) Other Useful APIs for Development and Support of Assistive Technologies
96 Bibliography

Related products

BSI PD ISO/IEC TR 13066-2:2016
$215.11