Change Details

### Background Landmark regions are an important way people using assistive tech browse webpages. Currently most wiki pages easily have 10+ navigation regions depending on the page and wiki. These nav regions aren't always well labeled or easily understood (i.e. "Navigation navigation"), and they clutter up the DOM making it harder for users to get to the content they need (i.e the main landmark region or the contents of a menu dropdown). ### Suggested behavior Many of these landmarks can be combined or removed. I suggest creating 3 new regions roughly corresponding to user links in the top right, the sidebar links, and the links that appear above wiki articles. Navboxs can also contribute a fair bit of clutter, as every Navbox uses a navigation role. This is less of a priority because they are located after the main content, but it could be worth looking into updating that template, and wrapping all Navboxes' under a single navigation region ### Developer notes This can be accomplished by removing the nav element from the Menu mustache template. While we could easily swap out the nav element with a div, this means that we would lose labeling for the default and tab menus. This should be acceptable considering those menus will be enclosed by new nav landmark regions that presumably would have better labels. We also want to consider refactoring the Menu template to conditionally add a heading/label for only the portlet and dropdown menu types. Considering the menu types mostly all have different designs and HTML requirements, a refactor could make the behavior and styles for the menu types more explicit and easier to understand. | | Default | Portlet | Tab | Dropdown | | Requires visual label | no | yes | no | no | | Requires screenreader accessible label | no | yes | no | yes |

### Background Landmark regions are an important way people using assistive tech browse webpages. Currently most wiki pages easily have 10+ navigation regions depending on the page and wiki. These nav regions aren't always well labeled or easily understood (i.e. "Navigation navigation"), and having too many nav regions can make it harder for users to access other landmarks (i.e the main landmark region). ### Suggested behavior Many of these landmarks can be combined or removed. I suggest creating 3 new regions roughly corresponding to user links in the top right, the sidebar links, and article links. ### Developer notes This can be accomplished by removing the nav element from the Menu mustache template. While we could easily swap out the nav element with a div, this means that we would lose labeling for the default and tab menus. This should be acceptable considering those menus will be enclosed by new nav landmark regions that presumably would have better labels. Removing the nav element from the Menu temple also means we can remove the `aria-hidden` attribute from the label, as the label is no longer being repeated.

### Background Landmark regions are an important way people using assistive tech browse webpages. Currently most wiki pages easily have 10+ navigation regions depending on the page and wiki. These nav regions aren't always well labeled or easily understood (i.e. "Navigation navigation"), and they clutter up the DOMhaving too many nav regions can makinge it harder for users to get to the content they needto access other landmarks (i.e the main landmark region or the contents of a menu dropdown). ### Suggested behavior Many of these landmarks can be combined or removed. I suggest creating 3 new regions roughly corresponding to user links in the top right, the sidebar links, and the links that appear above wiki articles. Navboxs can also contribute a fair bit of clutter, as every Navbox uses a navigation role. This is less of a priority because they are located after the main content, but it could be worth looking into updating that template, and wrapping all Navboxes' under a single navigation regionarticle links. ### Developer notes This can be accomplished by removing the nav element from the Menu mustache template. While we could easily swap out the nav element with a div, this means that we would lose labeling for the default and tab menus. This should be acceptable considering those menus will be enclosed by new nav landmark regions that presumably would have better labels. We also want to consider refactoring the Menu template to conditionally add a heading/label for only the portlet and dropdown menu types. Considering the menu types mostly all have different designs and HTML requirementsRemoving the nav element from the Menu temple also means we can remove the `aria-hidden` attribute from the label, a refactor could make the behavior and styles for the menu types more explicit and easier to understand. | | Default | Portlet | Tab | Dropdown | | Requires visual label | no | yes | no | no | | Requires screenreader accessible label | no | yes | no | yes |s the label is no longer being repeated.