W3C

Web Content Accessibility Guidelines Working Group Teleconference

21 Apr 2011

Agenda

See also: IRC log

Attendees

Present
Mary_Utt, Michael_Cooper, Bruce_Bailey, Loretta_Guarino_Reid, Marc_Johlic, Wolf_Schmidt, James_Nurthen, David_MacDonald, Tim_Boland
Regrets
Chair
Loretta Guarino Reid
Scribe
Loretta

Contents


http://www.w3.org/2006/02/lc-comments-tracker/35422/NOTE-WCAG20-TECHS-20101014/2475

<jamesn_> <discussion of editing issues and status of drafts>

The Comments column explains how Acrobat Pro displays the corresponding information.

http://www.w3.org/WAI/GL/2011/WD-WCAG20-TECHS-20110310/PDF#pdf_notes

<David> The following list is not intended to by exclusive or exhaustive, but simply reflects our findings as of this writing. Also, it should be noted that these products *can* produce accessible PDF.

scribe: if used properly,

<David> As in HTML editors, meeting WCAG in PDF editors and generators depends upon meeting the Success Criteria.

Not all versions of these tools support accessible PDF. Check with tools vendors about the accessibility support in their product.

<David> In general newer tools provide better support than older ones

<Mary> http://trace.wisc.edu/wcag_wiki/index.php?title=PDF_Technology_Notes

<David> You can add Lotus Symphony Documents to the list of applications that can export accessibly tagged PDFs. Lotus Symphony is based on OpenOffice.org Technology and supports the ODF standard, ISO 26300: http://www-03.ibm.com/software/lotus/symphony/home.nsf/product_wpe

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2011/04/22 13:49:06 $