responsibility: Code
Collection of success criterion where the responsibility falls under technical implementation and developer tasks.
1.1.1 Non-text Content
All images and other non-text content (like icons, charts, audio, CAPTCHAs, or controls) must have a descriptive text alternative that conveys their meaning. Purely decorative content can be hidden from assistive technologies (e.g. using an empty alt attribute).
1.3.1 Info and Relationships
Visual information and relationships (like labels, headings, or groupings) must also be conveyed in the code using semantic HTML (e.g. <label for="">
, <ul>
, <h1>
) or ARIA attributes (e.g. <aria-describedby>
, <role="group">
) so that assistive technologies can understand the structure.
1.3.2 Meaningful Sequence
Content must follow a logical and meaningful order in the code so it can be understood correctly by assistive technologies even if the visual layout differs.
1.3.4 Orientation
Content must remain readable and usable in both portrait and landscape orientation, unless a specific one is essential (e.g. in a piano app that requires landscape to show the full keyboard).
1.3.5 Identify Input Purpose
The purpose of common form fields (like name, email, or address) must be defined in the code so that browsers and assistive technologies can offer input support, such as autocomplete.
1.3.6 Identify Purpose
The purpose of regions and common elements must be defined in the code using semantic HTML or ARIA attributes, so that; assistive technologies can communicate their meaning, and; browsers can adapt or simplify the interface (e.g. hide non-essential content).
1.4.2 Audio Control
If audio plays automatically for more than 3 seconds, it must be possible to pause the audio, stop the audio, or adjust the volume, without using system-wide controls.
1.4.9 Images of Text (No Exception)
Text must be actual text, not images of text (no exception, not even for design or aesthetic reasons).
1.4.12 Text Spacing
Text remains readable and usable when spacing is changed using custom styles to at least 1.5× line height, 2× spacing after paragraphs, 0.12× letter spacing, 0.16× word spacing, without content being hidden, cut off, or broken.
1.4.13 Content on Hover or Focus
When additional content appears on hover or keyboard focus (including long press on touch), it must stay visible until dismissed or no longer valid, be dismissible (e.g. using the key), and remain visible when hovered or focused.