RE: Tables: Does scope="col" Stop When A Row Spans Multiple Columns?

Hi,
The table I looked at was in a PDF. JAWS spoke the headers correctly when I moved from left to right. It spoke the whole column down to the cell I landed on when I moved from right to left. So, if I was in row six, it read all five cells above where I looked, and if I was in row nine, it read the first eight cells, then the one I landed on. Could there be some other problem?

Thanks.

Jim



-----Original Message-----
From: Roger Hudson [mailto:rhudson@usability.com.au] 
Sent: Tuesday, August 13, 2013 4:28 PM
To: 'Duff Johnson'; w3c-wai-ig@w3.org
Subject: RE: Tables: Does scope="col" Stop When A Row Spans Multiple Columns?

Some years ago I checked how well several screen readers used scope and
found with "rows" the results were not good, and only just OK with "col".
Does anyone have any recent results of testing HTML data tables with screen
readers, and in particular with complex tables that have more than one level
of column and/or row headers?

Thanks,

Roger

-----Original Message-----
From: Duff Johnson [mailto:duff@duff-johnson.com] 
Sent: Wednesday, 14 August 2013 5:06 AM
To: w3c-wai-ig@w3.org
Subject: Re: Tables: Does scope="col" Stop When A Row Spans Multiple
Columns?

Jim,

- Headers with a scope of "col" are column headers
- Headers with a scope of "row" are row headers
- Cell can span rows or columns up to the maximum number of rows or columns
in the table.

If the table may be fully executed using the above you don't need to use
IDs.

Does that help?

Duff.

On Aug 13, 2013, at 2:02 PM, "Homme, James" <james.homme@highmark.com>
wrote:

> Hi,
> I have a table in which the heading cells all have scope="col", but the
table has some rows that span across the whole table. What is the expected
behavior for this situation? Should I consider using the headers and id
attributes to get proper reading if something doesn't work?
>  
> Thanks.
> 
> Jim
>  
>  
> 
> 
> This e-mail and any attachments to it are confidential and are intended
solely for use of the individual or entity to whom they are addressed. If
you have received this e-mail in error, please notify the sender immediately
and then delete it. If you are not the intended recipient, you must not
keep, use, disclose, copy or distribute this e-mail without the author's
prior permission. The views expressed in this e-mail message do not
necessarily represent the views of Highmark, its diversified business, or
affiliates.

Received on Wednesday, 14 August 2013 12:40:42 UTC