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

[Bug 13539] New: Specify reading and navigation order

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

           Summary: Specify reading and navigation order
           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

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.

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 encounters a table that is designed to be read
down the columns rather than across the rows, this simplistic navigation is
entirely inappropriate. A similar problem occurs when CSS is used to rearrange
blocks of text on the screen.

Recommendation: Allow marking up a table to indicate whether the preferred
reading order is by columns, by rows, both (either being equally valid),
neither (not designed to be read by columns or rows), or left unspecified. This
could be done with a new attribute, such as orientation="columns".

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:40:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:59 UTC