Confirmed users
1,396
edits
Accessibility/RichContentKeyboardBehaviour: Difference between revisions
Jump to navigation
Jump to search
Accessibility/RichContentKeyboardBehaviour (view source)
Revision as of 19:08, 16 February 2010
, 16 February 2010→Up/down navigation
| Line 259: | Line 259: | ||
=== Up/down navigation === | === Up/down navigation === | ||
When the user navigates up/down the lines then the caret should be placed before the character visually placed | When the user navigates up/down the lines (up/down arrow keys) then the caret should be placed before the character visually placed above/bellow relative the visual caret position (anchor position). | ||
If the integral element is placed above/below the anchor position then the caret should be set between empty characters of the element, i.e. integral element should be focused or selected. | |||
If the static element is placed above/below the anchor position then the caret should be set before or after the element depending on what the element edge is closer to the anchor position. | |||
If the caret is on the element (between its empty characters) then the caret should be placed before the element that is closest to the start edge of the element. | |||
If the integral element is focused and it has own processing of up/down arrow keys then up/down navigation is not permitted. In this case up/down arrow + ctrl (option) keys should be used instead. | |||
<div style="margin: 1em 0px; border: 2px dotted orange; padding: 1em;"> | |||
For example, | |||
<pre> | |||
<button>click</button><br> | |||
click | |||
</pre> | |||
If the caret position is between 'cl' and 'ick' substrings and user press the up arrow key then the button should be focused. Then if the user press down arrow key then the caret should be moved before the 'click' word. | |||
</div> | |||
=== Home/end navigation === | === Home/end navigation === | ||