Search the Guide
New in WCAG 2.2
When page controls like buttons and form inputs are small, it's much harder to hit the target area accurately without accidentally activating a different control. This can especially happen on mobile devices, and frustrate people who have difficulty with fine motor control. Making targets big enough or giving them enough space can help prevent accidentally clicking the wrong control.
Smartphones and tablets can use motion sensors to make a particular feature or content work (tilting, shaking, etc.) However, for users that may need a device in a fixed position, or can't move the device in a particular motion, that feature or content may be unusable. Some users may also activate the motion accidentally, starting an action that they don't want.
Scalable vector graphics (SVGs) need additional accessibility information to be conveyed properly to all users. SVG markup by itself can produce a confusing output for anyone using a screen reader. If the SVG is acting as an image, it should have a text alternative, similar to images with all text.
Assistive technologies will read the caption or accessible name of tables on your page, making it especially important to have unique names/captions for each table. Multiple tables on a page without captions will make it difficult for assistive technology to tell one table from another.
Audio descriptions allow people who are blind, have low vision, or other vision disabilities to hear what's happening or displayed on the screen that they can't see. Audio descriptions are an additional audio file that can be played over a video to describe the visual content in order to progress with the narrative.