Our goal is to provide a consistent user experience for all users, whether they’re navigating with a mouse/touchscreen, keyboard, or screen reader.
An accessible product should:
- Give all users the same quality of experience
- Adapt to users and situations
Individually accessible elements and components are part of building accessible products, but the accessibility efforts need for manual testing. When designing new UIs, rely as much as possible on Wave existing components and follow accessible patterns. If you're creating a new component or pattern (one that doesn't exist in Wave), keep in mind accessibility practices before your implementation.
The Wave Design System team wants as many people as possible to be able to use Wave powered products. For example, that means you should be able to:
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- listen to most of the website using a screen reader
Aid development process
- How to audit Web a11y Video
- Use the a11y project checklist and aim for at least A level compliance
- Use axe dev tools for accessibility testing. Check more at deque Axe and learn how to use it with this Video
- Use Lighthouse Chrome extension for accessibility score. Check more at Web.dev a11y
- Use accessible queries when writing tests. This assume you are using testing-library