Accessibility review

Most accessibility failures are not exotic. They are a div that should have been a button, a form field with no label, and a modal that traps nobody's focus. Fixing the common handful gets you most of the way, and they are cheap when caught in review and expensive later.

The fastest useful test: put the mouse away. If you cannot complete the flow with a keyboard, neither can a large group of users, and no amount of ARIA fixes it.

1. Use the right element before adding anything

The single highest-leverage rule. A native <button>, <a>, <input>, or <label> brings keyboard handling, focus, roles, and states for free. A div with a click handler brings none of it, and reproducing them correctly takes far more code than people expect.