Avoid repeated content
Only at the top (where the author put them)
Only a partial overview
Not quite so useful in app-like settings
Signposts to broad areas of the page
Non-visual complement to visual design
Part of the W3C's Accessible Rich Internet Application (ARIA) standards
is the same, semantically, as
|Element||Landmark region role|
isn't a landmark, but this is:
Headings: fine-grained navigation
Use relatively few landmarks…
…but cover all of the content on the page.
If you've got more than one of the same type of landmark on a page, use labels to differentiate them.
There's no need to include the type of landmark in its label.
Screen-readers may say"Site, navigation"
Screen-readers may say"Site Navigation, navigation"
I mentioned at the London Accessibility Meet-up that Dragon supported landmark roles, however it may not (to be confirmed shortly)—oops! It does now support
aria-labelledby and ARIA roles for form controls.
The BBC Sport article referenced earlier mentioned this: the average runner shrinks 1.25cm during a marathon, due to spine compression. We all get shorter throughout the day, too, but the amount varies.