WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: When is use of scope, col and/or colgroup important for accessibility?

for

From: Ryan E. Benson
Date: Jul 24, 2012 8:50PM

Glenda,

> If I'm in a one dimensional data table, I just use the appropriate
> <th> tags to mark up all my table headers.
At work, I would near -automatically mark this as not compliant. I
would give a bit of leeway if the table in question was 3x3 or under.
Would I say a 4x2 or 4x3 is not compliant? I do not wish to discuss
that level of policy here.

Jared said
> I'm not aware of any accessibility benefit of colgroup, rowgroup,
> thead, tbody, or tfoot (except perhaps improved comprehension of
> multi-page printed tables).
I agree with this. I see tbody used periodically at work, most of the
time it is used incorrectly. Most of /that/ time the dev doesn't know
why it was used or know what that tag does.

--
Ryan E. Benson


On Mon, Jul 23, 2012 at 12:15 PM, Glenda Sims < <EMAIL REMOVED> > wrote:
> Hey Gang,
>
> I'll admit. I don't use scope or colgroup when creating accessible data
> tables. If I'm in a one dimensional data table, I just use the appropriate
> <th> tags to mark up all my table headers. I do the same thing if I'm in a
> two dimensional data table, just use <th> to mark up headers.
>
> When I'm in a complex data table, I still use <th> where appropriate, but
> also add explicit associations for each data cell to the appropriate header
> using the id and header attributes.
>
> So, my question is...when advising people on accessible data tables, is
> there ever an accessibility reason for using colgroup or rowgroup? I
> understand theoretically colgroup and rowgroup add some delicious
> semantics...but does any form of assistive technology use that for the
> benefit of people with disabilities.
>
> Love,
> the every curious Goodwitch
> (also known as Glenda Sims)
>
> --
> glenda sims | deque.com | 512.963.3773
>
> *web for everyone. web on everything.* - w3 goals
> > >