WAI-ARIA: another W3C failure?

ARIA (Accessible Rich Internet Applications) is a WAI initiative promoted by the W3C to make rich internet applications accessible to assistive technologies. I'm actually quite a fan of this initiative, but I'm also aware of the fact that maybe we're facing another W3C failure. I'll try to make myself clear. The sad truth about these initiative is that the actual actors of this drama are not on the stage together. The actors of the W3C play are both user-agent vendors and assistive technologies vendors. So far so good.

The problem here is that both actors don't communicate to each other. For example, many of you recall the problem of the CSS declaration display: none interpreted by most screen readers as speak: none. This is a bug, of course, but you can't blame or curse screen readers, because their implementors were not involved with the process behind the CSS specifications. None of them! As result, screen readers didn't implement aural style sheets which were later abandoned. So we have two actors on two different stages, as you can see from the following picture taken from the ARIA specs:

WAI-ARIA Scheme

Theoretically speaking, user-agents and assistive technologies should communicate in order to make this model work. Reality is actually different: WAI-ARIA is currently poorly supported by most browsers, not to say ignored by Internet Explorer which is still the most used browser on the web. I think that we're facing a situation similar to the lack of support for application/xhtml+xml which made XHTML 1.1 fall into oblivion (and, consequently, HTML 5 arose from the ashes of XHTML 2). To prevent this from happening, the W3C should put both actors on the same stage by getting them involved with this initiative as much as possible. Otherwise, this would be another W3C failure.

FBML (Facebook Markup Language) and the W3C

I just typed social markup language on Google and I got this. Excellent. So what's the point here? The point is, rather surprisingly, that the W3C is actually ignoring the social network phenomenon or, more explicitly, neglecting the actual needs of web users and developers. There's no SNML (Social Network Markup Language) standardized in any W3C specification. Too bad. So the W3C seems not to care very much about what is become a de facto standard of many web platforms. It seems to delegate to specific social network owners the task of creating a common set of tags to handle their documents. But this is exactly what happened a long time ago before the creation of the W3C itself, that is, the proliferation of proprietary and not-interoperable tags in the HTML. So what? The W3C should get more interested in the real web, now and not in a remote and distant future. The alternative is simply a jump back to the age of incompatible markup and the resulting chaos of platform wars.

Standards war, episode one: revenge of the embed element

As many of you have noticed yet, this blog has the bad habit to embed many YouTube videos taken from different sources. Since I should be, theoretically speaking, a stickler of web standards, this should be done only through the object element. But this is not the case, and that's not my fault and it doesn't depend on a personal choice. The sad truth is that the object element alone is supported by all browsers, but not all its features, such for example the parameters you can pass to it via the param element. Internet Explorer, in fact, fully supports this element, but this is not the case of Firefox, which still uses the embed element. Why? Because this is a relic of the age of the first browser wars, when every browser tried to beat its adversary by implementing new features. More specifically, the embed element was not that bad, but the official HTML specs didn't include it as a standard element so its use should be deprecated. I said "should", but when it comes to reality, this element takes its revenge on standards in the form of a widespread support by almost all the platforms used for sharing videos (headed by YouTube). So what? As always, we must wait until the use of the object element will reach its momentum or, alternatively, try the new cool features of the latest HTML 5 specs (if we have enough spare time... or we can afford to wait). If you want code to the standards, consider the use of JavaScript as an alternative to avoid validation issues.