W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13533] New: Navigation to and through static content

From: <bugzilla@jessica.w3.org>
Date: Tue, 02 Aug 2011 22:02:36 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-13533-2486@http.www.w3.org/Bugs/Public/>

           Summary: Navigation to and through static content
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: a11y, a11ytf
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: gcl-0039@access-research.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, public-html-a11y@w3.org

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?

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 2 August 2011 22:02:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:15 UTC