346
edits
Accessibility/JSON ARIA: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(New page: =Role extensibility= This is a proposal for how authors could define new ARIA widgets. ==Why do we need this?== ARIA role & property extensibility will be important for things such as: ...) |
No edit summary |
||
| Line 3: | Line 3: | ||
This is a proposal for how authors could define new ARIA widgets. | This is a proposal for how authors could define new ARIA widgets. | ||
=Why do we need this?= | |||
ARIA role & property extensibility will be important for things such as: | ARIA role & property extensibility will be important for things such as: | ||
| Line 12: | Line 12: | ||
* Diagrams, where the visual appearance (color, dashed lines, whatever) often indicate properties | * Diagrams, where the visual appearance (color, dashed lines, whatever) often indicate properties | ||
= Authoring new roles = | |||
== Pointing to new roles definitions from within document content== | == Pointing to new roles definitions from within document content== | ||
| Line 90: | Line 91: | ||
} | } | ||
</pre> | </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. | |||