346
edits
Accessibility/JSON ARIA: Difference between revisions
→End user experience
| Line 93: | Line 93: | ||
= End user experience = | = End user experience = | ||
== Screen reader users == | |||
Screen reader users would be able to hear the role of the new type of object, and associated properties. | Screen reader users would be able to hear the role of the new type of object, and associated properties. | ||
| Line 98: | Line 100: | ||
* If the object is focused, then any properties in the activeProperties or liveProperties would be spoken | * If the object is focused, then any properties in the activeProperties or liveProperties would be spoken | ||
* If the object is not focused, then any properties in the liveProperties would be treated as a polite change | * If the object is not focused, then any properties in the liveProperties would be treated as a polite change | ||
== Alternative input == | |||
(To do) | |||
= Accessibility API Support (ATK/AT-SPI and IAccessible2) = | = Accessibility API Support (ATK/AT-SPI and IAccessible2) = | ||
Need to fill this out -- the idea is to use object attributes and events to indicate changed attributes. | Need to fill this out -- the idea is to use object attributes and events to indicate changed attributes. | ||