W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2009

Minutes WCAG 10 September 2009

From: Michael Cooper <cooper@w3.org>
Date: Fri, 11 Sep 2009 15:39:47 -0400
Message-ID: <4AAAA783.7000500@w3.org>
To: List WAI GL <w3c-wai-gl@w3.org>
Minutes of the 10 September 2009 WCAG meeting are posted to
http://www.w3.org/WAI/GL/2009/09/10-wai-wcag-minutes and copied below
(for Trackbot's use).


  Web Content Accessibility Guidelines Working Group Teleconference


    10 Sep 2009

See also: IRC log <http://www.w3.org/2009/09/10-wai-wcag-irc>


    Attendees

Present
    Bruce_Bailey, Loretta_Guarino_Reid, Andrew_Kirkpatrick,
    Ben_Caldwell, sofia_celic, Andi_Snow-Weaver, Tim_Boland,
    Gregg_Vanderheiden
Regrets

Chair
    Loretta Guarino Reid
Scribe
    greggvanderheiden


    Contents

    * Topics <http://www.w3.org/WAI/GL/2009/09/10-wai-wcag-minutes#agenda>
         1. Issue 2762 - G53: Example 2 (edit)
            <http://www.w3.org/WAI/GL/2009/09/10-wai-wcag-minutes#item01>
         2. Issue 2761 - SCR35: Example 3 (edit)
            <http://www.w3.org/WAI/GL/2009/09/10-wai-wcag-minutes#item02>
         3. Issue 2759 - H63: Why td for header cells? (edit)
            <http://www.w3.org/WAI/GL/2009/09/10-wai-wcag-minutes#item04>
         4. Issue 2758 - G182: Applicability (edit)
            <http://www.w3.org/WAI/GL/2009/09/10-wai-wcag-minutes#item05>
         5. Issue 2757 - G182: Examples (edit)
            <http://www.w3.org/WAI/GL/2009/09/10-wai-wcag-minutes#item06>
         6. Issue 2763 - G182: Example 3 (3rd bullet) (edit)
            <http://www.w3.org/WAI/GL/2009/09/10-wai-wcag-minutes#item07>
    * Summary of Action Items
      <http://www.w3.org/WAI/GL/2009/09/10-wai-wcag-minutes#ActionSummary>

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

<Loretta>
http://trace.wisc.edu/bugzilla_wcag/buglist.cgi?cmdtype=runnamed&namedcmd=Open%20Issues
<http://trace.wisc.edu/bugzilla_wcag/buglist.cgi?cmdtype=runnamed&namedcmd=Open%20Issues>



      Issue 2762 - G53: Example 2 (edit)

*RESOLUTION: Accept. Tell them we agree and will remove it.*


      Issue 2761 - SCR35: Example 3 (edit)

<Andi> if and only if the form post provides the same functionality as
the script.

<Andi> "This approach can be used TO CREATE sites that do not rely on
script, if and only if ...."

<Sofia> The action attribute of the enclosing form element sumbits the
form to the server which has a script to perform the action.

*RESOLUTION: evise "This approach can be used <del>by sites</del><ins>to
create sites</ins> that do not rely on script, if and only if the form
post provides the same functionality as the script."*

@@ delete "or will load a Web page that explains that JavaScript is
required to interact with the site. " from
http://www.w3.org/TR/WCAG-TECHS/working-examples/SCR35/jsbutton.html

@@ revise, "The action attribute of the enclosing form element submits
the form to the server which has a script to perform the action.


      Issue 2759 - H63: Why td for header cells? (edit)

*RESOLUTION: revise the cells with row="scope" to be <th>*

Respond with:

Technically, the presence of the scope attribute should be enough to
signal assistive technologies that these are header cells. However, we
agree that using <th> in this case is more appropriate and will revise
the example to use <th> for cells that have the scope attribute.


      Issue 2758 - G182: Applicability (edit)

<Loretta> Note that while this technique is sufficient to meet the
visual requirements of Success Criterion 1.4.1, the information conveyed
by the color must also be programmaticvally determined to satisfy
Success Criterion 1.3.1.

<Loretta> Note that while this technique is sufficient to meet the
visual requirements of Success Criterion 1.4.1, the information conveyed
by the color must also be available programmatically to satisfy Success
Criterion 1.3.1. See Understanding Success Criterion 1.3.1.

*RESOLUTION: RESPONSE: This technique is sufficient for this SC which is
just about colorblindness - but would not meet 1.3.1. To bring this to
the readers attention we added a note to end of description: Note that
while this technique is sufficient to meet the visual requirements of
Success Criterion 1.4.1, the information conveyed by the color must also
be available programmatically to satisfy Success Criterion 1.3.1. See
How To*

Meet Success Criterion 1.3.1.


      Issue 2757 - G182: Examples (edit)

<Ben> first half of issue is
http://lists.w3.org/Archives/Public/public-comments-wcag20/2009Aug/0039.html


RESOLUTION 1: For Bullet #2 and #3 we will change text to read: A news
site lists links to the articles appearing on its site. Additional
information such as the section the article appears in, the time the
article was posted, a related location or an indication that it is
accompanied by live video appears in some cases. The Links to the
articles are in a different color than the additional information but
the links are not

underlined, and each link is presented in a larger font than the rest of
the information so that users who cannot see color can identify the
links more easily.

Resolution 2: For bullet #3 change to: Short news items sometimes have
sentences that are also links to more information. Those sentences are
printed in color (without underline) and use a sans-serif font face
while the rest of the paragraph is in black Times-Roman.

Resolution 3: Add a new bullet example in front of #1 that reads: The
default formatting for links on a page includes have the links be both
in a different color than the other text on the page and is also
underlined to make the links identifiable even without color vision.


      Issue 2763 - G182: Example 3 (3rd bullet) (edit)

*RESOLUTION: Response: The applicability section mentions some common
examples where authors use color to convey information. The example
describes an additional option where a sentence at the end of a
paragraph is a link to additional details.*

G182 is about the use of color. If the link were underlined, you are
correct that the underlined link text would be sufficient.

However, screen readers announce the presence of links (or play a sound
to indicate their presence). Therefore, there would be no confusion
about the fact that the sentence is a link.

We have revised the example as follows:

A news page includes short short descriptions of articles followed by
links (without underlines) to the full story. The links are presented in
color and also use a sans-serif font face while the rest of the
paragraph is in black Times-Roman so that users who can not identify the
color difference can still see that there is a difference between the
article description and the link


    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: 2009/09/11 19:38:29 $


-- 

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, 11 September 2009 19:40:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:57 GMT