This is a question that esmi has brought up in make.accessible:
Cited example: Should the Twenty Thirteen drop the use of the
role
attribute on the HTML5nav
element on the grounds that the element, by definition, has the role of navigation? Or shouldrole="navigation"
be retained in order to support technologies that are not yet HTML5 aware?My own opinion that the
role
attribute should be retained for the time being in order to support the widest range of technologies. Dropping it would offer only a marginal benefit in reducing page bloat. Please do weigh in with your opinions on the ticket.
Great question and I love the focus on keeping things light and less bloated, but I don’t think it should be dropped as it’s still used. Offer up your opinions in the thread here.
Are there any other things that you can think of stripping recently? Any other conversations you guys are having to keep things light and fast?
On another note, I have yet to install Twenty Thirteen on any of my sites – I’m just not liking it enough yet… am I missing something?
Have you used it yet?
2 Comments