Techniques for WCAG 2.0とUnderstanding WCAG 2.0がアップデートのドラフトが公開(1/16)

1月16日にW3Cより、Techniques for WCAG 2.0Understanding WCAG 2.0のアップデートのドラフトが公開されました。フィードバックを受けて正式版になるようです。ちなみに、フィードバックの期日は2月14日までです。

ざぁと見た感じTechniques for WCAG 2.0とUnderstanding WCAG 2.0の変更箇所、追加箇所は下記の項目になっています。

Techniques for WCAG 2.0の変更箇所、追加箇所


  • G86: Providing a text summary that can be understood by people with lower secondary education level reading ability
  • G141: Organizing a page using headings
  • G179: Ensuring that there is no loss of content or functionality when the text resizes and text containers do not change their width
  • H42: Using h1-h6 to identify headings
  • H45: Using longdesc
  • H69: Providing heading elements at the beginning of each section of content
  • H92: Including a text cue for colored form control labels
  • ARIA1: Using the aria-describedby property to provide a descriptive label for [begin change]user interface[end change] controls
  • ARIA2: Identifying a required field with the aria-required property
  • F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely
  • F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images in HTML in a way that allows assistive technology to ignore them
  • F39: Failure of Success Criterion 1.1.1 due to providing a text alternative that is not null (e.g., alt="spacer" or alt="image") for images that should be ignored by assistive technology
  • F42: Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable
  • F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content
  • F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control
  • F62: Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML
  • F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link
  • F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determined
  • F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order
  • F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number
  • F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link
  • F91: Failure of Success Criterion 1.3.1 for not correctly marking up table headers


  • ARIA4: Using a WAI-ARIA role to expose the role of a user interface component
  • ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component
  • ARIA6: Using aria-label to provide labels for objects
  • ARIA7: Using aria-labelledby for link purpose
  • ARIA8: Using aria-label for link purpose
  • ARIA9: Using aria-labelledby to concatenate a label from several text nodes
  • ARIA10: Using aria-labelledby to provide a text alternative for non-text content
  • ARIA11: Using ARIA landmarks to identify regions of a page
  • ARIA12: Using role=heading to identify headings
  • ARIA13: Using aria-labelledby to name regions and landmarks
  • ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used
  • ARIA15: Using aria-describedby to provide descriptions of images
  • ARIA16: Using aria-labelledby to provide a name for user interface controls
  • ARIA17: Using grouping roles to identify related form controls
  • ARIA18: Using aria-alertdialog to Identify Errors
  • ARIA19: Using ARIA role=alert or Live Regions to Identify Errors
  • F92: Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information

Understanding WCAG 2.0の変更箇所、追加箇所


  • Non-text Content 1.1.1
  • Info and Relationships: 1.3.1
  • Keyboard 2.1.1
  • Bypass Blocks 2.4.1
  • Page Titled 2.4.2
  • Link Purpose(In Context) 2.4.4
  • Link Purpose(Link Only) 2.4.9
  • Section Headings 2.4.10
  • Error Identification 3.3.1
  • Labels or Instructions 3.3.2
  • Error Suggestion 3.3.3
  • Name, Role, Value 4.1.2