WCAG in Plain English

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.

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

Time limits must be avoided unless essential for the task (e.g. exams, auctions). If time limits are used, it must be possible to turn them off, adjust them to at least 10× the default, or extend them by at least 10×.

Content must not include time limits for reading or interaction, unless it’s part of a live event or time-based activity (e.g. auctions, broadcasts).

When (re-)authentication is required (e.g. after session timeout), all previously entered data must be preserved so the task can continue without starting over.

If inactivity could lead to data loss, a clear warning must be shown before the timeout, with enough time to react, and including an option to extend the session.

The visible text of a button, link, or form field must also be part of its accessible (programmatic) name.

No unexpected changes must happen when a field value changes (like auto-submit, reload, open new page).

Major changes (like open dialog, navigate, submit) must only happen when explicitly requested.