Confirmed users
1,396
edits
Accessibility/WebAccessibilityAPI: Difference between revisions
→Interactions
| Line 476: | Line 476: | ||
Questions/concerns | ====Questions/concerns==== | ||
* Interactions should be extended to allow to specify a control that triggers the action. The concept is described by InidieUI: you can use mouse, touchscreen, keyboard, voice control or a control element to invoke the action. Maybe Interactions should be renamed to Triggers to share terms with IndieUI. | * Interactions should be extended to allow to specify a control that triggers the action. The concept is described by InidieUI: you can use mouse, touchscreen, keyboard, voice control or a control element to invoke the action. Maybe Interactions should be renamed to Triggers to share terms with IndieUI. | ||
Here's the image of InideUI action/interaction concept. | Here's the image of InideUI action/interaction concept. | ||
http://www.w3.org/WAI/intro/iui-scroll.png | http://www.w3.org/WAI/intro/iui-scroll.png | ||
Alternatively we could introduce relations between actions like "triggers" and "triggeredby". | |||
* What about highlevel actions (uberactions), for example, "press" buttons means "send something somewhere". This may be covered by label. Another example, selected listitem on the left changes a view on the right, "select" actions has meaning of "change view". Or checkbox that enables/disables related controls, "check/uncheck" action means "enable/disable controls". These examples correlates to controlledby/controllerfor relations, but the relations doesn't reveal type of control. | |||
===Parent-child relations=== | ===Parent-child relations=== | ||