Authors should be able to specify preferred direction and/or order for
sequential navigation, even among things such as tables that would not normally
have a tab order.

Recommendation: Allow marking up any element with a reference to the logically next and/or previous elements, for use when those are not the next/previous elements in the source. 

We do not yet have a recommended method, but will be doing further discussion. 

For example, one potential method would be general attributes for next and previous such when a browser was implementing caret browsing and the caret moved beyond the end of a paragraph marked up with next="story5", that attribute would be a hint to the browser to move the caret to the element with id="story5" rather than to the element that follows the paragraph in the HTML source. 

Use case: Masahiko is reading a web page, and uses browser commands to move the
text cursor to the next and previous paragraphs. In most cases this works fine
because the suggested reading order is that in which elements occur in the
HTML. However, when Masahiko is reading a document where CSS is used to reorder and reposition paragraphs on the screen, caret browsing in document order would seem to Masahiko to be a random order, and therefore very confusing and unusable.