
HTML inert keeps an inactive area out of the interaction path
HTML inert can make a whole interface section unavailable to interaction. Pair it with clear state changes and test focus, visibility and restoration.

HTML inert can make a whole interface section unavailable to interaction. Pair it with clear state changes and test focus, visibility and restoration.

Keep a control’s visible wording within its accessible name so speech-input and screen-reader users can identify the same action.

A control’s HTML should match what it does. Use links for navigation and buttons for actions, then verify keyboard behaviour and accessible names.

Test a modal dialog’s focus entry, keyboard containment, dismissal and return path to make the interaction usable beyond the mouse.

Drag-and-drop interfaces need an alternative that works without dragging. Buttons or a move menu can offer the same result more accessibly.

Make links that open a new tab predictable with a clear advance cue, then test the behaviour with keyboard and assistive-technology users in mind.

Make an automatically moving carousel controllable with a reachable pause mechanism, readable state and testing beyond mouse hover.

Test whether keyboard users can see where they are on a website and move through controls in a meaningful order without getting trapped.