Improve accessibility for the page base components.
Review Request #10938 — Created March 4, 2020 and submitted
This updates the base template and page-level UI components (top header
bar, search, navigation, and sidebar) to better meet accessibility
We're now using more specific tags for many of thes elements:
- The top bar now uses
- The navigation areas in the top bar use
- The page sidebar uses a standard
<div>, but is split into a
<footer>for use with the mobile menu
- Individual sidebars should now use
on what's appropriate for that sidebar
- The main content area uses
Some ARIA roles and labels have been added to parts of these components
in order to provide context to screen readers.
This is not comprehensive, but does improve what we've had quite a bit.
The page now has distinct landmark areas, which can be more easily
accessed when using assistive technologies.
Checked that the page continues to render correctly in all major
Inspected the landmark areas using a browser extension, verifying the
landmark trees and labels.
Also inspected using Firefox's Accessibility tree.
I know some people are interpreting <aside> occurring on its own (i.e. outside of <article>) as suitable for something like ...
- Removed usage of
page-sidebar, and in fact any landmarks.
- Added landmark information to the actual
<section>. We'll now make these the landmarks instead, as these are going to have more context as to their purpose, helping screen readers.
- Tested the landmarks and navigation with a screen reader. (There's still a lot to do here.)
Revision 2 (+146 -76)
Checks run (2 succeeded)