Testing for accessibility is a developer's responsibility to remove barriers for users with assistive technologies and create a more inclusive web.
Learn how to generate a Lighthouse report to get an initial score and a list of automated accessibility checks.
Understand how to read the Lighthouse report, including how to use the "learn more" links to understand complex issues like ARIA toggle fields.
Use a screen reader like VoiceOver to manually test interactive elements and discover issues that automated tools miss, such as unnamed controls.
The accessibility tree is a simplified version of the DOM that assistive technologies use to interpret a webpage's content and structure.
Use the full page accessibility tree in DevTools to inspect computed properties, identify incorrect `aria-hidden` attributes, and live-edit the DOM to fix bugs.
Use the DevTools inspector and color picker to identify and correct low color contrast ratios to meet WCAG standards.
Use the rendering tab in DevTools to simulate various vision deficiencies and test the `prefers-color-scheme` media feature for dark mode.
Use DevTools features to inspect page landmarks for navigation, visualize the source order of elements, and track the active focus element.
Explore powerful browser extensions like Wave, Accessibility Insights for Web, and Heading Maps to supplement the built-in DevTools features.
Jobs that call for the skills explored in this talk.