Accessibility/RichContentKeyboardBehaviour: Difference between revisions

Jump to navigation Jump to search
m
Line 104: Line 104:
A rich element should be treated differently than rich text when user navigates through navigable area. The primary idea is to put the caret immediately before or after the rich element. This makes it possible to select only the rich element as it is not immediately surrounded by the rich text. This requirement has special meaning for editable areas where the user should be able to write text before or after the rich element.
A rich element should be treated differently than rich text when user navigates through navigable area. The primary idea is to put the caret immediately before or after the rich element. This makes it possible to select only the rich element as it is not immediately surrounded by the rich text. This requirement has special meaning for editable areas where the user should be able to write text before or after the rich element.


[davib: I'm not sure my edits capture your intended meaning here ^]
[davidb: I'm not sure my edits capture your intended meaning here ^]


To make this happen special autogenerated ''empty characters'' are inserted before and after the rich element. If the rich elements are placed one after another then each of them has empty character embedded between them, i.e. the elements don't share empty characters.
To make this happen special autogenerated ''empty characters'' are inserted before and after the rich element. If the rich elements are placed one after another then each of them has empty character embedded between them, i.e. the elements don't share empty characters.
Confirmed users
1,085

edits

Navigation menu