Hello,
Which one would you pick over the other and why?
Regards,
-jj.![]()
| SitePoint Sponsor |





Hello,
Which one would you pick over the other and why?
Regards,
-jj.![]()





At this point, the div since HTML(5) support is still sketchy.
In a few years when IE9 is the dying browser, I'd probably go with nav.
Xazure.Net - My Blog - About Programming and Web Development
Follow Me on Twitter!
Christian Snodgrass





I would pick
<ul role="navigation">
because most of the time, your navigation is a list of links. If it isn't, I would tack the navigation role on whichever container was closest (nesting-wise) to whatever you are calling "navigational thingies". I would not include a site search form under this, even though it is a valid form of "navigation" for many people. Search forms should already have a role of "search", as a separate thing.
Bruce Lawson and Remy Sharp's book on HTML5 really stretched the meaning of "navigation" and were advocating <nav> and navigation roles all over the place... but they have since scaled back, way back.
A note: using a manual role of navigation on a nav tag has been known to screw up the NVDA screen reader (let alone Window-Eyes). Since eventually HTML5 wants to have native roles on most/all elements, in the unforseen future the nav tag should by default have a "navigation" role.
When that happens, user agents should then be able to easily tell the difference between a native role and a landmark (ARIA) role.









HTML5 is not HTML??Besides, <nav> is not an HTML element.
Are you not falling for the "living standard" indoctrination??? A pox upon thee and thyne house!
It's become my second source of invalid HTML4, right after the tabindex="-1" for either removing redundant links from tab order or making IE6 actually work with skip links : )role="" is not an HTML attribute either in that case.
And to think, I used to write valid HTML...
I'd be inclined to use the <nav> but if you needed a <div> inside that to markup the content in the CSS I'd rely on that for styling/coding leaving the <nav> as a bonus for browsers/search engines that recognised it.





Which currently, so far as I know, none do (FF has an experimental html5 parser that you can switch on... not sure if Opera's done the same yet).leaving the <nav> as a bonus for browsers/search engines that recognised it.





Ah I'm still on 3.6x.Firefox has shipped with the HTML5 parser enabled by default since FF4.
OMIDOG THE END OF THE EARTH IN AN EPIC BATTLE OF FIRE AND ICE AND HTML5!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Ragnarök hasn't shipped yet but can be tested in a Labs build.
Where the hell have I been?
When IE finally does it they should call it ARMAGEDDON
what is "role" for?
I'll go with <nav> this is HTML5, the future of web design.
just use ie fix javascript to make it compatible to idiot browsers.



Ha ha, 20 role="complimentary". That's a good one. Note that I could find use for such a role, though.
It seems that a lot of people keep on using "aside" when they mean "complementary" and, as you stated, "complementary" when they mean "contentinfo".





Those two are awfully close, yes. Except if I were to use <aside> for say a sidebar, I'd only bother adding the role if it was a case where I'd want to add a skip link to it anyway (I'll add skip links for sighted keyboarders and older sr's either way).It seems that a lot of people keep on using "aside" when they mean "complementary"
Or do you mean people are using role="aside"? Does such a role exist?
Firefox 3.6 will be the next IE 6. Yuppers.





Without the scattered millions of shackled office workers tied to ancient and expensive Java applications.Firefox 3.6 will be the next IE 6. Yuppers.
FF3.6 will be gone long before IE6 >:)
Bookmarks