Archive for category HTML5
The Unpopular Position: Recently, another fear-mongering, not-quite-correct anti-DRM article was posted over at FreeCulture.com. I’ve pretty much had it with the amount of FUD being propagated around the web on this topic, and so against my better judgment (OK, maybe not), I am about to set out and articulate the other perspective. Continue Reading DRM at the W3C? Not such a Bad Idea.
With respect to the Mozilla bug-tracker (where I originally wrote this, and then counted to ten – err, rather 8 before changing my mind), here is my original unvarnished response to Ian Hickson’s comments. Continue Reading Related to Bug 854848 – Support the longdesc attribute
In 2013 it is simply inexcusable to be saying things like “Dyslexics can always upgrade” or that your site/app/service “is optimized for WebKit browsers such as Chrome and Safari” to the point that it will not work in other browsers, or that it imposes a real hardship on your users. We tried that in the 90′s, and trust me, it didn’t work then either. STOP THE MADNESS (Again already!) Continue Reading Everything Old is New
It’s a common design pattern, seen multiple times a day: a thumbnail image and Headline, both linked to the same URL. We’ve seen this pattern for so long now that most sighted users know, instinctively, that clicking on either the thumbnail or the Headline takes them to the same location. However the code developers use to achieve this is a bit of a mess, and for non-sighted users or keyboard-only users, the User Experience (UX) leaves a lot to be desired: duplicate links announced for each article, and excessive tabbing through the content. It would appear that either
role="presentation" should be able to help out here. Continue Reading HTML5 Accessibility: aria-hidden and role=”presentation”
HTML5 has added a number of new element attributes, including 12 attributes used when creating forms. These Common input element attributes include 2 new Boolean attributes, the required attribute and the readonly attribute. Recently a number of current browsers have implemented native support for the ‘required’ attribute, and so I thought it woulde be useful to examine this attribute in more detail.
There is no harm using div elements; you can continue using them instead of section and article. I think we should use the new elements to make your mark-up readable, not for any inherent semantic advantage.
Divya is quite confused about web accessibility. I examine everything she says in a detailed, semi-sarcastic, no-holds barred manner. Conclusion: Semantics matter – a lot.
The @longdesc “discussion” just won’t go away. Over on the W3C mailing list, Tantek Çelik said something that I wanted to drill into a bit further… Continue Reading WYSIWYG support for @longdesc today