W3C home > Mailing lists > Public > public-html-a11y@w3.org > January 2012

[Bug 13539] Specify reading and navigation order

From: <bugzilla@jessica.w3.org>
Date: Tue, 17 Jan 2012 00:05:51 +0000
To: public-html-a11y@w3.org
Message-Id: <E1RmwYh-0003Pz-DJ@jessica.w3.org>

Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed:

           What    |Removed                     |Added
                 CC|                            |bhawkeslewis@googlemail.com

--- Comment #7 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2012-01-17 00:05:51 UTC ---
(In reply to comment #6)
> <th scope="col"> would not be sufficient for tables because it is only usable
> on tables that have heading rows or columns, whereas tables are often used
> without them. Thus, tables require a separate attribute such as
> orientation="columns".

Can you point to an example of the sort of table you have in mind?

> In addition, it's worth considering that tables are only one example of the
> general problem of reading order being different from document order. 


> A common example of the latter is many news web sites where selecting an
> article and its title also selects a sidebar because it immediately follows the
> title in the source document, even though visually it appears to follow the
> article, being displayed in a separate column on the right.

The general problem of allowing authors to distinguishing a logical order from
a visual layout order will be solved by CSS features currently in draft:



Even when visual layout order is incorrectly pushed into the HTML layer,
authors can use the @aria-flowto attribute to indicate a logical reading order:


Why do you think we should introduce additional HTML features for this?

Configure bugmail: https://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, 17 January 2012 00:05:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:26 UTC