Accessibility/RichContentKeyboardBehaviour: Difference between revisions

Accessibility/RichContentKeyboardBehaviour (view source)

160 bytes added , 4 February 2010

m

Confirmed users

1,396

edits

@@ Line 147: / Line 147: @@
 === Navigation by words ===
-If the caret position is somewhere in the middle of the text and the user navigates by words (ctrl + arrow key or alt (option) + left/right arrow depending on platform) and rich element is encountered on the way then the rich element should be skipped, i.e. the caret should be moved from the position before the element to the position after the element.
+If the caret position is somewhere in the middle of the text and the user navigates by words (ctrl or alt (option) + left/right arrow key depending on platform) and rich element is encountered on the way then the rich element should be skipped, i.e. the caret should be moved from the position before the element to the position after the element.
-For example, if the caret is before the HTML table element (or HTML anchor element) then caret shouldn't be moved into the table content (or HTML anchor).
+For example, if the caret is before the HTML button element then the caret should be moved after element. If the caret is before HTML input then it should be skipped as well. The same is applicable to HTML anchor element. So that any compound element is excluded from navigation sequence when the users navigates by words.
 If the caret is in the middle of the compound element then the user should navigate the compound element entirely.