Web Content Accessibility Guidelines Working Group Teleconference

<trackbot> Date: 18 November 2010

PDF Techniques Roadmap

no resolution necessary on PDF Roadmap ... internal doc

Sufficient PDF Technique for SC 2.2.1, 2.2.3: Allowing time limits to be disabled or modified via scripting for interactions with PDF forms

Resolution: technique redundant and general so will drop Sufficient PDF Technique for SC 2.2.1, 2.2.3: Allowing time limits to be disabled or modified via scripting for interactions with PDF forms

Sufficient PDF Technique for SC 1.3.1, 2.4.6, 3.3.2, 4.1.2: Adding interactive controls to forms in PDF documents

<AWK> http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/H91

Resolution: Sent back for more work on Topic: Sufficient PDF Technique for SC 1.3.1, 2.4.6, 3.3.2, 4.1.2: Adding interactive controls to forms in PDF documents

Sufficient PDF Technique for SC 3.3.1, 3.3.3, 3.3.4: Providing form validation and error prevention in PDF forms

<Loretta> Michael?

<Loretta> http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-identified.html

<AWK> New text? The objective of this technique is to validate user input as values are entered for each field. If errors are found, an alert dialog describes the nature of the error in text. NOTE: Once the user dismisses the alert dialog, it may be helpful if the script positions the keyboard focus on the field where the error occurred, although some users may expect the focus to remain on the last control focused prior to the alert appearing. Authors should exerc

<AWK> (that's for you to look at, Michael) :)

<AWK> Authors should exercise care to ensure that any movement of the focus will be expected (e.g. If the alert announces an error in a phone number field, positioning the focus on that field when the alert is dismissed can be regarded as helpful and expected).

<AWK> :) Example 2, first sentence

<AWK> http://trace.wisc.edu/wcag_wiki/index.php?title=Providing_form_validation_and_error_prevention_in_PDF_forms

Resolution: More editorial work, possibly splitting it into two Sufficient PDF Technique for SC 3.3.1, 3.3.3, 3.3.4: Providing form validation and error prevention in PDF forms

<Loretta> http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html

Sufficient PDF Technique for SC 2.4.4, 2.4.9, 3.2.4: Providing links and link text using the /Link structure element in PDF documents

Resolution: Accept as amended Sufficient PDF Technique for SC 2.4.4, 2.4.9, 3.2.4: Providing links and link text using the /Link structure element in PDF documents

Sufficient PDF Technique for SC 1.3.1, 2.4.6, 3.3.2, 4.1.2: Adding labels to form controls in PDF documents

Sufficient PDF Technique for SC 1.3.1, 2.4.6, 3.3.2, 4.1.2: Adding labels to form controls in PDF documents

Resolution: Leave open for revision Sufficient PDF Technique for SC 1.3.1, 2.4.6, 3.3.2, 4.1.2: Adding labels to form controls in PDF documents

Sufficient PDF Technique for SC 1.3.1, 2.4.3: Making tables accessible in PDF documents by using table elements

Resolution: Leave open for editing Sufficient PDF Technique for SC 1.3.1, 2.4.3: Making tables accessible in PDF documents by using table elements
... Accept as proposed Sufficient Silverlight Technique for SC 3.3.1, 3.3.3, 3.3.4: Using the Validation and ValidationSummary APIs to Implement Client Side Forms Validation in Silverlight

Parsing Text-Format Text Captions for MediaElement Content

Resolution: Leave open for editing Parsing Text-Format Text Captions for MediaElement Content

<MichaelC> scribe: David

<MichaelC> trackbot, end meeting