Accessible by Design

Some of the people who visit your page can't see the screen, can't use a mouse, or zoom the page to read it, and many companies and schools must make their sites accessible by law. You will see a page the way a screen reader and a keyboard user meet it, use ARIA only where HTML has no element for the job, and test a page yourself.

Updated

Why Accessibility

  1. Who Accessibility Helps (Apprentice): Accessibility means people can use your page however they browse, and it helps far more people than you might think, from a screen-reader user to someone holding a baby in one arm.
  2. What a Screen Reader Hears (Journeyman): A screen reader announces each part of a page by its role, its name and its state, all read from your HTML, and the developer tools show you exactly what it will say.

Keyboard and ARIA

  1. Keyboard Use and Focus (Journeyman): Everything on a page should work with the keyboard alone, and it does when you use real links, buttons and form fields in a sensible order, add a skip link, and keep the focus ring visible.
  2. ARIA: When HTML Isn't Enough (Freelancer): ARIA attributes change what a screen reader announces, never how an element behaves, so you use them only where HTML has no element or attribute for the job, such as naming an icon-only button.

Testing Accessibility

  1. Testing a Page for Accessibility (Journeyman): A repeatable accessibility check takes about fifteen minutes, keyboard only, a screen reader, Lighthouse and axe, 200% zoom and captions, and it finds the barriers a person meets and a tool misses.

Exercise: Audit the Movie Theater Page

  1. Exercise: Audit the Movie Theater Page (Journeyman): Run a full accessibility audit on the Starlight Cinema's showtimes page, log the ten barriers you find, fix the HTML, and let the tests confirm every fix.