[Bug 9241] New: Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9241

           Summary: Explicitly state, "For guidance on accessibility
                    requirements for text alternatives authors should
                    consult WCAG 2.0" and link to WCAG 2.0
           Product: HTML WG
           Version: unspecified
          Platform: Macintosh
               URL: http://dev.w3.org/html5/spec/text-level-
                    semantics.html#the-img-element
        OS/Version: All
            Status: NEW
          Keywords: a11y, a11y_text-alt
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: laura.lee.carlson@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org, public-
                    html-a11y@w3.org
        Depends on: 8171


SPEC SECTION:

[http://dev.w3.org/html5/spec/text-level-semantics.html#the-img-element 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 explicitly state: 

"For guidance on accessibility requirements for text alternatives authors
should consult WCAG 2.0." 

Make sure that the text "WCAG 2.0" in that statement links to
http://www.w3.org/TR/WCAG20/ 

OUTCOMES OF FIXING THE BUG:

* Refers people to the WAI'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]

* 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.

REFERENCES:

http://dev.w3.org/html5/spec/text-level-semantics.html#the-img-element [1]
http://www.w3.org/WAI/about.html [2]
http://www.w3.org/TR/2008/REC-WCAG20-20081211/#intro [3]
http://www.w3.org/2009/06/Text-Alternatives-in-HTML5 [4] 
http://www.surl.org/usabilitynews/32/links.asp [5] 
http://lists.w3.org/Archives/Public/public-html/2010Feb/0871.html [6]

HTML5 ISSUE:

This is associated with HTML TRACKER ISSUE-31:
http://www.w3.org/html/wg/tracker/issues/31


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 13 March 2010 19:12:23 UTC