Nav bar - consistent user experience across related WAI resources

[shawna-slh]

Important context: The new design is optimized for Understanding, Techniques, Supplemental Guidance, ARIA APG that have several links in the navigation bar -- e.g., to list of all, parent page, previous, next. e.g.:

The "About..." link:

• Is important for new users — especially those who land on a page and don't have background in WCAG or such. It will rarely be wanted by regular users.
• Is located in the header right after the tagline/strapline, where it is easy for newbies to find and repeat users to ignore.

---

For Rules, there are at least two questions about the navigation:

1. Do we want to be consistent with the related resources and have the "About..." link in the header?

• Unless there is a compelling reason to break consistency, it seems the best user experience is to have the About link in the same place for all related resources.

2. Do we want to provide other navigation?

• afaik, there isn't really a parent for each Rule, and the order is alphabetical, not otherwise related. afaik, users will not usually "walk" the rules - going from one to the next to the next. Therefore, seems low priority to have <-previous next->. And, I don't see any reason not to, if it is within someone's priority to code.

[WilcoFiers]

Personally, I preferred the tab-style look we had before. It's a far more familiar pattern than the parent / previous / next type of navigation. Having the "about" link in the header doesn't feel intuitive to me. I wouldn't find it there. I only recently noticed the WAI site has its own about link next to the search bar.

If that's an option, I'd rather go back to tabs, and have "about" be one of them, instead of having it in the head. I don't expect people will browse rules one after another. Then again, I wouldn't think that's all too common for techniques or understanding documents either.