WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Use of Headings


From: Karlen Communications
Date: Jul 27, 2010 10:45AM

I completely agree!

One of the problems with using tables for layout is that they are often not
retained as inserted. For example a document author might start off with a 6
column table and then adjust the number of columns to fit the content...not
data table content...and what ends up happening is that part of the table
used for layout is converted to a data table inappropriately while other
pieces of the table aren't.

What this means for someone using a screen reader is that content that
doesn't seem to fit a table structure is plunked into one. This affects
comprehension and readability and is very confusing.

Cheers, Karen

-----Original Message-----
[mailto: <EMAIL REMOVED> ] On Behalf Of Duff Johnson
Sent: July-27-10 12:22 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Use of Headings

> Does the use of table structures for layout trouble screen reader users?

The fact that table-tools were used to author the document should not be
taken to imply that tables should be represented in the document's tags.
Semantics should always trump the machine output.

> I'm seeking advice on the best way to work with the Acrobat tag tree in
this document.
> Logically, the tags should be : <h1>, <h2>, followed by several <p>
> and an <L>. Then another <h2>, followed by several <p> and an <l> tags.

Then tag it that way, replacing the "detritus" table tags left over from the
PDF's creation.

> But because she used a layout table, these tags end up nested in various
table tags.

Yes... so the tags in the PDF as-created are incorrect and must be edited in

> Should I modify the physical structure to reflect the logical
> structure of the document? Or leave the various table tags in the

Modify the logical structure in the PDF to match the semantics of the


Duff Johnson
Appligent Document Solutions