RE: Call for Consensus (CfC); Alt

Janina Sajka wrote:
"It is believed that over the past few years these differences have been
successfully resolved. This CfC tests this thesis. For the record we are
requesting the Task Force confirm this consensus, or point out specific
remaining insufficiencies."

I support this CFC.

Léonie.

--
Léonie Watson - Senior accessibility engineer
@LeonieWatson @PacielloGroup

-----Original Message-----
From: janina@rednote.net [mailto:janina@rednote.net] 
Sent: 29 May 2014 03:53
To: HTML Accessibility Task Force
Subject: Call for Consensus (CfC); Alt

Colleagues:

This is a Call for Consensus (CfC) to the HTML-A11Y Task Force to confirm
the sufficiency and accuracy of guidance on the alternative text attribute
for images as provided by the following two related HTML-WG documents. It is
also a Call for Consensus regarding proposed next steps for each of these
documents.

You will recall the relationship between these documents is that the first
was initially created to help remedy perceived deficiencies in the second.
In other words, initially guidance in these two documents was different, and
the two did not agree.

It is believed that over the past few years these differences have been
successfully resolved. This CfC tests this thesis. For the record we are
requesting the Task Force confirm this consensus, or point out specific
remaining insufficiencies.

1.)	HTML5: Techniques for providing useful text alternatives
	http://rawgit.com/w3c/alt-techniques/master/index.html

This document was initially created to help remedy deficiencies regarding
the alt attribute in early drafts of the HTML 5.0 specification. Over the
past few years, guidance originally present in this document has been
migrated to the HTML specification itself and removed from this document.
However, it is believed that this document should nevertheless be published
because the remaining content will continue to provide valuable guidance to
authors.

Recent edits to this document can be seen in the W3C Bugzilla bugs shown at
the following URI:

http://tinyurl.com/kjvj3bb

A permanent, though very long URI for these bugs is:

https://www.w3.org/Bugs/Public/buglist.cgi?bug_status=UNCONFIRMED&bug_status
=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=
VERIFIED&bug_status=CLOSED&component=CR%20alt%20techniques%20%28editor%3A%20
Steven%20Faulkner%29&list_id=37965&product=HTML%20WG&query_format=advanced

QUESTION 1:	Does the Task Force
		a.)	Accept the changes identified above to this
		    document; and
		b.) Recommend that work on this document be terminated; and
		c.) Support publication of this document by the HTML-WG
		    as a W3C Note.

2.)	HTML 5.0 Sec. 4.7.1.1 Requirements for providing text to act as
	an alternative for images
	
http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#alt

As noted above there have been significant edits to this section of the HTML
5.0 specification in order that this specification might best reflect
current consensus best practice guidance regarding alt. These changes are
documented by the following W3C Bugzilla bugs:

8827* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=8827>
Inappropriate spec text and advice where images are not known

9215* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=9215>
Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5:
Techniques for providing useful text alternatives"

9216* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=9216>
Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to "HTML5:
Techniques for providing useful text alternatives"

10708* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=10708>
change normative alt text authoring requirements to informative advice

13428* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=13428>
Remove Requirements for providing text to act as an alternative for images

20401* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=20401>
non conforming use of title attribute in example code

20402* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=20402>
use of title attribute in example is incorrect

20403* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=20403>
spec states plural conditions when only 1 condition is conforming

20404* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=20404>
more non conforming uses of title attribute in example code

20405* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=20405>
plural 'conditions' used when only one condition exists

21420* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=21420>
note about conforming image is incorrect

21941* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=21941>
Spaghetti Monster reference is provocative

22161* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22161>
paragraph contains inaccuracies

22373* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22373>
Should a a logo example that is not linked.

22375* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22375>
Images of text where there is also an image

22438* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22438>
Alt text for an image to a home page of a web site

22773* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22773>
Captions in image alt attributes

22774* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22774>
4.8.1.1.3 Image alts and explanations

22791* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=22791>
Alt text for charts, graphs etc should (when sensible) state what the
graphic is

23059* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23059>
Alt text section should address a headshot of a person with their name
written

23207* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23207>
Alt text should identify image class when relevant

23397* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=23397>
Expand advice regarding the use of images for gaiji, novel currency symbols,
and the like

24001* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=24001>
alt text example in wrong place

25264* <https://www.w3.org/Bugs/Public/show_bug.cgi?id=25264>
- Pointer to additional resources in section on text alternatives for images

QUESTION 2:	Does the Task Force:
		a.)	Accept the changes identified above to this
		    specification; and
		b.) Recommend that work on this specification be terminated;
and
		c.) Support publication of this section of the
		    specification  by the HTML-WG as part of W3C HTML 5.0.

ACTION TO TAKE

According to agreed HTML-A11Y Task Force Consensus Procedures [1], this CfC
is now open for objection, comment, as well as statements of support via
email. Silence will be interpreted as support, though messages of support
are certainly welcome.

If you have objections to any part of the above two questions, or any
comments concerning the proposed next steps for either of the above
documents, please respond by replying on list to this message no later than
midnight Boston Time, Wednesday 4 June.

Janina

[1] http://www.w3.org/WAI/PF/HTML/consensus-procedures


-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/

Received on Saturday, 31 May 2014 08:33:34 UTC