This Wiki page is edited by participants of the HTML Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.

Bugs/LinkToWCAG2

From HTML accessibility task force Wiki
< Bugs
Revision as of 19:13, 13 March 2010 by Lcarlson (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0

Bug Number

Bug 9241

Bug Title

Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0.

Spec Section

The img element [1]

Bug Description

In the img section, as recommended by WAI CG's Consensus Resolutions on Text alternatives in HTML 5", please state:

  • Refers people to the W3C's Web Content Accessibility Guidelines 2.0 (WCAG). Accessibility is WAI's domain and specialty. WAI develops guidelines which are widely regarded as the international standard for Web accessibility [2]. WAI's WCAG defines how to make Web content more accessible to people with disabilities.[3]

Outcomes of Fixing This Bug

  • Is in accord with Accessibility Coordination Group's "Consensus Resolutions on Text alternatives in HTML 5". [4]
  • As one study indicates, users prefer embedded reference links into the body of a document instead of lumping them all into one section. They believed that embedding the links within a document made it easier to navigate, easier to recognize key information, easier to follow the main idea of the passages, and promoted comprehension. [5]
  • Could help in the goal of modularizing W3C documents[6] as some information in the img section may be covered in WAI documents. It may aid in alleviating duplication of effort and double maintenance.
  • Could help in the goal of modularizing W3C documents[6] as some information may be covered in WAI documents. It may aid in alleviating duplication of effort and double maintenance.

REFERENCES

HTML5 Issue

This is associated with HTML TRACKER ISSUE-31:

http://www.w3.org/html/wg/tracker/issues/31