DocsDocs

Accessibility

What every component does for keyboard, screen readers, contrast, motion and touch, and what an app still supplies.

On this page

Behaviour

What every component does

Every envUI component works for everyone without extra work, and each component's page says what it does in detail.

  • Keyboard: everything works from the keyboard, in the order it shows.
  • Visible focus: a clear ring shows where the keyboard is.
  • Screen readers: controls, regions and messages are announced by their name and state.
  • Contrast: text, edges and focus are checked for contrast in all four themes.
  • Reduced motion: when people ask for less motion, things fade instead of move.
  • Forced colors: with the system's own high-contrast colors, every state stays visible.
  • Touch: on a touchscreen, controls grow big enough for a finger.

Try the keyboard

Tab moves through the controls in the order they show.

Rules

envUI can't know an app's own words: the app, or the agent that builds it, still supplies them.

  • Labels: a visible label for every field, and a name for every button that is only an icon.
  • Text for pictures: a description of every image that carries meaning.
  • Headings: headings in order, so people can find their way around a page.
  • Error messages: messages that say what went wrong and how to put it right.

Words to use

Ask an agent for accessibility in these words; envUI does the rest in every component.

Name this button

Gives a button that is only an icon a name that screen readers say.

Keyboard order

Puts controls in the order they show, so the keyboard moves through them as people read.

High contrast

Stronger text and edges, chosen by the reader or followed from their system.

Respect reduced motion

Makes the app's own animations fade instead of move when people ask for less motion.