A tiny audit of the six most common failures
Real tools (axe, Lighthouse) do this far more carefully. Fix each failure in the HTML and run again until every count is 0 and the language is set.
Accessibility means people with disabilities can use your page with their own tools; WCAG is the shared rulebook, AA is the level most laws ask for, and good HTML gets you most of the way.
Change the code and press Run (Ctrl+Enter). Predict what will happen first, then break it on purpose and read what changes. Your edits are saved and match the lesson page.
Ready for more? This phase has 6 hands-on exercises with automatic checks.
Practice questions
Write the code in the editor, run it, then open the model answer to compare.
Write the HTML for a newsletter sign-up with one email field and a button so that a screen reader announces the field's name and the button's name. Make the page language English.
Using the contrast function from the first example, check #ffffff text on a #1a73e8 blue button. Does it pass AA for normal text?
Explain it without notes
What is the accessibility tree, and why does it matter which HTML element you choose?
What do the four POUR principles mean? Give one example of each.
What is the difference between WCAG levels A, AA and AAA, and which level do teams usually target?
Give three reasons a business should invest in accessibility.
Preview
Console
Nothing logged yet.Expected console output
Page language set? false
Images without alt: 1
Inputs without a label: 1
Empty links: 1
Empty buttons: 1