responsibility: Code
Collection of success criterion where the responsibility falls under technical implementation and developer tasks.
1.1.1 Non-text Content
Images should have descriptive (alt) text.
1.3.1 Info and Relationships
Information or relationships between content that is visual is also conveyed through the code, via HTML or ARIA (for example the for attribute on a form label, or aria-describedby on an input that has hint text).
1.3.2 Meaningful Sequence
The visual presentation of the content matches what’s read out by a screen reader.
1.3.4 Orientation
Rotating a device from portrait to landscape doesn’t stop everything being perfectly readable and usable.
1.3.5 Identify Input Purpose
The purpose of form fields can be identified by the browser, so that auto-complete suggestions can be offered in a dropdown.
1.3.6 Identify Purpose
Landmark regions and personalization semantics are used, allowing browser tools to remove non-essential content or add identifying icons to specific elements on the page.
1.4.12 Text Spacing
Users can increase letter, word, line, and paragraph spacing without cutting off content or breaking functionality.
1.4.13 Content on Hover or Focus
Tooltips can be dismissed, usually via the esc key, the text in the tooltip can be selected, and they don’t time out on their own.
1.4.2 Audio Control
Auto playing audio that lasts more than 3 seconds can be turned down or stopped.
1.4.9 Images of Text (No Exception)
Text is actual text; never images of text.
