Was this page helpful? Please submit feedbackopens in new window so we can improve.
Accessibility is a shared responsibility. We want our products to be accessible and welcoming for all people. Overarching strategies guide our work, best practices are integrated throughout our design system, and we practice inclusive design.
We aim to be compliant with WCAG 2.1 (Level A and AA) and follow the four principles of accessibility.
The Design System site itself is evaluted regularly and the most recent report is available for review. Changes related to accessibility are tracked in What's New.
We extend HTML by using features from the Accessible Rich Internet Applications (WAI-ARIA or ARIA) specification to build in functionality that is not available in native HTML. This is done in a purposeful manner and with guidance from the W3C’s ARIA design patterns library to make our products more accessible.
Having a clear hierarchy helps everyone. We write for people using headings and lists, use consistent patterns in our reusable designs, and love testing and talking about information architecture.
We are deep believers in the power of good content. Our content guidelines consider how people may come to our content, as well as how they read on the web, and we use plain language whenever possible.
We write with care to acknowledge our users and make them feel welcome at the library.
This means making intentional choices in how we write about people and includes using inclusive language in how we talk about gender, age, race, ethnicity, nationality, and ability, as well as recognizing and eliminating racist and bigoted phrases and terms.
We also follow plain language practices recognizing many people using the library speak or read English as their second language.
Our color palette provides a set of options to support consistency and create accessible combinations.
We design and develop knowing that some people cannot (or choose not to) use a mouse.
In our designs, anything that can be seen by hovering with a mouse is also accessible through keyboard focus and by other assistive technologies (such as screen readers). We pay attention to the order of elements on the page and make sure the keyboard focus is visible.
In addition to our design and development practices, we test our visual elements and reusable designs for accessibility with automated and manual techniques.
These include native and third-party tools like:
We recognize that no manual or automated tests can catch all barriers that people with disabilities may encounter with our content, products, and services. We actively include people with disabilities and those who use assistive technology in product design, testing, and development work to drive human centered improvements.