Accessibility gets treated like a phase-two nicety. In reality, the cheapest time to build an accessible site is while you're building it the first time.

Semantic HTML does the heavy lifting

Use a <button> for buttons and a <nav> for navigation, and you get keyboard support, screen-reader labels, and focus management for free. Most accessibility wins are just using the right element.

The quick audit

  • Can you reach every interactive element with the Tab key?
  • Does every image have meaningful alt text — or empty alt if decorative?
  • Is there a visible focus state?
  • Do colours meet contrast requirements?

An accessible site is simply a well-built site. The two aren't separate goals.