Word doesn’t do Section 508, PDF gets the blame

Editor’s Note:
Duff Johnson is the CEO of Appligent Document Solutions. This article originally appeared on Appligent.com, and has been reprinted with permission.

So, you think PDF is a problem when it comes to accessibility and Section 508 compliance? Let’s talk about that expensive and widely used word-processing software known as Microsoft Word.

Word appears unaware of Section 508 requirements for tables. In Word, column heading cells occur only when an option to repeat headings on following pages is selected. There’s no way in Word to create row headings, no way to manage multilevel headings and no way to set the scope of heading cells.

Microsoft may be unaware that Word is unaware of these requirements, since in their VPAT for Word 2007 Microsoft claims — erroneously — that Word supports paragraphs (g) and (h) of the Section 508 regulations which require, among other things, row headings in tables.

So why expect that a PDF made from Word will do any better?

Logical structure information has to come from somewhere. PDF has no inherent concept of words, sentences, lines or paragraphs for a variety of extremely good reasons we’ll discuss some other time.

PDF can include mechanisms that allow the document’s logical structure to be represented in addition to the contents. When a Word file is converted to PDF using capable software and the correct settings, structure information from the source is conveyed into the resulting PDF file.

However, to the extent that the authoring application is itself unaware of accessibility requirements, the newly-created PDF is less likely to be accessible as-created, and must be corrected after-the-fact.

src=’http://www.planetpdf.com/images/articles/Duff_Johnson/Word_doesnt_do_Section_508/1-DJ_Word_doesnt_do_Section_508_-_tags-table.jpg’ width=’348′ height=’197′
alt=’Screen-shot of table tags represented in a grid.’>

You May Also Like

About the Author: Duff Johnson

Leave a Reply