In the screenshots, the tab is still named Audits but it was renamed into Lighthouse in Chrome 83 You can check what version you're running at chrome://version.
Note: The screenshots in this section were taken with Chrome 69. DevTools shows you various configuration options. See also Make your website more readable. The text elements on a page have sufficient contrast ratios.A page is properly marked up for screen readers.In general, use the accessibility checks under the Lighthouse panel to determine if: See How To Do An Accessibility Review to learn more. The only way to find errors related to question #1 is to try using a page with a keyboard or screen reader yourself. Question #1 is just as important, but unfortunately DevTools can't help you there. In general, DevTools can help you fix errors related to question #2, because these errors are easy to detect in an automated fashion. Are the page's elements properly marked up for screen readers?.Can I navigate the page with a keyboard or screen reader?.When determining whether a page is accessible, you need to have 2 general questions in mind: This section explains how DevTools fits into your overall accessibility toolkit. # Overview of accessibility features in Chrome DevTools See Learn Accessibility if you'd like to learn how to develop accessible websites. See Navigating Chrome DevTools With Assistive Technology if you're looking for help on navigating DevTools with an assistive technology like a screen reader. The purpose of this reference is to help you discover all of the tools available in DevTools that can help you examine a page's accessibility. Are familiar with accessibility principles and best practices.Have a basic understanding of DevTools, such as how to open it.
This page is a comprehensive reference of accessibility features in Chrome DevTools.
0 kommentar(er)
