WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Complex tables: Scope AND id and header attributes

for

From: Sailesh Panchang
Date: Oct 26, 2015 10:28AM

In my experience, if headers-id is used, the scope is redundant and
serves no real purpose. Every data cell clearly conveys which header
cells are associated with it when one uses headers-id.
Skip the step for scope and try reading a table tagged only with
headers-id with a screen reader. It should work fine.
Thanks and regards,
Sailesh Panchang


On 10/26/15, Dona Patrick < <EMAIL REMOVED> > wrote:
> Thanks for your responses. My question stemmed from being required to use
> both scope AND id and header attributes/arrays in complex tables on a PDF
> file. The PDF files have tables that have headers two-levels of headers,
> one of which spans multiple columns. The resource used was from the VA (
> http://www.section508.va.gov/support/tutorials/pdf/Creating_Accessible_PDF_Tutorials_with_Acrobat_XI.pdf)
> (page 47 - 51).
>
> I'm going to follow the directions they gave and not argue, but I wanted
> the opinion of the group and wanted to make sure that when I DON'T use both
> I am still doing it correctly.
>
> Thanks again!
>
> Dona
>
>
>
> On Fri, Oct 23, 2015 at 5:07 PM, Moore,Michael (Accessibility) (HHSC) <
> <EMAIL REMOVED> > wrote:
>
>> On the PDF side you only need to use header and id in the following
>> circumstances.
>>
>> 1. You have headers on the diagonal.
>> 2. You have headers that span multiple rows. - Row span and scope does not
>> seem to get you what it should.
>>
>> Mike Moore
>> Accessibility Coordinator
>> Texas Health and Human Services Commission
>> Civil Rights Office
>> (512) 438-3431 (Office)
>>
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf Of Birkir R. Gunnarsson
>> Sent: Friday, October 23, 2015 4:01 PM
>> To: WebAIM Discussion List
>> Subject: Re: [WebAIM] Complex tables: Scope AND id and header attributes
>>
>> Hi
>>
>> I would avoid headers/id by now (in html), it is being sunsetted and its
>> support by assistive technologies is no better than that of the
>> replacement
>> techniques.
>> Also, you can no longer use the scope attribute on td cells, you must use
>> them on header (th or td with role="columnheader" or "rowheader") cells.
>> If you want to indicate that a single row- or column header spans multiple
>> rows or columns, sue the rowspan or colspan attribute with
>> scope="rowgroup"
>> or "colgroup".
>> E.g.
>> This header cel is header for two columns:
>> <th colspan="2" scope="colgroup">Phone numbers</th>
>>
>> and this is a header for two rows:
>> <th rowspan="2" scope="rowgroup">My contact info</th>
>>
>> Colgroup is decently supported on Windows, but support for rowgroup is
>> somewhat buggy, though getting better.
>> Voiceover (ioS 9.1) does not yet support colgroup properly. It will
>> announce the multi-column header, but does not announce the individual
>> column headers.
>> if you had this:
>> <table>
>> <tr>
>> <th colspan="2" scope="colgroup">Phone numbers</th> </tr> <tr> <th
>> scope="col">Personal</th> <th scope="col">Business</th> </tr> <tr>
>> <td>919 999 9999</td>
>> <td>919777 8797</td>
>> </tr>
>> </table>
>>
>> If you go into the first td cell using table navigation in Jaws or NVDA,
>> they would read:
>> Phone numbers, personal, 919 999 9999
>> Voiceover (on iOS) reads:
>> Phone numbers 919 999 9999.
>> hth
>> -Birkir
>>
>>
>>
>> On 10/23/15, Dona Patrick < <EMAIL REMOVED> > wrote:
>> > I recall being told by someone or reading somewhere that one should
>> > not use both Scope AND id and header attributes in complex tables. I
>> > don't recall if this was HTML or PDF.
>> >
>> > Has anyone else heard this? Is it true or was it misinformation?
>> >
>> > Thanks,
>> >
>> > Dona
>> > >> > >> > archives at http://webaim.org/discussion/archives
>> > >> >
>>
>>
>> --
>> Work hard. Have fun. Make history.
>> >> >> at http://webaim.org/discussion/archives
>> >> >> >> >> >>
> > > > >