Step 1 of 10
Start here: why can't some people finish our sign-up form?
This web accessibility training starts with a problem many product teams meet without knowing it: the new sign-up page passed design review and every test the team ran with a mouse, yet some people can't finish it at all. Watch the page read element by element, the way a screen reader and the Tab key meet it.
Each element on the page was read out, found wanting and fixed until it had a name, a role and enough contrast, and the reader could see where focus was. In this lesson you learn to find those problems on your own pages and check each fix.
What you'll do
- Sort real barriers into WCAG's four principles: perceivable, operable, understandable, robust.
- Read a page the way a screen reader does, and hear what it says about each element.
- Fix contrast, text alternatives, keyboard access, focus, labels and headings, each one checked live.
- Run a five-check pass on a new feature, the way a team does before release.
By the end you can
- Find the most common WCAG 2.2 level AA failures on a page without special tools.
- Fix each one and say which success criterion it meets.
- Run a short accessibility check before every release.
You need a browser. No accessibility background.