W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2005

RE: Validity

From: Roberto Scano (IWA/HWG) <rscano@iwa-italy.org>
Date: Fri, 4 Nov 2005 15:30:46 +0100
To: <akirkpatrick@macromedia.com>, <w3c-wai-gl@w3.org>
Message-Id: <200511040924234.SM00784@Inbox>



----- Messaggio originale -----
    Da: "Andrew Kirkpatrick"<akirkpatrick@macromedia.com>
    Inviato: 04/11/05 15.02.35
    Actually, Section 508 in the US is basically WCAG-based and doesn't
    include validation or many other P2's.
    
Roberto:
Sorry but we are talking about a new set of guidelines, not to a national law of the last Century... There is not only USA but, for eg, also Europe.


Andrew:
    As far as not having valid code, it doesn't mean that Flash can't be
    used, it means that other compromised need to be made.  If you want
    valid code with Flash you need to either:
    1) require javascript from your users

Roberto:
This is not in discussion. Javascript should respect accessibility issues.

Andrew:
    2) use proprietary IE-specific comments

Roberto:
That, in html, are normal comments.

Andrew:
    3) use a valid technique that breaks accessibility in the most widely
    used user agent for blind people
    
Roberto:
At now i can test it only in IE + AT. Can u tell please where there is support for flash accessibility?

Andrew:
    Does using the embed element cause problems for automated testing tools?
    Really?  They seem to parse it now fairly well...
    
Roberto:
Nope, but means to use a proprietary tag (from netscape) that has never Been part of any spec.

Andrew:    
    If you think that this is all about the Flash player then your view is
    too narrow. This is a problem for QuickTime, SVG, WindowsMedia, Real,
    and others.  

Roberto:
Yes i know, but they use all code that conform to specifications.
    
Andrew:
    What will happen is that users will reply on javascript more to write
    the needed code on the fly, after passing validation.  This goes on now
    with a lot of dynamic javascript web work - the application/page is
    declared 'valid XHTML' but the new content that is added dynamically
    isn't necessarily.

Roberto:
Adding code with dom injection that add custom elements and attributes that are not part of a dtd is worste than violate directly a page code. An UA parse  content served to the browser and make fool the validator don't mean be intelligent - imho.

All the best,
Roberto Scano
IWA/HWG
Received on Friday, 4 November 2005 14:27:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:40 GMT