RE: EOWG: WCAG-EM comments due this week

Hi all,

My comment is on a potential overuse of definition list code in the WCAG-EM.
Definition lists are more complex for screen reader users to navigate, and
they are announced as definition lists, so incorrect use misinforms the user
about the type of content they are about to encounter.   ... Just let me
know if I'm being too pedantic. 

In one instance the <dl>  code is used where styling, semantic structure and
ease of navigation indicate that headings would be more appropriate. This is
found under:

<h3>Background reading

Currently the <h3> is followed by a leading paragraph, then a definition
list of three items, ("Web Accessibility Essentials", "Evaluating Websites
for Accessibility" and "Web Content Accessibility Guidelines (WCAG) 2.0)").
Each of these is styled to look like a sub-heading of "Background Reading"
and is followed by content that goes beyond defining these terms. 

Another and more obvious example is found under Appendix C: 
The second list in this appendix is an unordered list with an introductory
sentence of "All reports should at least have the following basic
information:" which is coded as a definition term, but there is no <dd>
coded.  Again, it doesn't appear to me that the list that follows this is a
definition of the introductory text. 




      -----Original Message-----
      From: Shawn Henry []
      Sent: 20 March 2013 17:44
      To: EOWG (E-mail)
      Subject: EOWG: WCAG-EM comments due this week
      -------- Original Message --------
      Subject: EOWG - WCAG-EM review reminder
      Date: Fri, 08 Mar 2013 13:45:27 -0600
      From: Shawn Henry <>
      To: EOWG (E-mail) <>
      Hi all,
      I've updated the wiki page for comments on WCAG-EM:
      If you have copyedits that don't need EOWG consideration, you can send
      directly to <> or put them in the wiki under
the section
      "Copyedits & things that probably don't need discussion"
      Remember EOWG is focusing on things like clarity, understandability,
      readability, usability, relationship with other WAI documents, etc. If
you have
      comments on technical aspects, please send those directly to
<public-wai->. (If you're not sure, feel free to put them in the
      -------- Original Message --------
      Subject: 	Call for Review: Website Accessibility Conformance
      Methodology (WCAG-EM)
      Date: 	Tue, 26 Feb 2013 10:10:18 -0800
      From: 	Shawn Henry <>
      To: 	WAI Interest Group <>
      CC: 	Shadi Abou-Zahra <>, Eric Velleman
      Dear WAI Interest Group Participants,
      WAI invites you to comment on the updated Working Draft of Website
      Accessibility Conformance Evaluation Methodology (WCAG-EM) 1.0 at:
        *We are particularly interested in how it works for you in
      WCAG-EM describes an approach for evaluating how websites -- including
      web applications and websites for mobile devices -- conform to Web
      Accessibility Guidelines (WCAG) 2.0. It covers different situations,
      self-assessment and third-party evaluation. It is independent of
      evaluation tools, web browsers, and assistive technologies. For more
      information, see the WCAG-EM Overview at:
      For review:
      All sections are updated based on feedback from the previous draft.
      review questions are indicated with "Review Note" in the draft. We
      encourage feedback on how the methodology works in different
      Please send comments on this draft document to the publicly archived
                by *22 March 2013*
      WCAG-EM is developed by the WCAG 2.0 Evaluation Methodology Task
      Force (Eval TF), a joint task force of the Web Content Accessibility
      Working Group (WCAG WG) and Evaluation and Repair Tools Working Group
      (ERT WG). The Eval TF is introduced
      It is a supporting resource for WCAG 2.0 and does not replace or
supersede it
      in any way. For an overview of WCAG,
      This work is developed with support of the EC-funded WAI-ACT Project
      287725) described at:<>
      It is part of W3C WAI activities on web accessibility evaluation and
      introduced at:<>
      The first URI above goes to the latest version of the document. The
      version of this draft is:<
      The difference between these URIs are explained in Referencing and
      to WAI Guidelines and Technical Documents
      Please let us know if you have any questions. Thank you in advance for
      Feel free to circulate this message to other lists; please avoid
      where possible.
      ~Shawn Lawton Henry, WAI Outreach
      Eric Velleman, Eval TF Facilitator
      Shadi Abou-Zahra, W3C/WAI Staff Contact
      Shawn Lawton Henry
      W3C Web Accessibility Initiative (WAI)
      Massachusetts Institute of Technology (MIT)
      phone: +1.617.395.7664

Received on Thursday, 21 March 2013 10:48:53 UTC