Confirmed users
1,085
edits
Accessibility/RichContentKeyboardBehaviour: Difference between revisions
Accessibility/RichContentKeyboardBehaviour (view source)
Revision as of 15:31, 7 April 2010
, 7 April 2010→Navigation blocks
DavidBolter (talk | contribs) |
DavidBolter (talk | contribs) |
||
| Line 63: | Line 63: | ||
== Navigation blocks == | == Navigation blocks == | ||
Navigation order should be defined by navigation blocks. The user should navigate the block entirely before the caret moves to the next block. For example if two blocks are visually placed next to each other and the user reaches the end of line of the first block then caret should be moved to the | Navigation order should be defined by navigation blocks. The user should navigate the block entirely before the caret moves to the next block. For example if two blocks are visually placed next to each other and the user reaches the end of line of the first block then caret should be moved to the first line of the next block. | ||
The navigation blocks are defined by layout flow. All content of the normal flow is contained by one navigation block what may contain nested blocks | The navigation blocks are defined by layout flow. All content of the normal flow is contained by one navigation block what may contain nested blocks. In contrast to normal flow content the ''float'' content or the ''absolute'' positioned content are presented by its own blocks, i.e. each container (where the flow is changed) is represented by its own navigation block. | ||
The navigation blocks can be nested. For example, if the content contains editable area then the area is presented by own block which is contained by the | The navigation blocks can be nested. For example, if the content contains an editable area then the area is presented by its own block which is contained by the containing parent block. | ||
The next block is defined by the page layout. If two blocks are overlapped then "more closer" block is used and then "more far" is used. If two blocks occupy the same place then z-index is used, the bottom content is excluded from navigation order. | The next block is defined by the page layout. If two blocks are overlapped then the "more closer" block is used and then the "more far" is used. If two blocks occupy the same place then z-index is used, the bottom content is excluded from navigation order. | ||
Navigation blocks are organized in tree structure. The tab navigation order is defined within the navigation block until the navigation order is changed | Navigation blocks are organized in a tree structure. The tab navigation order is defined within the navigation block until the navigation order is changed via changing the tabindex attribute value. | ||
<div style="margin: 1em 0px; border: 2px dotted orange; padding: 1em;"> | <div style="margin: 1em 0px; border: 2px dotted orange; padding: 1em;"> | ||
| Line 83: | Line 83: | ||
</pre> | </pre> | ||
which visually can presented as | which visually can be presented as | ||
<table> | <table> | ||
| Line 96: | Line 96: | ||
</table> | </table> | ||
If the user navigates through normal paragraph by characters then it should be navigated entirely, the caret should be moved to the floating paragraph when the user reaches the end of the normal paragraph. Note, the first line of the floating paragraph ("floating multiline") is visually "next" to the first line of the normal paragraph ("normal multiline"). | If the user navigates through a normal paragraph by characters then it should be navigated entirely, the caret should be moved to the floating paragraph when the user reaches the end of the normal paragraph. Note, the first line of the floating paragraph ("floating multiline") is visually "next" to the first line of the normal paragraph ("normal multiline"). | ||
</div> | </div> | ||