Keyboard accessibility

[markmagennis]

Our users need to be able to access all the functionality using the keyboard only, i.e. without a mouse. Is this possible for the functions that involve interacting with the book content itself, e.g. notes, highlighting, annotating, dictionary? For example, can users Tab into the content pane, move the cursor to a position, select a piece of text, bring up the menu and toolbar and select operations, using keyboard navigation keys or shortcuts?

[johnfactotum]

The paginator does handle tabbing and caret browsing. Though it would be difficult to move the caret and select text with the keyboard alone without enabling the browser's caret browsing mode.

Furthermore, it does not handle using the keyboard to access annotations. You can implement this relatively easily for caret browsing, requiring the user to move the caret to the highlighted text manually. It would be more involved to make them tabbable because highlighting does not add tabbable elements (or any element, for that matter) to the book's document. Highlights are rendered outside the iframes and overlaid on the them. To implement this, one can either make them part of the tabbing sequence by intercepting the keyboard event, or to implement a keyboard shortcut specifically for accessing the annotations.