20:00:33 RRSAgent has joined #wai-wcag 20:00:33 logging to http://www.w3.org/2012/05/03-wai-wcag-irc 20:00:35 RRSAgent, make logs public 20:00:35 Zakim has joined #wai-wcag 20:00:37 Zakim, this will be WAI_WCAG 20:00:37 ok, trackbot, I see WAI_WCAG()4:00PM already started 20:00:38 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 20:00:38 Date: 03 May 2012 20:00:42 +Cooper 20:00:57 +Andrew_Kirkpatrick 20:01:02 zakim, Microsoft is Alex_Li 20:01:02 +Alex_Li; got it 20:01:06 +Kathy 20:01:11 +Bruce_Bailey 20:01:46 +ifette 20:02:04 zakim, ifette is Loretta_Guarino_Reid 20:02:04 +Loretta_Guarino_Reid; got it 20:02:09 awk has joined #wai-wcag 20:02:16 agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2012AprJun/0055.html 20:02:20 chair: Loretta_Guarino_Reid 20:08:24 scribe: Kathy 20:08:27 scribe: David 20:08:31 Finish up the discussion on headings 20:08:38 scribe: Kathy 20:08:42 scribe: Kathy 20:08:55 Yeahhhhh 20:10:43 Does assistive technology handle a heading and a link? 20:11:01 topic: LC-2607: Headings https://www.w3.org/2002/09/wbs/35422/20120419TF/results#x2607 20:11:28 It shows up in the heading list, David will check to see if it is in the links list 20:12:52 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." 20:13:50 Question is how much is up to author 20:14:17 +[Microsoft] 20:14:24 Area of judgement here 20:16:15 Topic: LC-2607 : Headings 20:17:29 +Gregg_Vanderheiden 20:18:07 -Alex_Li 20:29:40 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. 20:32:23 WCAG does not require strict hierarchy in headings. It recommends it but does not require it. Using two

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 20:34:03 hierarchically, the content can still meet WCAG, since equivalent information is exposed to everyone. 20:35:52 WCAG does not require strict hierarchy in headings. It recommends it but does not require it. Using two

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. 20:39:53 http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/H69.html 20:43:41 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. 20:43:52 Success Criterion 1.3.1 requires that if headings are in the content that the relationships are conveyed programmatically. 20:49:52 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. 20:50:22 Conclusion: Accepted as amended 20:51:06 Topic: HTML5: Techniques for providing useful text alternatives 20:52:04 Example 6.1 20:52:15 https://www.w3.org/2002/09/wbs/35422/20120503misc/results#xq1 20:58:56 Conclusion: Example is fine 20:59:14 scribe: David 20:59:29 -Kathy 20:59:36 Resolution: example 2.2, 6.1 ok 20:59:50 -Robin_Tuttle 21:06:18 pure decoration 21:06:19 serving only an aesthetic purpose, providing no information, and having no functionality 21:06:21 Note: Text is only purely decorative if the words can be rearranged or substituted without changing their purpose. 21:06:22 Example: The cover page of a dictionary has random words in very light text in the background. 21:07:01 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. 21:21:24 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. 21:52:23 -Andrew_Kirkpatrick 21:52:24 -[Microsoft] 21:52:25 -Loretta_Guarino_Reid 21:52:26 -Bruce_Bailey 21:52:29 -Cooper 21:52:29 -David_MacDonald 21:53:54 -Gregg_Vanderheiden 21:53:56 WAI_WCAG()4:00PM has ended 21:53:56 Attendees were Robin_Tuttle, David_MacDonald, Cooper, Andrew_Kirkpatrick, Alex_Li, Kathy, Bruce_Bailey, Loretta_Guarino_Reid, [Microsoft], Gregg_Vanderheiden 21:57:38 MichaelC has joined #wai-wcag 22:23:38 Action: Bruce Bailey and David to provide recommended edits to the group on “Techniques for providing useful text alternatives.” 22:23:38 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]. 22:23:44 rrsagent, make minutes 22:23:44 I have made the request to generate http://www.w3.org/2012/05/03-wai-wcag-minutes.html MichaelC 22:32:02 Zakim has left #wai-wcag