2006-118 Meeting Minutes

Return to Meetings 

PDF-UA 2006-118
May 31, 2006

PDF/UA Working Group Meeting Minutes

Teleconference

PDF/UA (Universal Accessibility) Working Group Draft Meeting Agenda
Wednesday, May 31, 2006,  3:00 P.M. - 5:00 P.M. EST
Conference Call Information
International Dial-in: +1-303-928-2600
U.S. Dial-in: 1-888-742-8686
Conference ID: 7083945

NOTE:  All attending members should load the PDF/UA page.
We'll be working "live" throughout the meeting!

 

Attendees

Duff Johnson DJ - Chair Document Solutions
Karen McCall KM - Karlen Communications
Joe Clark JC- Independent Accessibility Consultant
Loretta Guarino-Reid LGR - Adobe Systems
Mark Gavin MG - Appligent
Greg Pisocky GP - Adobe Systems
Neil Soiffer NS – Design Sciences
Ferass El Rayes - FER - Netcentric Technologies
Nick Braven - NB Dolphin

Approval of the Agenda

Gavin / LGR

Approval of Previous Minutes

Postpone final approval of minutes upon verification of action items....

GP / LGR

Introduction of New Participants

Ferass El Rayes VP Product development at Netcentric. Ottawa plug-in testing and remediation of PDF against Section 508.

Nick Braven Dolphin –

Action Items from previous meetings

AI Draft List:

Update Wiki contacts in PDF Roster Page

Find Duff’s meta data page – compliant PDF files shall have meta data. Author meta data perhaps not required, but title meta data must be provided

AI Org and Use Fonts – GP not complete date updated. Communications from the Netherlands

AI Character sets – Unicode DJ – still in process

AI Convince other members – ongoing

AI Report on response form – Complete JC

AI GP to post email into the minutes.

AI deleted duplicate

AI – Javascript – Ferass if it affects accessibility Javascript in forms.

AI – GP still trying to reach Lori

AI: GP Contact DOM scripting task force. JC web standards project Jeremy Keith, Dory Smith Javacript DOM scripting task force to obtain some insight.

AI: RH meta data – deferred to 6/21

AI: LGR – deferred to 6/21

AI: LGR Annotation brain storming. Links, movies form fields and custom annotations. Annotations need not be interactive but they are. Thought of as a separate layer sitting atop the page. They can be in the tag order. Spec compliant tagged PDF could have annotations that are not in the tag order. Certain classes of annotations have to be in the tag order. One class is deep and wide another category, boxes, another category form fields.  Distinction between annotation types, comment variety and content variety. Form fields have to be. We should work on the “musts” first. As a result, would it be possible to include both types.

Proposal: JC Can someone look at the spec and determine if there are indeed 2 categories or more and establish a priority list for these categories. The most urgent may result in remediation for all.

Some instances are more problematical, for instance 3D art. Or we may exclude custom annotations for instance. They can be included but they are not documented for accessibility. This remains an extensive area for discussion.

Of course, one of the things we might want to support is MathML which might have to  be implemented as an annotation, so there is a danger in “locking down” certain types of annotations.

AI: DJ Brainstorm issues around annotations. Categorize and prioritize. Also specify as important. Forms, links, multimedia, 3D art, comments, custom annotations. Review list, determine what’s missing.

AI: XFA Forms Spec GP to obtain

AI: Ensure XFA represented in the draft spec

Proposal: DJ: Note this is an issue to be noted in the working draft as a pending item.

AI: LGR Complete

AI: Subsection for assignments, edit page

AI: Review tag set options lack of clarity.

AI: 2005 Annual Report Complete

Content in our Draft Specification

Group will examine the spec and review with what Loretta has done.

Proposal: MG: Adopt the following naming convention. Use the term Reference to refer to the PDF Reference version 1.6 and use the term “spec” or “specification” when referring to the PDF/UA specificiation. 

Viability section. Optimal, Required, encoding information that is required to play multimedia. There is nothing in the section that PDF/UA needs to speak to. We will have to address this issue by referring to external specifications and standards. Is this the place to record the issue concerning the accessibility of players. What we are really talking about user agents, renditions. The information that is in the PDF is there to tell you what player is viable.

Somewhere the accessibility of media players will have to be discussed in this specification.

Media Clip Objects – changed from delete since this is where the alt parameter is defined to provide alt descriptions for clip objects that need it defined. We would probably require this.

Play Parameters – duration, sizing, behavior and form factor of media openings. This is a page we need to keep.

Renditions:

Renditions

Goal: make sure that multimedia annotations provide, at least optionally, captions, audio descriptions, audio overdubs, and subtitles (where appropriate for accessibility). Overdubs and subtitles are now removed.
* Do we need all of these? (WCAG only addresses captions and audio descriptions) The provisions can match what WCAG has. Sign language considerations.
* Can we tell when they are needed? There are edge cases when they are not. Best approach is yes, you must unless there is a compelling reason not to.
AI: JC to determine which get must, and which get shalls. JC to consult with the audio description mailing list to determine which categories of video will require shall, must, should, may, etc... One list to be developed for description and one to be developed for captioning.  6/21/2006.
 * Do we need different conformance levels for this different augmentations?  Built into the genre.
* Need to sort out interaction with MH (must honor) and BE (best effort) dictionaries. Also see note in Table 9.2 (of the PDF 1.6 Reference) Contains only 1 key, the media criteria dictionary. MH (Must have dictionaries) Must be honored for a rendition to be viable. Absolute requirements into MH dictionaries. BE for optimal. Relevant example. As a best effort you should be showing captions, though if you cannot show the captions then its okay to play. If on the other hand, you wanted to stipulate that if you cannot show the captions, then you cannot play then the item should go into the MH dictionary. All related to viability. Open the reference. Need to come up with some high level direction. FE suggests using the WCAG implementation of multimedia in the same way HTML has done it.  Nothing to be said about the must honor best effort dictionaries. Frame the requirement into the content level discussion.
The selector rendition for a multimedia annotation contains media renditions.
* At least one media rendition must have a media criteria dictionary containing the value true for the A key (audio description).
* At least one media rendition must have a media criteria dictionary containing the value true for the C key (captions).
* At least one media rendition must have a media criteria dictionary containing have the value true for the O key (audio overdubs).
* At least one media rendition must have a media criteria dictionary containing have the value true for the S key (subtitles).

Media Screen Parameters

Are these items exposed? Is it a problem if they are not exposed?  Example a certain application launches 2 windows. One is announced by screen reader, other is not. Not aware it’s there. Issues regarding obtaining focus and providing notification for their presence.

AI: KM to develop some thoughts regarding multi media presentation in PDF 6/21.

AI: DJ and KM: Generate samples of Multi media PDFs with media in different locations.

Wrap and Close

Next meeting, June 21, 2006 3:00 PM EST

Next face to face scheduled in Toronto. October 17 -18, 2006.

AI: FER edit a designated page (of his choice) of what “shall” or “shall not” statements should be posted. 

Increased traffic on the Wiki will generate increased interest.

Adjourn

Pisocky / Soiffer

Meeting ended 5:10 pm