Navigation or content first?
Monday, September 24th, 2007It’s a debate that comes and goes: should your content be before your navigation in the source order and/or in the visual order?
Personally, I use the visual layout of nav on the left, but at the bottom of the source. With a huge nav like a blog generally has, I think Google likes my content better if it’s at the top of the source, and it’s better for screenreader users not to tab through endless nav.
Arguments against content first tend to focus on the subversion of user expectation: it spooks people out too much if the content is first. I say “Tish and Pish!” because I think that’s a red herring—users expect massively-nested tables for layout but doesn’t mean you should do it. I also think that websites are so heterogenous that people expect to have to learn a new layout for each site, anyway.
The reason I mention this is that I read a generally sensible blog post the other day by the American Federation for the Blind called How to Make Your Blog Accessible to Blind Readers which said:
Blind users find top and left-hand navigation bars annoying because the screen reader starts at the top of the page and reads from left to right. It is very time-consuming to listen to the same list of links every time you visit a page. You can get people right to your latest post by putting your navigation links on the right-hand side.
If you are wedded to left-hand navigation, then place a tiny “skip link” at the top, so blind users can jump to the new content. Just don’t forget the anchor!
Assuming that the AFB knows what it’s talking about, that’s pretty clear: put content first, but if you really can’t do that, use skip links (even though “skip links” is a widget that’s does what the browser should do, and Patrick Lauke will give the AFB a collective wedgie for recommending it).
Talking of which, Ian Lloyd has made a video that shows people how to resize text in all the popular browsers called Teach a Man to Fish (or How to Resize Text) which he wants people to link to instead of arseing around with text resize widgets. Do it, or Lauke will give you a wedgie.