new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

IBM Carbon · all subjects

button/accessibility

6 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Design annotation required for icon-only buttons

Icon-only buttons without persistently displayed labels must be annotated with a label that will be exposed on hover or focus, for example label=Rename.

Button keyboard interaction: Tab, Space, Enter

Buttons can be reached by Tab key and selected with Space key or Enter key.

Icon-only button labels exposed on hover and focus

Icon-only buttons that do not persistently display a text label automatically expose their label on hover and focus.

Menu-opening buttons are separate components

When icon-only buttons are used to open menus, they are treated as separate components in Carbon. Refer to Dropdown and Overflow menu components for this pattern.

Repurposed links as buttons need Space key support

Where links have been repurposed as a button, they need to be coded so the Space key can also activate, since links are only activated by default by Enter key.

Toggle button aria-pressed attribute

Toggle buttons can be accessibility supported by changing the value of aria-pressed between 'true' and 'false' or with a change of name that reflects a change in the icon shape, for example 'play' or 'pause'.

Give your agent this brain