Accessibility and Quality
Build pages everyone can use: alt text, keyboard and focus, ARIA, accessible names, testing with real tools, best practices and interview answers.
Accessibility (often shortened to a11y: an a, 11 letters, a y) means building pages that people with disabilities can perceive, understand, navigate and use. That includes people who are blind and use a screen reader, people who can't use a mouse, people with low vision, colour blindness, hearing loss, tremors or memory difficulties, and everyone having a temporary or situational problem, like a broken arm or bright sunlight on a phone.
This phase turns everything you learned so far into quality work. You'll write alt text that helps, make every control reachable and visible with the keyboard, learn what ARIA is (and why the first rule of ARIA is not to use it), see how the browser computes the accessible name of every element, and test pages with the validator, Lighthouse, axe, a screen reader and the DevTools accessibility tree.
It ends with the common HTML mistakes seniors spot in code review, and a set of HTML interview questions with model answers that pull the whole course together. Accessibility continues in the CSS course (contrast, focus styles, reduced motion) and the JavaScript course (managing focus and keyboard events).
Practise this phase
Hands-on exercises: write the code, see your page live, and press Check to have it tested automatically.