The goal of digital accessibility is to make content more useful for people with disabilities, and in most cases, the best way to do that is to code websites with simple HTML. However, that’s not always practical: The modern internet thrives on interactivity, and while HTML has come a long way, it has limitations.
WCAG SC 3.2.2, “On Input”
Here’s the full text of this success criterion:
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
WCAG SC 2.2.1, “Timing Adjustable"
This guideline requires websites to give users control over events that have time limits. Users should be able to turn off, adjust, or extend time limits unless it is essential.
WCAG SC 2.1.2, “No Keyboard Trap”
Here’s the full text of this guideline:
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.
Remember, many people browse the web without a mouse — keyboard accessibility is a fundamental part of web design.
Related: Why Keyboard Traps Are One of the Most Frustrating Accessibility Issues
- Test your content frequently. Access your web page with a keyboard alone; does everything work as expected?