- From: <bugzilla@jessica.w3.org>
- Date: Tue, 17 Jan 2012 00:05:51 +0000
- To: public-html-a11y@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13539
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.
[snip]
> 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:
http://www.w3.org/TR/css3-grid-layout/
http://www.w3.org/TR/2011/WD-css3-regions-20111129/
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:
http://www.w3.org/TR/wai-aria/states_and_properties#aria-flowto
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