Closed rosy1280 closed 4 years ago
If you choose to use aria labels, you should also make sure that HTML Landmarks are properly marked as well. If you choose not to go with aria labels, this should be broken out into a separate ticket and include in Epic #330
@rosy1280 I've updated the documented inputs, searches, and selects with ARIA labels and roles for the header and navigation.
Changes HH will need to make in velocity to match the pattern library.
input.search-menu-toggle
should have an aria label that matches the label of the corresponding search option. .header
as a parent of .header-main
): Add role="banner"
and aria-label="Main navigation and search"
.nav-menu-main
): Add aria-label="Main navigation"
and role="navigation"
.subnav-menu-main
): Add aria-label="Submenu navigation"
.nav-menu-utility
): Add aria-label="Utility navigation"
.footer
): Add aria-label="Main footer"
.search-menu-toggle
): Add aria-labels
for each search optioninput.-search.-[big / small].search-box
): Add aria-label="Main search text input"
.branding-header-dropdown-menu
): Add aria-label="Select a location"
<title>
element as first child of <svg>
element with "Dismiss notification" as the text node within <title>
.aria-label="Enter a name, title, library, phone number, or email to filter the list of staff"
aria-label="Enter keywords to search for a service"
aria-label="Select a subject area to filter the list of subject librarians"
The attached report from CPA suggests adding either labels or aria attributes to form elements. On our site these appear specifically in the following locations:
Consider which of the options they suggest makes the most sense and implement them.