Re: heading elements (h#) in tables? [SEC=UNCLASSIFIED]

That's generally my suggestion: Review the complex table and ask yourself whether you haven't essentially fused several simpler tables. If so, break them apart. As Andrew notes, that makes life easier on everyone!

Cliff



________________________________
From: "Arch, Andrew" <Andrew.Arch@finance.gov.au>
To: Sailesh Panchang <sailesh.panchang@deque.com>; Léonie Watson <lwatson@nomensa.com>
Cc: Harry Loots <harry.loots@ieee.org>; Jeff Orchard <porch@sympatico.ca>; "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Sent: Wednesday, September 28, 2011 5:11 PM
Subject: RE: heading elements (h#) in tables? [SEC=UNCLASSIFIED]

What about the solution of simplifying the complex table into three separate smaller tables? I know the accountants often don't like this but it also makes it easier to see the sections for sighted people as the programs are separated out more clearly. The captions could be "Academic Missions budget allocation 2007-2008" etc and then I suspect we all gain.

Andrew

-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf Of Sailesh Panchang
Sent: Wednesday, 28 September 2011 11:43 PM
To: Léonie Watson
Cc: Harry Loots; Jeff Orchard; w3c-wai-ig@w3.org
Subject: Re: heading elements (h#) in tables?

In large complex data tables, h<n> tag may help navigation. Screen
reader users may navigate to various segments of the table and then
use regular table navigation to read through details. Header-id markup
cannot be avoided when colspan / rowspan is used to associate data
cells with header cells. The h<n> tag may help one comprehend the
overall table structure. Again the h<n> numbering cannot and must not
be used for column headers  or to group columns. It may be useful for
grouping data rows.
A well written table summary attribute will also help. Sometimes major
sections within the table may also be numbered like:
"I. Operating Expenses"
"II. Administrative and Selling Expenses"
Such numbering helps everyone.
Sailesh Panchang
Deque Systems

On 9/28/11, Léonie Watson <lwatson@nomensa.com> wrote:
> Harry Loots wrote:
> "it seems to me that the table has been structured incorrectly, and hence
> the reading of columns, all belong to one header.
> The Header "State Revenue" for example, should span the rows, as opposed to
> the columns, then the correct column names will be associated with the data.
> Using Headings, will not remove the confusion."
>
>     I believe that introducing headings in this context would confuse the
> situation. The accepted order of content is a heading, followed by some
> content. Adding headings into the table header would break this convention
> from a screen reader user's perspective.
>
>
> Regards,
> Léonie.
>
> --
> Nomensa - humanising technology
>
> Léonie Watson, Director of Accessibility & Web Development
>
> tel: +44 (0)117 929 7333
> twitter: @we_are_Nomensa @LeonieWatson
>
>
>
>
> ________________________________
> From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf
> Of Harry Loots
> Sent: 28 September 2011 13:42
> To: Jeff Orchard
> Cc: w3c-wai-ig@w3.org
> Subject: Re: heading elements (h#) in tables?
>
> Hi Jeff
> it seems to me that the table has been structured incorrectly, and hence the
> reading of columns, all belong to one header.
>
> The Header "State Revenue" for example, should span the rows, as opposed to
> the columns, then the correct column names will be associated with the data.
> Using Headings, will not remove the confusion.
>
>
> Kind regards
> Harry
>
>
>



________________________________

Finance Australian Business Number (ABN):   61 970 632 495    
Finance Web Site:   www.finance.gov.au    

IMPORTANT:

This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information. If you are not the intended recipient, you are notified that any use or dissemination of this communication is strictly prohibited. 
If you have received this transmission in error, please notify us immediately by telephone on 61-2-6215-2222 and delete all copies of this transmission together with any attachments. 
If responding to this email, please send to the appropriate person using the suffix .gov.au. 

________________________________