Re: Strategic decision time (was Re: Next steps for the ARIA syntax discussion)

On Thu, 29 May 2008 14:13:43 +0200, Henry S. Thompson <>  
> We have to set against the problems with aria: the medium- and
> long-term negative aspects of the aria- approach, which focusses on
> ease of ARIA integration in text/html environments at the expense of
> costly integration throughout the application/...+xml universe.  From
> my perspective, the cost of aria: in the text/html environment is
> modest, manageable, and declining over time, whereas the cost of aria-
> in the application/...+xml universe is large and permanent.

This is by no means proven. I don't buy it at all that the specific syntax  
has much impact on the cost of introducing ARIA in any vocabulary.

The cost of ARIA is in figuring out what happens when native and ARIA  
semantics clash.

Also, as for syntax, I'd claim that given the HTML environment we have on  
the Web (which is by the way much larger than this magical XML universe,  
but that's besides the point), introducing aria-* is of much lower cost to  
everyone involved than introducing aria:*. We need ARIA in HTML, XHTML,  
and SVG. Those languages don't have that attribute now. The only cost of  
introducing those attributes is the cost I mentioned above, figuring out  
what happens in case of clashing semantics, which we have regardless of  

The cost of introducing aria:* however is bigger, because of DOM and  
styling differences as has been explained countless times. As well as  
making it impossible to ever change the way colon works in HTML, et cetera.

Anne van Kesteren

Received on Thursday, 29 May 2008 12:41:56 UTC