Minutes WCAG 03 May 2012

Minutes of the 3 May 2012 WCAG meeting are posted to
http://www.w3.org/2012/05/03-wai-wcag-minutes.html and copied below.


  Web Content Accessibility Guidelines Working Group Teleconference


    03 May 2012

Agenda <http://lists.w3.org/Archives/Public/w3c-wai-gl/2012AprJun/0055.html>

See also: IRC log <http://www.w3.org/2012/05/03-wai-wcag-irc>


    Attendees

Present
    Robin_Tuttle, David_MacDonald, Cooper, Andrew_Kirkpatrick, Alex_Li,
    Kathy, Bruce_Bailey, Loretta_Guarino_Reid, [Microsoft],
    Gregg_Vanderheiden
Regrets
Chair
    Loretta_Guarino_Reid
Scribe
    Kathy, David


    Contents

    * Topics <http://www.w3.org/2012/05/03-wai-wcag-minutes.html#agenda>
         1. LC-2607: Headings
            https://www.w3.org/2002/09/wbs/35422/20120419TF/results#x2607
            <http://www.w3.org/2012/05/03-wai-wcag-minutes.html#item01>
         2. LC-2607 : Headings
            <http://www.w3.org/2012/05/03-wai-wcag-minutes.html#item02>
         3. HTML5: Techniques for providing useful text alternatives
            <http://www.w3.org/2012/05/03-wai-wcag-minutes.html#item03>
    * Summary of Action Items
      <http://www.w3.org/2012/05/03-wai-wcag-minutes.html#ActionSummary>

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


      LC-2607: Headings
      https://www.w3.org/2002/09/wbs/35422/20120419TF/results#x2607

<Kathy> Finish up the discussion on headings

Does assistive technology handle a heading and a link?

It shows up in the heading list, David will check to see if it is in the
links list

Loretta suggests the following change: "WCAG only requires that the
markup reflect what what authored." -> "Success Criterion 1.3.1 requires
that if headings are used, they be marked up as headings. It does not
require that headings be used at all, or that they be used in any
particular way."

Question is how much is up to author

Area of judgement here


      LC-2607 : Headings

<awk> So long as the heading structures provided match the content,
there is no prohibition against an HTML page having multiple H1 heading
elements or not following a strict heirarchy of headings, nor any
similar prohibition for similar semantic structures in technologies
other than HTML.

<Loretta> WCAG does not require strict hierarchy in headings. It
recommends it but does not require it. Using two <h1> headings would not
violate any of the success criteria, so WCAG conformance would not
prohibit it. Success Criterion 1.3.1 requires that if headings are used,
they be marked up as headings. It does not require that headings be used
at all, or that they be used in any particular way. If the author used
heading level to emphasize the importance of a

<Loretta> hierarchically, the content can still meet WCAG, since
equivalent information is exposed to everyone.

<awk> WCAG does not require strict hierarchy in headings. It recommends
it but does not require it. Using two <h1> headings in an HTML document
would not violate any of the success criteria, so WCAG would not
prohibit it. Success Criterion 1.3.1 requires that if headings are in
the content that the relationships are conveyed programmatically.

<Loretta> http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/H69.html

<Loretta> Success Criterion 1.3.1 requires that if headings are used,
they be marked up as headings. It does not require that headings be used
at all, or that they be used in any particular way. If the author used
heading level to emphasize the importance of a topic, for instance, but
did not create sections hierarchically, the content can still meet WCAG,
since equivalent information is exposed to everyone.

<Loretta> Success Criterion 1.3.1 requires that if headings are in the
content that the relationships are conveyed programmatically.

Conclusion: Rewrite the response to state that 2 h1 headings does not
violate the success criteria so WCAG conformance would not prohibit it.
Include a reference to technique h69 and g141. Current screen readers
support navigation elments marked up as headings.
... Accepted as amended


      HTML5: Techniques for providing useful text alternatives

Example 6.1

<MichaelC> https://www.w3.org/2002/09/wbs/35422/20120503misc/results#xq1

Conclusion: Example is fine

Resolution: example 2.2, 6.1 ok

pure decoration

serving only an aesthetic purpose, providing no information, and having
no functionality

Note: Text is only purely decorative if the words can be rearranged or
substituted without changing their purpose.

Example: The cover page of a dictionary has random words in very light
text in the background.

Decoration, Formatting, Invisible: If non-text content is pure
decoration, is used only for visual formatting, or is not presented to
users, then it is implemented in a way that it can be ignored by
assistive technology.

<awk> As decisions about when to provide a text alternative are based on
context of use, both options are considered to be conforming, but it is
recommended that a brief text alternative is provided as what different
users may consider to be "pure decoration" and not necessary to
understand the content is somewhat subjective.

<MichaelC> *ACTION:* Bruce Bailey and David to provide recommended edits
to the group on “Techniques for providing useful text alternatives.”
[recorded in http://www.w3.org/2012/05/03-wai-wcag-minutes.html#action01]

<trackbot> Created ACTION-172 - Bailey and David to provide recommended
edits to the group on “Techniques for providing useful text
alternatives.” [on Bruce Bailey - due 2012-05-10].


    Summary of Action Items

*[NEW]* *ACTION:* Bruce Bailey and David to provide recommended edits to
the group on “Techniques for providing useful text alternatives.”
[recorded in http://www.w3.org/2012/05/03-wai-wcag-minutes.html#action01]
 
[End of minutes]
------------------------------------------------------------------------
Minutes formatted by David Booth's scribe.perl
<http://dev.w3.org/cvsweb/%7Echeckout%7E/2002/scribe/scribedoc.htm>
version 1.136 (CVS log <http://dev.w3.org/cvsweb/2002/scribe/>)
$Date: 2012/05/03 22:23:49 $

-- 

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/>