Confirmed users
1,396
edits
Accessibility/RichContentKeyboardBehaviour: Difference between revisions
Accessibility/RichContentKeyboardBehaviour (view source)
Revision as of 08:59, 31 May 2010
, 31 May 2010→Rich element as a lexical unit
| Line 142: | Line 142: | ||
To make this happen special autogenerated {{term||empty character||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. For instance, if there are two rich elements next to each other then there will be (empty)(rich)(empty)(empty)(rich)(empty). | To make this happen special autogenerated {{term||empty character||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. For instance, if there are two rich elements next to each other then there will be (empty)(rich)(empty)(empty)(rich)(empty). | ||
Empty characters are used to designate the element boundaries when the element is treated as lexical unit, however their behavior differs from the word delimiters; like 'space' characters. | |||
The empty characters are not presented visually but they affect keyboard navigation. They do not affect on DOM but they are stored in browser rendering model instead. Also they are [[#Mapping_to_AT|exposed to AT]]. | |||
=== Integral element is a word === | === Integral element is a word === | ||