To ensure website accessibility, use a consistent navigational menu on each website page. Users with disabilities benefit with webpage predictibility. Menus should be appear in the same location on each page and items repeating in the same order.
Include the <nav> element with the <aria-label> that matches the name in the <ul>.

Whether by use of assistive technology or mouse, users can focus on components without changing their context. The links in the example below have a black border applied to support the WCAG 3.2.1 Success Criteria. When focus moves onto an element through tab key or mouse the user will know when to initiate the desired action.

                        <nav role="navigation" aria-label="Floral Shop">
                          <ul role="menu" aria-label="Floral Shop">
                          </ul>
                        </nav>
                    

                            nav > ul > li > a:focus{
                              border: 2px solid #000000;
                            }
                        

The “Skip Navigation” means users with assistive devices can avoid tabbing through all menu items just to reach the main content on the webpage, therefore saving them much time and frustration. Often, a website will have a “Skip Navigation’ which is only visible to screen readers as it works solely with assistive devices. This is accomplished using CSS. See Figure A.

"In order to support assistive devices, include a “Skip to main content” link before the header for keyboard users which is visible only when it has focus. This benefits keyboard users who can reach content with fewer keystrokes. Users can easily skip some sections which are not relevant to them."

WAI, WCAG Read about this Success Criteria.

.sr-only{
                              border: 0;
                              clip: rect(0,0,0,0);
                              height: 1px;
                              margin: -1px;
                              overflow: hidden;
                              padding: 0;
                              width: 1px;
                            }
                    

Figure A: “Skip Navigation’ is only visible to screen readers as it works solely with assistive devices. This is accomplished using CSS.

Read more about how this relates to Success Criterion 2.4.1

NOTE: This is only a visual representation.
To test out a working example, reload this webpage in a CHROME browser. Then press the TAB on your keyboard. This will make the "SKIP NAVIGATION" button visible at the top left of the page. Tap ENTER again.

A breadcrumb navigation is a secondary navigation that provides a trail of the user's location within a website. One can find their way back to other pages through a hierarchical manner.

"It is also helpful when a user follows a link directly to a page deep within a set of Web pages and needs to navigate that Web site to understand the content of that page or to find more related information." WAI, WCAG

Breadcrumb navigation should be arranged horizontally as text links to be most comprehensive to the user in websites that contain a large amount of pages.

                        <nav role="navigation" aria-label="Breadcrumb">
                          <ul role="menu" aria-label="Breadcrumb">
                          </ul>
                        </nav>
                    

"The WCAG Success Criterion 2.4.8 is helpful for people with a short attention span who may become confused when following a long series of navigation steps to a Web page."

WAI, WCAG Read about this Success Criteria.

NOTE: The WCAG Success Criterion 2.4.8 Location is not required for AODA compliancy as it is Levell AAA. However, it is recommended as it follows best practices.