W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2010

Minutes WCAG 18 November 2010

From: Michael Cooper <cooper@w3.org>
Date: Fri, 19 Nov 2010 09:02:24 -0500
Message-ID: <4CE68370.7000203@w3.org>
To: List WAI GL <w3c-wai-gl@w3.org>
Minutes of the 18 November 2010 WCAG meeting are posted to
http://www.w3.org/2010/11/18-wai-wcag-minutes and copied below.


  Web Content Accessibility Guidelines Working Group Teleconference


    18 Nov 2010

Agenda <http://lists.w3.org/Archives/Public/w3c-wai-gl/2010OctDec/0047.html>

See also: IRC log <http://www.w3.org/2010/11/18-wai-wcag-irc>


    Attendees

Present
    Mary_Utt, Andrew_Kirkpatrick, Bruce_Bailey, David_MacDonald,
    Michael_Cooper, James_Nurthen, Loretta_Guarino_Reid, Adam_Solomon,
    Wolf_Schmidt, Marc_Johlic, Tim_Boland
Regrets

Chair
    Loretta_Guarino_Reid 
Scribe
    David


    Contents

    * Topics <http://www.w3.org/2010/11/18-wai-wcag-minutes#agenda>
         1. PDF Techniques Roadmap
            <http://www.w3.org/2010/11/18-wai-wcag-minutes#item01>
         2. 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
            <http://www.w3.org/2010/11/18-wai-wcag-minutes#item02>
         3. 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
            <http://www.w3.org/2010/11/18-wai-wcag-minutes#item03>
         4. Sufficient PDF Technique for SC 3.3.1, 3.3.3, 3.3.4:
            Providing form validation and error prevention in PDF forms
            <http://www.w3.org/2010/11/18-wai-wcag-minutes#item04>
         5. <Loretta>
            http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html
            <http://www.w3.org/2010/11/18-wai-wcag-minutes#item05>
         6. 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
            <http://www.w3.org/2010/11/18-wai-wcag-minutes#item06>
         7. 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
            <http://www.w3.org/2010/11/18-wai-wcag-minutes#item07>
         8. Sufficient PDF Technique for SC 1.3.1, 2.4.3: Making tables
            accessible in PDF documents by using table elements
            <http://www.w3.org/2010/11/18-wai-wcag-minutes#item08>
         9. Parsing Text-Format Text Captions for MediaElement Content
            <http://www.w3.org/2010/11/18-wai-wcag-minutes#item09>
    * Summary of Action Items
      <http://www.w3.org/2010/11/18-wai-wcag-minutes#ActionSummary>

------------------------------------------------------------------------

<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


    Summary of Action Items

[End of minutes]
------------------------------------------------------------------------
Minutes formatted by David Booth's scribe.perl
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm>
version 1.133 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2010/11/19 14:01:05 $


-- 

Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org <mailto:cooper@w3.org>
Information Page <http://www.w3.org/People/cooper/>
Received on Friday, 19 November 2010 14:02:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 19 November 2010 14:02:49 GMT