WCAG Guideline 2.6.1: Device Sensors Explained
Estimated read time: 6–7 minutes
Guideline 2: Operable
The Operable principle ensures that all users can interact with and control web content, regardless of their abilities. This includes making sure device sensors (like motion, orientation, or proximity) are never the only way to interact with content.
Guideline 2.6: Input Modalities (Extended)
Guideline 2.6 focuses on making it easier for users to operate functionality through various input methods, including device sensors.
What Is Guideline 2.6.1 Device Sensors?
"Functionality that can be operated by device sensors can also be operated by user interface components, and sensor-activated features can be disabled."
Guideline 2.6.1 Device Sensors is a Level A requirement in the Web Content Accessibility Guidelines (WCAG) .
- Any feature that uses device sensors (motion, orientation, proximity) must also be operable by a standard UI control (button, link, etc.).
- Exception: motion is essential to the function (e.g., step counter).
- Applies to mobile apps, games, and web content using device sensors.
Why Does It Matter?
- Inclusivity: Device sensors can be difficult or impossible for some users.
- Legal Compliance: Device Sensors is a Level A requirement in WCAG 2.1 and 2.2.
- Usability: Ensures all users can operate features regardless of device sensors.
For more, see W3C’s guidance on device sensors .
What Needs Device Sensor Alternatives?
- Tilt to scroll
- Shake to undo
- Any feature using device sensors
All must have alternative controls for sensor-based actions.
How to Make Device Sensors Accessible
- Provide alternatives to device sensors
- Allow users to disable sensor-activated features
- Document sensor feature options
- Test with users with limited mobility
For more, see the W3C's Device Sensors Techniques .
Common Mistakes to Avoid
- Only supporting device sensors
- No alternative for device sensors
- Not documenting sensor feature options
- Not testing with users with limited mobility
Differences Between A, AA, and AAA for Guideline 2.6.1 in WCAG 2.2
- Level A: Requires alternatives to device sensors and ability to disable sensor features. This is the core requirement for 2.6.1 and is mandatory for basic accessibility.
- Level AA: For Guideline 2.6.1, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AA.
- Level AAA: For Guideline 2.6.1, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AAA.
For more, see the W3C’s official documentation for 2.6.1 Device Sensors .
Quick Checklist
- Alternatives to device sensors are provided
- Sensor-activated features can be disabled
- Sensor feature options are documented
- Tested with users with limited mobility
Summary
Guideline 2.6.1 is essential for ensuring all users can operate your site. By providing alternatives to device sensors, you support users with disabilities, improve usability, and meet legal requirements. Test your site regularly and make sensor accessibility a core part of your development process.
Next Up