WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Sailesh Panchang
Date: Jul 24, 2012 9:01AM

Using headers-id is no different from using aria-labelledby with id.
JAWS supports both in IE and FF but NVDA supports neither in IE.
In fact NVDA works better in FF with headers-id.
Also NVDA supports scope only in FF but not IE.
JAWS has the most robust support for scope.
See H63 of WCAG 2.
The example-1 and description beginning with 'For simple data tables
where ...' is what I had authored.
Also see resource#3 that I had co-authored. The last table corresponds
to the code under example-1 for H63.
Table#1 of that resource is a complex table.
Sailesh Panchang


On 7/23/12, Ken Petri < <EMAIL REMOVED> > wrote:
> Howdy Glenda,
>
> I know JAWS understands headers-id associations, but NVDA and VoiceOver
> (Mac and iOS) seem not to (they do understand scope). Not sure about
> Window-Eyes. So, headers-id associations, while the technically correct way
> to show multiple associations between a data cell and headers, may not
> deliver a uniform experience, something that users might want to know
> about. I suppose you could get creative in complex tables and use
> aria-labelledby, since there is pretty wide support for aria-labelledby....
>
> I always use scope with THs to avoid ambiguity. Just seems like the safest
> thing to do.
>
> And I had the exact same question about scope="rowgroup" or "colgroup." I
> have not experimented to see if screen readers are grokking those, but I'm
> ginning up some tests.
>
> ken
> > > >