Confirmed users
1,396
edits
Accessibility/EditorBehaviourOnUserInput: Difference between revisions
Accessibility/EditorBehaviourOnUserInput (view source)
Revision as of 01:25, 15 March 2010
, 15 March 2010→Stub approach
| Line 39: | Line 39: | ||
==Stub approach== | ==Stub approach== | ||
All rich elements aren't focusable and included into navigation sequence. When the caret is between empty characters of the rich word or sentence then the rich element is called selected. Visually it might look a blue border around the element. | All rich elements aren't focusable and included into navigation sequence. When the caret is between empty characters of the rich word or sentence then the rich element is called selected. Visually it might look a blue border around the element. | ||
===Refined statements=== | |||
#editable area is always [[Accessibility/RichContentKeyboardBehaviour#Navigation_blocks|navigation block]] | |||
#if caret is inside an editable area then the editor is focused | |||
#if the editor is focused then pressing tab should insert '\t' character or its used analogue or move the focus outside and editable area to the next tabable element what depends on editor preferences or platform. | |||
=Suggestion= | =Suggestion= | ||