テーマ： aria

• ARIA roles: why a native HTML element beats a div with a role

  The W3C's first rule of ARIA use is to prefer a native HTML element or attribute that already has the semantics and behaviour required; ARIA only changes what assistive technology is told, never what the element does. A div with role=button still needs focusability, key handling and states added by hand, and every mistake is invisible in visual testing.

  article · en · reviewed · 知識の基準日 2026-09-16

• Keyboard navigation in composite widgets: roving tabindex, arrow keys and Escape

  Tab and Shift+Tab move between components; arrow keys move inside a component such as a tab list, toolbar, menu or radio group. Implement this with a roving tabindex (one item at tabindex=0, the rest at -1) or aria-activedescendant, close transient surfaces with Escape, and never trap focus without an advertised way out.

  article · en · reviewed · 知識の基準日 2026-09-16

機械可読： JSON