A few highlights of this change:
If the element pointed by sequential focus navigation starting point is removed from the document tree, a point where there was the element at would be the starting point.This is good for accessibility in modern web sites, such as single-page apps. We'll first need to see some follow-on improvements in browsers and assistive technologies, but eventually this might allow web authors to simplify focus management, as DOM elements are removed and changed.
Implementation: Sequential focus navigation starting point is represented as a Range object, and it is owned by a Document.This is the technically elegant part. It builds on existing patterns, to achieve something new.
Now I have a few questions for the community. The behavior is already looking good for users, so these questions are mainly geared toward supporting web authors.
- There's a standard and widely supported Range object. What's the interface to access this new special Range? Maybe as a property of the Document?
- The related WebKit ticket points out that Gecko (Firefox) and Trident (Internet Explorer) already have their own implementations. Can this interface be standardized across browsers, or is it too late for that?
- Would it make sense for this Range object to be the relatedTarget of blur events?
- Is there a consistent behavior in browsers for caret navigation?
- What are the use cases for mobile browsers?