W3C home > Mailing lists > Public > public-html@w3.org > June 2012

Re: Issue 31c: Meta generator

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Thu, 7 Jun 2012 14:53:32 +0100
Message-ID: <CA+ri+Vme+8mQZ_581=K-1C1tAzYyhmoS91FU+oDbRS5LEdY3_Q@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: Toby Inkster <tai@g5n.co.uk>, Julian Reschke <julian.reschke@gmx.de>, Sam Ruby <rubys@intertwingly.net>, Judy Brewer <jbrewer@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, HTMLWG WG <public-html@w3.org>
Hi Henri,


> Or even better, a boolean option built into the validator's UI.
>
> That would not address the problem. Let's recap what problem the spec
> is trying to address: The spec is trying to remove the incentive for
> generator developers to emit empty alt when their generator doesn't
> have or logically cannot have proper alternative text it could stick
> into alt. If suppressing reporting of missing alt was under the
> control of the person who invokes the validator instead of the person
> who programs the markup generator, the person who programs the markup
> generator would still be incented to make the generator emit empty alt
> in order to make the generator always produce valid output so that the
> generator appears to be correct in the eyes of people who judge it by
> validating its output.
>

I suggest that a message be provided in the reulsts for pages that include
any error suppression in a similar format to this currently displayed in
the nu markup service:

*Info*: Using the schema for HTML5 + SVG 1.1 + MathML 2.0 + RDFa Lite 1.1 +
> Microdata.
>

for example:

*Info*: meta name="alternative_text" content="nowarn" , suppressing missing
> alt attribute errors
>


regards
Stevef

On 7 June 2012 14:29, Henri Sivonen <hsivonen@iki.fi> wrote:

> On Fri, May 18, 2012 at 5:37 PM, Toby Inkster <tai@g5n.co.uk> wrote:
> > This could be a different <meta> element...
> >
> >        <meta name="alternative_text" content="nowarn">
>
> This could work. (Work for alt, that is. I don't expect it to be
> reasonable to come up with names for all possible aspects of validator
> behavior, but I don't expect it to be interesting to suppress
> arbitrary validator behaviors.)
>
> > Or even better, a boolean option built into the validator's UI.
>
> That would not address the problem. Let's recap what problem the spec
> is trying to address: The spec is trying to remove the incentive for
> generator developers to emit empty alt when their generator doesn't
> have or logically cannot have proper alternative text it could stick
> into alt. If suppressing reporting of missing alt was under the
> control of the person who invokes the validator instead of the person
> who programs the markup generator, the person who programs the markup
> generator would still be incented to make the generator emit empty alt
> in order to make the generator always produce valid output so that the
> generator appears to be correct in the eyes of people who judge it by
> validating its output.
>
> --
> Henri Sivonen
> hsivonen@iki.fi
> http://hsivonen.iki.fi/
>



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Thursday, 7 June 2012 13:54:49 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:32 UTC