theme: Wording
How language, tone, and phrasing impact accessibility.
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.3 Sensory Characteristics
Instructions and descriptions must not rely on sensory features alone, like color, shape, size, visual location, or sound. Always provide additional text to clarify meaning.
2.4.2 Page Titled
Each page must have a unique and descriptive that reflects its topic or purpose.
2.4.4 Link Purpose (In Context)
The purpose of each link must be clear from the link text itself, or the surrounding context.
2.4.6 Headings and Labels
Headings must describe what follows. Labels and buttons must clearly communicate what information is needed or what action will happen.
2.4.9 Link Purpose (Link Only)
The purpose of each link must be clear; from the link text alone; without relying on surrounding context.
3.1.1 Language of Page
Each page must have a <html lang=""> attribute that matches the main language of the page.
3.1.2 Language of Parts
Any parts of the content in a different language must be marked with the correct lang attribute. Expressions borrowed from another language (like “déjà vu” in English) do not need this, unless pronunciation or understanding would be affected.
3.1.3 Unusual Words
Unusual terms, jargon, or figurative language should be avoided when possible, or explained the first time they appear.
