Web accessibility (a11y) ensures services are usable by everyone, and developers must follow standards to avoid making the web inaccessible.
Disabilities can be permanent, temporary, or situational, and accessibility also benefits users with technical or environmental limitations.
The Web Content Accessibility Guidelines (WCAG) are built on four principles: Perceivable, Operable, Understandable, and Robust (POUR).
Test all interactive elements for focus visibility, logical tab order, and actionability using only a keyboard to find common issues.
Use screen readers like VoiceOver or NVDA to check for proper landmarks, descriptive links, alt text, and announcements for dynamic content.
Use built-in browser tools like Lighthouse, the Accessibility Pane, and emulation features to inspect the accessibility tree and simulate user conditions.
Integrate automated accessibility checks into your workflow using tools like the axe-cli to quickly find and report common violations.
Prioritize accessibility from the start by combining automated checks, manual testing, and feedback from real users with disabilities.
Sensory-Minds GmbH
Offenbach am Main, Germany
56:41Dennie Declercq
31:38Anuradha Kumari
29:59Konstantin Tieber
24:30Emma Dawson
35:39Chris Heilmann & Daniel Cranney
56:00Karl Groves
27:16Tanja Ulianova
23:33Maria Korneeva
Jobs that call for the skills explored in this talk.
LARAM SOFT LLC
Chicago, United States of America
Triumph Services
Richmond, United States of America
Active Internet Technologies, LLC
Indianapolis, United States of America
TestPros, Inc.
Sterling, United States of America
Ad Hoc, LLC
McLean, United States of America
University of Oregon
Eugene, United States of America
Ad Hoc, LLC
Kemp Mill, United States of America
