This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
User agents need to support navigation to and through non-editable content such as blocks of text and images ("caret browsing"). Issue: Is there anything that HTML5 should do to facilitate this feature? Are any changes needed to the spec's discussion of focus, tabindex, events, etc.? Use case: Wayne needs to select and copy some content from a Web page. Pressing the Tab key would normally move the focus between controls, links, frames, and the browser UI, but it would not stop at blocks of read-only text and images. For this task Wayne turns on his brower's "caret browsing mode," which adds each block of read-only content to the tab order. He can then move focus to the appropriate block, move the text cursor through it, select a range, and copy it to the clipboard or invoke its shortcut menu, all using the keyboard. This is true regardless of whether the page's author considered that the focus could be on and within a block of static content. Are there things the author should do in their scripting to better accommodate it and avoid being broken by it?
Issue: If the user is navigating through a page using a caret browsing or similar feature, and then navigate to another page and back, should the user agent restore focus to the same element and location within the element as when they left (e.g. focus on a p element and the text focus between the third and fourth characters within that paragraph)?
Other things to keep in mind include focus other than on operable elements, the dual nature of focus on an element and text focus and/or search results within the element, the practice of having search and navigation be relative to the user's point of regard (e.g. scrolling a viewport and then pressing navigation keys or doing a search), etc.
mass-move component to LC1
As far as I can tell, this is entirely a UA UI issue.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: <http://dev.w3.org/html5/decision-policy/decision-policy.html>. Status: Rejected Change Description: no spec change Rationale: This is out of scope for HTML.
Bug Triage sub-team suggests the User Agent Accessibility Guidelines address this issue.