- From: <bugzilla@jessica.w3.org>
- Date: Fri, 04 Apr 2014 19:39:58 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25264 Bug ID: 25264 Summary: Pointer to additional resources in section on text alternatives for images Product: HTML WG Version: unspecified Hardware: PC URL: http://www.w3.org/html/wg/drafts/html/CR/embedded-cont ent-0.html#alt OS: All Status: NEW Keywords: a11y Severity: normal Priority: P2 Component: HTML5 spec Assignee: faulkner.steve@gmail.com Reporter: mark@w3.org QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-admin@w3.org, public-html-wg-issue-tracking@w3.org The HTML Accessibility Task Force acknowledges that "4.7.1.1 Requirements for providing text to act as an alternative for images" [1] as revised, provides a good introduction to authoring useful alternative content for images. After consulting with other WAI groups, the TF requests that a link to a more comprehensive list of resources for authoring alternative content also be added to this section of the specification. Request replacing the following NOTE: "NOTE: The alt attribute on images is a very important accessibility attribute (it is supported by all browsers, most authoring tools and is the most well known accessibility technique among authors). Useful alt attribute content enables users who are unable to view images on a page to comprehend and make use of that page as much as those who can."" With this text: "NOTE: The alt attribute on images is a very important accessibility attribute. Authoring useful alt attribute content requires the author to carefully consider the context in which the image appears and the function that image may have in that context. The guidance included here addresses the most common ways authors use images. Additional guidance and techniques are available in <a href="http://w3.org/WAI/alt/">Resources on Alternative Text for Images</a>." [1] <http://www.w3.org/html/wg/drafts/html/CR/embedded-content-0.html#alt> -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 4 April 2014 19:39:59 UTC