Accessibility/EditorBehaviourOnUserInput: Difference between revisions

Accessibility/EditorBehaviourOnUserInput (view source)

Revision as of 10:05, 6 November 2009

496 bytes added , 6 November 2009

→‎Summary

Surkov.alexander

Confirmed users

1,396

edits

@@ Line 1: / Line 1: @@
 =Summary=
-The article is aimed to propose editor behaviour on user input when control elements are contained in editable area. Under control elements term is considered either HTML controls or ARIA controls. The main point is control element inside of editable area should behave as "normal" control, i.e. when it is not placed inside of editable are. For example, if user clicks on HTML:select@size="1" then drop down list is appeared. As well it means keyboard works as usually if control element is focused.
+The article is aimed to propose editor behaviour on user input when control elements are contained in editable area. Under control elements are considered either HTML controls or ARIA controls.
+=Suggestion=
+The main point is control element inside of editable area should behave as "normal" control, i.e. when it is not placed inside of editable are.
+;mouse interaction
+Control behaviour is the same on mouse input. For example, if user clicks on combobox (HTML:select) then drop down list is appeared.
+;keyboard interaction
+Control behaviour is the same on keyboard input when control is focused until action on key press can be performed. For example, if textbox (HTML:input) is focused then arrow keys moves through its text. If listbox (HTML:select) is focused then up/down arrow keys change selected item.
+;tab navigation
+If control is focused then tab press should navigate to the next control within editable are or outside of editable area if there is no control inside of editable are