Why Accessibility Matters

Web accessibility means building pages that people with disabilities — visual, auditory, motor, or cognitive — can still use effectively. This includes people using screen readers, keyboard-only navigation, voice control, or screen magnifiers.

A few numbers to consider: the World Health Organization estimates that over a billion people globally live with some form of disability. Beyond ethical responsibility, many countries have legal accessibility requirements for public and commercial websites, and accessible sites tend to rank better in search engines and work better for everyone — including people using slow connections or older devices.

Most accessibility wins come from doing ordinary HTML correctly, not from adding exotic extra code:

<!-- Bad: no way for a screen reader to know this is a button -->
<div onclick="submitForm()">Submit</div>

<!-- Good: a real button carries built-in keyboard support and semantics -->
<button onclick="submitForm()">Submit</button>

A <div> styled to look like a button gets none of the following for free: it isn't reachable by pressing Tab, isn't announced as a button by screen readers, and doesn't respond to pressing Enter or Space. A real <button> gets all of this automatically, at zero extra cost.

The single biggest accessibility habit to build early: reach for the semantic tag that already does what you need (<button>, <a>, <label>, heading tags) before reaching for a generic <div> styled to look similar.