W3C home > Mailing lists > Public > public-html-a11y@w3.org > April 2010

Re: RESOLUTION to modify text alternative change proposal and reject WAI CG's consensus recommendation

From: Joshue O Connor <joshue.oconnor@cfit.ie>
Date: Fri, 09 Apr 2010 12:42:06 +0100
Message-ID: <4BBF128E.4080409@cfit.ie>
To: John Foliot <jfoliot@stanford.edu>
CC: 'Laura Carlson' <laura.lee.carlson@gmail.com>, 'HTML Accessibility Task Force' <public-html-a11y@w3.org>, 'Janina Sajka' <janina@rednote.net>, "'Michael(tm) Smith'" <mike@w3.org>, 'Michael Cooper' <cooper@w3.org>, 'Judy Brewer' <jbrewer@w3.org>, wai-cg@w3.org
Hi John,

On 08/04/2010 23:27, John Foliot wrote:
> While I too share a frustration that the TF actually went so far as to pass
> resolutions at the F2F without proper prior notice, I do also wonder what to
> do when an<img>  is not valid.

This is a big part of the problem, devs that are inclined to put in 
anything to shut up a conformance checker etc will still do it. That is 
not serving the needs of the end user. In fact no matter what we do, for 
these use cases it could be argues there is little anyone can do.

> I don't see anything in the resolution that takes this away, in fact as I
> read it, it re-enforces this aspect: take advantage of the teachable moment
> and get out the appropriate resources.

Yes, exactly.

> On balance then, I feel that whether we call it an error or warning is less
> important ("a rose, by any other name...") than what we actually end up
> doing with that result which is most important, and pointing to the
> appropriate resources within WAI on remediation and repair has not been
> removed - rather, re-enforced.



Received on Friday, 9 April 2010 11:42:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:35 UTC