The nav Element

It's sheltered to accept that the nav component will show up in for all intents and purposes each venture. Nav speaks to precisely what it infers: a gathering of route connections. In spite of the fact that the most widely recognized use for nav will be for wrapping an unordered rundown of connections, there are different alternatives. For instance, you could wrap the nav component around a passage of content that contained the significant route joins for a page or area of a page. 

In either case, the nav component ought to be held for route that is of essential significance. In this way, it's prescribed that you abstain from utilizing nav for a brief rundown of connections in a footer, for instance.

Skip Navigation Links

An outline design you may have seen actualized on numerous destinations is the "skip route" interface. The thought is to permit clients of screen perusers to rapidly skip past your site's primary route on the off chance that they've officially heard it—all things considered, there's no point listening to a vast site's whole route menu each time you navigate to another page! The nav component can possibly dispose of this need; if a screen peruser sees a nav component, it could permit its clients to skirt the route without requiring an extra connection. The detail states: "Client specialists, (for example, screen perusers) that are focused at clients who can profit by route in arrangement being discarded in the underlying rendering, or who can profit by route data being quickly accessible, can utilize this component as an approach to figure out what content on the page to at first skip or give on demand (or both)." 

Although not all assistive devices recognize nav as of this writing, by building to the standards now you ensure that as screen readers improve, your page will become more accessible over time.

User Agents

You’ll encounter the term “user agent” a lot when browsing through specifications. Really, it’s just a fancy term for a browser—a software “agent” that a user employs to access the content of a page. The reason the specs don’t simply say “browser” is that user agents can include screen readers or any other technological means to read a web page. 

You can use nav more than once on a given page. If you have a primary navigation
bar for the site, this would call for a nav element. Additionally, if you had a secondary set of links pointing to different parts of the current page (using in-page anchors or “local” links), this too could be wrapped in a nav element. 

As with section, there’s been some debate over what constitutes acceptable use of nav and why it isn’t recommended in some circumstances (such as in a footer). Some developers believe this element is appropriate for pagination or breadcrumb links, or for a search form that constitutes a primary means of navigating a site (as is the case on Google). 

This decision will ultimately be up to you, the developer. Ian Hickson, the primary editor of WHATWG’s HTML5 specification, responded to the question directly: “use [it] whenever you would have used class=nav”.