This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9241 - Explicitly state, "For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0
Summary: Explicitly state, "For guidance on accessibility requirements for text altern...
Status: CLOSED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Macintosh All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/text-lev...
Whiteboard:
Keywords:
Depends on: 8171
Blocks:
  Show dependency tree / graph
 
Reported: 2010-03-13 19:12 UTC by Laura Carlson
Modified: 2014-02-10 09:50 UTC (History)
9 users (show)

See Also:

Attachments

Description Laura Carlson 2010-03-13 19:12:20 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2010-04-01 21:43:35 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: see diff given below
Rationale: I added the suggested text to the W3C HTML5 draft. I used "are encouraged to also consult" instead of "should consult" because "should" has a special meaning due to RFC2119.
Comment 2 contributor 2010-04-01 21:43:47 UTC 
Checked in as WHATWG revision r4935.
Check-in comment: Add link to WCAG2.
http://html5.org/tools/web-apps-tracker?from=4934&to=4935
Comment 3 Laura Carlson 2010-06-22 08:42:22 UTC 
Reopening this bug as the change was reverted:
http://lists.w3.org/Archives/Public/public-html/2010Jun/0525.html
Comment 5 Ian 'Hixie' Hickson 2010-08-16 22:02:09 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Having a reference to WCAG here would be inconsistent since we don't have them in all the other relevant places. Having them all over the place would make the spec less coherent and harder to edit. Therefore I think it is best if the two documents do not try to deep-link into each other.
Comment 6 Martin Kliehm 2010-12-07 16:40:41 UTC 
The bug-triage sub-team sees that there is a general issue regarding links to other W3C documents that should be addressed by the task force. But this particular bug shouldn't be task force priority.
Comment 7 Laura Carlson 2011-01-01 22:36:58 UTC 
Adding the TrackerIssue keyword as a Change Proposal for Issues 31/122 has incorporated this change:
http://www.w3.org/html/wg/wiki/ChangeProposals/TextAlternativesIssue122
Comment 8 steve faulkner 2014-02-10 09:48:25 UTC 
this is moot since the advice in the spec wcag 2.0 guidance