9
edits
Accessibility/RichContentKeyboardBehaviour: Difference between revisions
Jump to navigation
Jump to search
m
Accessibility/RichContentKeyboardBehaviour (view source)
Revision as of 08:00, 16 March 2010
, 16 March 2010→Keyboard interaction with the rich element
Sergeyreym (talk | contribs) m (→Terminology) |
Sergeyreym (talk | contribs) |
||
| Line 183: | Line 183: | ||
If the in-text element is driven by global navigation rules (e.g. HTML:a or ARIA controls) then nothing special should be done. However if the ARIA control handles and process keyboard events then it should care to prevent default action explicitly. | If the in-text element is driven by global navigation rules (e.g. HTML:a or ARIA controls) then nothing special should be done. However if the ARIA control handles and process keyboard events then it should care to prevent default action explicitly. | ||
For example if the text field processes keyboard events to implement the caret navigation then it should prevent the default action | For example if the text field processes keyboard events to implement the caret navigation then it should prevent the default action if the caret can't be moved within the text field. So that if the caret achieves the end of text field then the global keyboard navigation are applied and the caret is moved out from the text field to next keyboard navigable content. | ||
== Keyboard navigation == | == Keyboard navigation == | ||