In Praise of the Unambiguous Click Menu | CSS-Tricks
What’s important is that you test it with real users… and stop using hover menus.
Strong agree!
Another take on the scrolling navigation pattern. However you feel about the implementation details, it’s got to better than the “teenage tidying” method of shoving everything behind a hamburger icon.
What’s important is that you test it with real users… and stop using hover menus.
Strong agree!
Vasilis offers some research that counters this proposal.
It makes much more sense to start each page with the content people expect on that page. Right? And if you really need navigation (which is terribly overrated if you ask me) you can add it in the footer. Which is the correct place for metadata anyway.
That’s what I’ve done on The Session.
This looks like a handy library for managing page transitions on sites that are not single page apps.
I’ve said it before and I’ll say it again, but I really think that this handles 80% of the justification for using a single page app architecture.
Paul walks us through the process of making some incremental accessibility improvements to this year’s 24 Ways.
Creating something new will always attract attention and admiration, but there’s an under-celebrated nobility in improving what already exists. While not all changes may be visual, they can have just as much impact.
A peek behind the scenes of an interesting new navigation pattern on the Guardian’s still-in-beta responsive site.
You can try it out here
Is it okay if URLs and labels are out of sync?
Applying progressive enhancement to responsive navigation patterns.
Combining responsive design with CSS table layout to rearrange the display of content and navigation.
Rigidly defined areas of doubt and uncertainty.
Why do browsers that don’t implement stylesheet switching still download alternative stylesheets?