Changes made to UAAG2 Techniques
Checkpoint 1.2 ckl: Add some more techniques related to ARIA and accessibility APIs, such as:
- In a Rich Internet Application (RIA), an element with an event handler often defines a widget and has a defined "role" attribute to describe the behavior of the widget. The user agent must expose the value of role attributes to assistive technologies through DOM interfaces but should also expose these attributes using platform accessibility APIs. IAccessible2 (IA2) for Windows and the Accessibility Toolkit (ATK) for Linux have roles defined which easily map to roles defined for Accessible Rich Internet Applications (ARIA).
See http://www.w3.org/TR/aria-role/ for ARIA roles.
See http://accessibility.freestandards.org/a11yspecs/ia2/docs/html/ for IA2 roles.
See http://developer.gnome.org/doc/API/2.0/atk/AtkObject.html#AtkRole for ATK roles.
Checkpoint 1.3 ckl: Under techniques for this guideline, reference Live Regions section of ARIA States spec: http://www.w3.org/TR/aria-state/#liveregions
Checkpoint: (Technique is relevant to 4.1, 4.2, 4.3, 4.7, and possibly others.) JR: if a user agent uses *operating environment* services to render any content (e.g., tooltips displaying attribute values, window title bar displaying document titles), provide users with a shortcut to configure any display or control preferences of those services.