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

[Bug 13540] New: Specifying next and previous elements for reading and navigation order

From: <bugzilla@jessica.w3.org>
Date: Tue, 02 Aug 2011 22:50:12 +0000
To: public-html@w3.org
Message-ID: <bug-13540-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13540

           Summary: Specifying next and previous elements for reading and
                    navigation order
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Keywords: a11y
          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


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.

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

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:26 UTC