346
edits
Changes
no edit summary
This is a proposal for how authors could define new ARIA widgets.
ARIA role & property extensibility will be important for things such as:
* Diagrams, where the visual appearance (color, dashed lines, whatever) often indicate properties
= Authoring new roles =
== Pointing to new roles definitions from within document content==
}
</pre>
= End user experience =
Screen reader users would be able to hear the role of the new type of object, and associated properties.
Property changes:
* 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
= Accessibility API Support (ATK/AT-SPI and IAccessible2)
Need to fill this out -- the idea is to use object attributes.
