interactionsRAMS
Non-Interactive Element with Keyboard Handler
NEVER
NEVER: Use <div onClick> or <span onClick> for interactive elements. Use <button> for actions, <a>/<Link> for navigation. Non-semantic elements lack keyboard support.
Use semantic interactive elements instead of divs with handlers
Bad
Good
Why it matters
Rams ships this as a Critical checklist row, not prose. Our reading: bolting role, tabIndex, and onKeyDown onto a div is the expensive way to re-derive what <button> already gives you — focus, Enter/Space activation, and a correct screen-reader announcement. Reach for the semantic element first.
References