WCAG in Plain English

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.

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.

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.

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).

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.

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).

Color must not be the only way to convey information. Always provide an additional visual cue, like icon, text label, underline, shape, or pattern (e.g. striped, solid).

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.

Text contrast against its background must be at least 4.5:1 for normal text, or 3:1 for large text (over 24px, or bold and over 19px).

Text remains readable and usable when zoomed to 200%.