W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2015

Re: CSS display property and tables

From: Jesper Tverskov <jesper@tverskov.dk>
Date: Mon, 27 Apr 2015 13:08:44 +0200
Message-ID: <CAAuwN4EKi45tN1tqr__0t-W8+HCihW+2cqZjni9+wjONVXfjMw@mail.gmail.com>
To: w3c-wai-ig@w3.org
I think that:

"If there is no alternative to using HTML markup, you can put
role="presentation" on the <table> element. This will stop the table
semantics from being mapped to the accessibility API [2]."

is good advice, I will follow, when we have clear cut examples of
tables for layout.


On Sun, Apr 26, 2015 at 2:25 PM, Jesper Tverskov <jesper@tverskov.dk> wrote:
> I have published a blog-like article, “When even nested tables are
> just great”, at my website:
> http://www.friendlytest.com/doc/en.When_even_nested_HTML_tables_are_just_great.html
> I would like to hear the Accessibility Community, if there is
> consensus about the use of the CSS display property and the table
> related values, “table”, “table-row” and “table-cell” for short.
> In my opinion, tables should be made with table markup. Using e.g.
> “div” elements and the display property to make tables, is not a
> shortcut to get rid of the very last table of design.
> If a table of design is necessary as an exception to the rule then use
> a HTML table. It is simply too far out and misuse of the display
> property, confusing, and bound to be less widely supported, to use
> “div” and the display property as a substitute for a HTML table of
> design?
> Cheers
> Jesper Tverskov
Received on Monday, 27 April 2015 11:09:13 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 May 2017 01:54:15 UTC