Skip to main content

Home/ HTML5 development/ Group items tagged nav

Rss Feed Group items tagged

Vernon Fowler

Semantic navigation with the nav element | HTML5 Doctor - 1 views

  • Previous/next buttons (or pagination) I would say yes to this because it is important to the overall structure and hierarchy of the blog/site
  • Search form For me, a definite yes, but it is not mentioned in the spec. A search form is hugely important to the navigation of a site, particularly large sites which rely almost solely on their search engine.
  • Breadcrumbs Again, I would say yes to this as well. Although breadcrumbs are not always necessary and can be used when not applicable, on large sites a breadcrumb trail can be an important navigation aid.
  • ...3 more annotations...
  • <menu> is to be used for a list of commands and is an interactive element and more likely to be used exclusively in Web Applications.
  • The nav element represents a section of a page that links to other pages or to parts within the page: a section with navigation links.
  • Table of Contents I would say definitely yes to that – it is primary navigation for that particularly content
  •  
    Breadcrumbs Again, I would say yes to this as well. Although breadcrumbs are not always necessary and can be used when not applicable, on large sites a breadcrumb trail can be an important navigation aid.
Vernon Fowler

HTML5 sectioning elements, headings, and document outlines | 456 Berea Street - 0 views

  • To prevent the footer’s heading from becoming the page heading we can wrap the footer element’s contents in a section element:
  • This really feels like a hack, but it does move the footer heading to its expected position in the document outline.
  • Since there is no heading in the nav element, it becomes “Untitled NAV”.
Vernon Fowler

Document Outlines | HTML5 Doctor - 0 views

  • The sectioning elements act quite literally as their name suggests: they define sections of the parent element. These sections can be thought of as child nodes whose headings fall under their parent heading, regardless of their rank.
  • Sections may contain headings of any rank, but authors are strongly encouraged to either use only h1 elements, or to use elements of the appropriate rank for the section’s nesting level.
  • For accessibility reasons, we recommend each sectioning element have a heading, even <aside> and <nav>, as shown below. If you don’t want these headings to be visible, you can always hide them with CSS.
  • ...2 more annotations...
  • It’s best if you use logical heading levels — <h1>–<h6> — at least until the new outlines are more widely supported.
  • Unfortunately, there is little support for the new outlining algorithms right now. Search engines may be experimenting with it in their crawling algorithms as you read this, but as far as we know, headings are treated just as they were before. You won’t be penalised for using them, even if you use multiple <h1>s (which have always been okay as far as the spec is concerned). Check out our HTML5 and Search Engine Optimisation article for more on search engines and HTML5.
Vernon Fowler

Avoiding common HTML5 mistakes | HTML5 Doctor - 0 views

  • If it’s a purely presentational image and not referenced elsewhere in the document, then it’s definitely not a <figure>.
Vernon Fowler

The main element | HTML5 Doctor - 0 views

  • One important facet of <main> is that it can only be used once per page.
  • Another stipulation of <main> is that it can’t be used as a descendant of an <article>, <aside>, <footer>, <header>, or <nav> element.
  • Of course, if you use the html5shiv, <main> is now baked in directly.
Vernon Fowler

Designing a blog with html5 | HTML5 Doctor - 0 views

  • use the header, footer, main and nav elements to mark up the broad structure of the page. Doing this will make your site more accessible to real people who use some assistive technologies
1 - 6 of 6
Showing 20 items per page