RE: About ccategory- simple data tables with one header

On the other hand: it depends on what “the rest of the row” means. The quote refers to table directionality, but as “see also the section on table directionality”.

This example seems to say scope=row applies to the left and right of the designated column:

“By using the row value for scope assigns the header cells in the second column to data cells on the left and the right of the individual header cell.”

http://www.w3.org/WAI/tutorials/tables/two-headers/#table-with-an-offset-column-of-header-cells


An example at http://www.w3.org/TR/1999/REC-html401-19991224/struct/tables.html#adef-scope says “Note the value "col" for the scope<http://www.w3.org/TR/1999/REC-html401-19991224/struct/tables.html#adef-scope> attribute, meaning "all cells in the current column". However, the example uses scope=row in the first column, so It’s unclear.

Allen Hoffman
Deputy Executive Director
The Office of Accessible Systems & Technology
Department of Homeland Security
202-447-0503 (voice)
allen.hoffman@hq.dhs.gov<mailto:allen.hoffman@hq.dhs.gov>

DHS Accessibility Helpdesk
202-447-0440 (voice)
202-447-0582 (fax)
202-447-5857 (TTY)
accessibility@dhs.gov<mailto:accessibility@dhs.gov>

This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain sensitive and legally privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited.  If you have received this message in error, please reply immediately to the sender and delete this message.  Thank you.

From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
Sent: Wednesday, July 01, 2015 10:18 AM
To: Eric Eggert
Cc: w3c-wai-gl@w3.org
Subject: RE: About ccategory- simple data tables with one header

Eric,

Ø  Do you know if this behavior is consistently supported in browsers and assistive technologies?
I can’t speak to your other questions but I did test with JAWS and IE and NVDA with Firefox and IE and the row header was NOT announced for cells to the left of the row header per the specification when using alt+control+up and down arrow keys.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
Phone 703.637.8957
Follow us: Facebook<http://www.facebook.com/#!/ssbbartgroup> | Twitter<http://twitter.com/#!/SSBBARTGroup> | LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog> | Newsletter<http://eepurl.com/O5DP>

From: Eric Eggert [mailto:ee@w3.org]
Sent: Wednesday, July 01, 2015 10:04 AM
To: Jonathan Avila
Cc: w3c-wai-gl@w3.org
Subject: Re: About ccategory- simple data tables with one header


Hi Jonathan,

On 1 Jul 2015, at 15:12, Jonathan Avila wrote:

[…]

Also of confusion in the tutorial is the use of scope in examples with ids and headers. There is no advice on whether use of scope alongside ids and headers is wrong or required.
http://www.w3.org/WAI/tutorials/tables/multi-level/

The tutorial also incorrectly states "By using the row value for scope assigns the header cells in the second column to data cells on the left and the right of the individual header cell." When in fact it only applies to the right in LTR languages.

Direct link to the example: http://www.w3.org/WAI/tutorials/tables/two-headers/#table-with-an-offset-column-of-header-cells


Thanks for pointing that out, I wasn’t aware of this behavior. One always learns new things :-)

Do you know if this behavior is consistently supported in browsers and assistive technologies?

Am I right that the behavior that the tutorial wants to archive would only be possible with by creating a rowgroup for every row (using multiple tbodys) and using scope="rowgroup"?

[…]

</tbody>

<tbody>

  <tr>

    <td>215</td>

    <th scope="rowgroup">Abel</th>

    <td>5</td>

    <td>2</td>

    <td>0</td>

    <td>0</td>

    <td>0</td>

    <td>3</td>

  </tr>

</tbody>

<tbody>

[…]

This strikes me as pretty clumsy and unintuitive…

Best,
Eric

--

Eric Eggert
Web Accessibility Specialist
Web Accessibility Initiative (WAI) at Wold Wide Web Consortium (W3C)