These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
- Accessible to all
- Lighthouse accessibility scoring
- Additional items to manually check #
- Custom controls have ARIA roles Learn how to improve your web page's accessibility by making sure custom controls have ARIA roles that assistive technologies can interpret.
- Custom controls have associated labels Learn how to improve your web page's accessibility by making sure that all custom controls have labels that assistive technology users can access.
- User focus is not accidentally trapped in a region Learn how to improve you web page's accessibility for keyboard users by preventing focus from being trapped in a region of the page.
- Interactive controls are keyboard focusable Learn how to make custom controls on your web page focusable so keyboard users can access them.
- Interactive elements indicate their purpose and state Learn how to improve the accessibility of custom controls on your web page by making their purpose and states clear to all users.
- The page has a logical tab order Learn how to make it easier for keyboard users to navigate your web page by placing tab stops in a logical order.
- The user's focus is directed to new content added to the page Learn how to make changes in your web app's state understandable to assistive technology users by moving focus to newly added content.
- Offscreen content is hidden from assistive technology Learn how to improve your web page's accessibility for assistive technology users by hiding off-screen content from assistive technologies.
- HTML5 landmark elements are used to improve navigation Learn how to improve the accessibility of your web page by providing landmarks that keyboard users can use to navigate.
- Visual order on the page follows DOM order Learn about visual-order-follows-dom audit.
- Custom controls have ARIA roles