W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > July 2013

Incorrect recommendation for dealing with List Elements in tagged PDF

From: <noreply@w3.org>
Date: Tue, 23 Jul 2013 14:36:34 +0000
Message-Id: <E1V1dha-0001LE-E4@crusher.w3.org>
To: public-comments-wcag20@w3.org
Name: Jonathan Metz
Email: jonathanmetz@gmail.com
Affiliation: User
Document: TD
Item Number: PDF21
Part of Item: Examples
Comment Type: technical
Summary of Issue: Incorrect recommendation for dealing with List Elements in tagged PDF
Comment (Including rationale for any proposed change):
The page suggests that using the list button on the ribbon as the "easiest way to ensure that lists are formatted correctly when they are converted to PDF". It doesn't actually, since Word throws the label element in with the <Lbody> in the tag tree whenever one exports a list from Word. The user always has to edit those elements in the tag tree later. It even goes so far as to show screenshots of what happens when you do that. 

It provides the List Elements at the beginning of the technique, but fails to show the relevant usage for implementing them. 

It provides no information about dealing with unordered lists or how such labels for them are optional.

It also does not clearly explain how a list is should appear properly structured.

Proposed Change:
1. Show how lists are properly structured.
2. Explain which tags are optional for which list type (ordered must be labeled, unordered is optional) and which tags are mandatory.
3. Show how to properly adjust tags in PDF to create said list first without the use of proprietary means (i.e. from Word/InDesign/etc).
4. Change text from " the easiest way to ensure that lists are formatted correctly when they are converted to PDF" to "easiest way to ensure that THE BASIS for list STRUCTURE is formatted correctly when they are converted to PDF."
5. Provide examples for how to fix the incorrect placement of the tags after exporting from Word (as the example writer)
Received on Tuesday, 23 July 2013 14:36:39 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 14 July 2018 08:34:47 UTC