- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Feb 2014 01:05:10 +0000
- To: public-html-admin@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24642
Bug ID: 24642
Summary: Should it be conforming to use role=presentation for
tables that have border=1?
Product: HTML WG
Version: unspecified
Hardware: PC
URL: http://www.w3.org/html/wg/drafts/html/master/tabular-d
ata.html#attr-table-border
OS: All
Status: NEW
Keywords: a11y
Severity: normal
Priority: P2
Component: HTML5 spec
Assignee: dave.null@w3.org
Reporter: xn--mlform-iua@xn--mlform-iua.no
QA Contact: public-html-bugzilla@w3.org
CC: eoconnor@apple.com, faulkner.steve@gmail.com,
mike@w3.org, public-html-admin@w3.org,
public-html-wg-issue-tracking@w3.org,
rubys@intertwingly.net,
xn--mlform-iua@xn--mlform-iua.no
See: http://www.w3.org/TR/html5/index.html#attributes-1
And: http://www.w3.org/TR/html5/tabular-data.html#attr-table-border
According to the first URL, the table@border attribute is an ”Explicit
indication that the table element is not being used for layout purposes”.
(Second URL basically repeats the same message.)
As the spec stands, it does not make sense to combine border=1 with
role=presentation since the two attributes send different messages to user
agents regarding whether the table is a layout table or a data table. E.g. to
visual users, the table could easily be perceived as a data table, while for AT
users it would probably be perceived as a layout table.
Hence I ask the editors to consider whether it should be non-conforming to
combine role=presentation and (conforming) border attribute values on the same
table.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 13 February 2014 01:05:12 UTC