Inspect a UI component for programmatic name, role, state, and value before approving it.
Accessible components expose a machine-readable contract. Name The name is what software can identify and present to the user. For controls, it should answer: what action or field is this? Icon-only controls need explicit naming. Visible-label controls usually need the accessible name to include that visible text. Role The role tells the user what kind of interaction to expect. Button, link, checkbox, switch, tab, combobox, and dialog all imply different keyboard models and mental models. A generic element with click behavior is not enough. State and value States and values tell the user what has changed. Expanded, selected, checked, disabled,…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in