Archive for category HTML5
The details are still fluid, but the idea is this: ARIA is here (cue the cheering), but working devs still need to deal with backward compatibility – what works where, and what doesn’t work where? And so that is/was the germ of the idea. What we are setting out to do is to create that gnarly database (as a SQL db – and as granular as possible), collect (or write) appropriate tests against the ARIA specification, get them into a location where users can test and report, and then crowd-source the testing and reporting.
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.
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.
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!)
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.
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.