On 11 Aug 2008, at 16:14, Hassan Schroeder wrote:
David Dorward wrote:
It doesn't really reject it, it just warns you that the combination
doesn't make much sense.
Sigh. Semantics. That was one suggested DOCTYPE that I found -- and
no, I'm not sure at this point where -- but regardless, do you know
the answer to the *original question*:
When will the W3C validator support ARIA?
I've no idea for HTML, but I'm not sure it is 100% important. If the
rest of your code is valid and the only thing that is invalid is the
WAI-ARIA stuff then that would be good enough for me as it is a W3C
spec that is approved and implemented by all the major browser. It is
not like you are adding something invalid that only one browser
implements or will make browsers rely on error handling. For XHTML it
is a different kettle of fish as it was designed to be extensible
using name spaces. Of course, you can't use XHTML as IE doesn't
support it, so even with the XHTML doctype, browsers will treat it as
HTML if you use text/html.
Or, if you believe it already does, what is the appropriate DOCTYPE
to use?
As http://esw.w3.org/topic/PF/ARIA/BestPractices/Introduction states:
"...extensibility to XHTML, for ARIA, is achieved through namespaces
(i.e.: aria:haspopup). HTML documents do not support namespaces, so
the required accessibility role and state metadata cannot be included
directly in these documents. In HTML 4, authors can define accessible
role and accessible states as keywords in the class attribute, then
use an ECMAScript library to parse the class keywords and copy them
into the appropriate role and state namespaces after the document has
been loaded. This enables provision of ARIA states and properties
while circumventing the HTML validator by using the class attribute."
This will allow it to validate, but seems to add a whole lot of extra
work for what is really just fooling the validator into validating as
the WAI-ARIA stuff will still be in the DOM at the end of the day.
Only thing it adds is giving you more brownie points for validating,
while not allowing WAI-ARIA to work if JavaScript is turned off.
--
Hassan Schroeder ----------------------------- [EMAIL PROTECTED]
Webtuitive Design === (+1) 408-621-3445 === http://webtuitive.com
dream. code.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
David Storey
Chief Web Opener,
Product Manager Opera Dragonfly,
Consumer Product Manager Opera Core,
Mobile Web Best Practices Working Group member
Consumer Product Management & Developer Relations
Opera Software ASA
Oslo, Norway
Mobile: +47 94 22 02 32
E-Mail: [EMAIL PROTECTED]
Blog: http://my.opera.com/dstorey
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
