Start With Semantic HTML
Choose semantic HTML before custom controls when building common UI interactions.
The fastest accessibility fix is often choosing the right element before you style it. Native behavior is product behavior When you choose a native element, you are not just choosing markup. You are accepting a tested behavior bundle: focusability, keyboard activation, accessible name calculation, form participation, browser defaults, and platform expectations. That bundle is why a plain HTML form can still be usable without your component library. ARIA fills gaps, not basics ARIA can describe a custom widget, but it does not make that widget behave. If a div has role='button', you still owe it keyboard activation, disabled handling, focus…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in