There are several reasons why the answer should be "yes."
It can improve user experience in some casesToday, for accessibility it's often necessary to set focus on a div or static text. If browsers and assistive technologies will provide a consistent experience for anchor links, then instead of setting focus on non-actionable content, it would be more like native browser behavior to set a Sequential Focus Navigation Starting Point. In such cases users would expect to see the element in the viewport, so the author should also use
There are good technical precedentsSetting
window.location.hrefcreates the same effect as a user clicking a link to a new page.
In most browsers,
Element.focus()creates the same effect as a user clicking an anchor link to land on a focusable element.
It might already workWhen an element has focus, then the expected behavior of
Element.blur()-- after Chromium issue 454172 -- is to create a Sequential Focus Navigation Starting Point.
So what should happen if the author invokes
Element.blur()on an element that does not currently have focus? The logical consequence would be for this element to become the Sequential Focus Navigation Starting Point.
I could live with this counterintuitive behavior of
Element.blur(), like we've all learned to live with