Superior Accessibility

Preserve the user's ability to perceive, understand, navigate, and operate the changed interface. Prefer native semantics and observable behavior over ARIA-heavy patches.

Establish the affected journey, interaction model, supported platform, and available verification tools before choosing a fix. Preserve product behavior unless an inaccessible interaction contract must change.

Structure and names

• Use the native element whose behavior matches the control.
• Give controls an accessible name that matches or includes the visible label.
• Keep heading order, landmarks, lists, tables, and form relationships meaningful.
• Use alternative text for informative images; keep decorative imagery out of the accessibility tree.
• Add ARIA only when native HTML cannot express the necessary relationship or state, and keep it synchronized.

Keyboard and focus