Confirmed users
1,396
edits
Accessibility/RichContentKeyboardBehaviour: Difference between revisions
Accessibility/RichContentKeyboardBehaviour (view source)
Revision as of 19:22, 16 February 2010
, 16 February 2010→Tab navigation
m (→Tab navigation) |
|||
| Line 284: | Line 284: | ||
When the user presses home/end + ctrl (option) keys then the caret should be moved to the begin/end of the navigation block. | When the user presses home/end + ctrl (option) keys then the caret should be moved to the begin/end of the navigation block. | ||
=== Tab navigation === | ===Tab navigation=== | ||
If the | If the element is focused then pressing tab should navigate to the next focusable element in tab order. Next focusable element in tab order can be encountered either inside or outside of the navigation block the element belongs to. This requirement is applied to integral elements and in-text element both. | ||
For example, if editable area contains two buttons (HTML and ARIA buttons) and there is one button outside of editable area | For example, if editable area contains two buttons (HTML and ARIA buttons) and there is one button outside of editable area | ||
| Line 296: | Line 296: | ||
and the 1st button is focused then pressing tab should move the focus to the 2nd button and then to the 3rd button. | and the 1st button is focused then pressing tab should move the focus to the 2nd button and then to the 3rd button. | ||
If the editor is focused then pressing tab should insert '\t' character or its used analogue or move the focus outside of editable area to the next tabable element what depends on editor preferences or platform. | If the editor is focused then pressing tab should insert '\t' character or its used analogue or move the focus outside of editable area to the next tabable element what depends on editor preferences or platform. | ||
== Mouse interaction with rich element == | == Mouse interaction with rich element == | ||