[html4all] ALT issue redux

Steven Faulkner faulkner.steve at gmail.com
Tue Feb 5 03:31:59 PST 2008


To pick up Josh's point,
There are many validation errors that don't cause browsers to stop
processing the document in HTML 4 and presume that this will be the case in
HTML5.

Relying upon this criteria as one of the points to decide whether alt should
be mandatory or not, is misguided.

On 05/02/2008, Joshue O Connor <joshue.oconnor at cfit.ie> wrote:
>
> > > Josh and I would seem to be agreed that "refuse to process
> > > such a page in the browser" is justified for a critical-content image
> > > that is lacking @alt.
>
> Just to be clear, I would not want the browser to refuse to render the
> page even if a critical alt is missing. That would be a situation where
> the cure is worse than the disease.
>
> > 3.  WCAG requires @alt (WCAG1) or the function that in HTML4
> > is provided by @alt (WCAG2)  [editorial note -- add links]
>
> I want the @alt to be mandatory for critical content for conformance for
> WCAG 1.0 and also [insert new attribute here] for WCAG 2.0.
>
> That puts accessibility into the right domain. Should the browser still
> continue to render pages that don't conform, yes. Should authors right
> better code and mark-up content in a proper way, yes. Should the browser
> not render a page that is not proper or does not conform? No.
>
> Cheers
>
> Josh
>
>
>
> _______________________________________________
> List_HTML4all.org mailing list
> https://www.html4all.org/wiki
>



-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://wilbur.bytowninternet.com/pipermail/list_html4all.org/attachments/20080205/d637ccdf/attachment-0001.html 


More information about the List_HTML4all.org mailing list