Intro to Git — Snapshots, Branches & Sharing
WorkshopyOfficial10 stepsQuiz9 interactiveDiagram
gitversion controlbeginners
Web accessibility training on WCAG 2.2: use a page by keyboard and screen reader, measure contrast, fix labels, focus and headings, and check every fix.

WorkshopyOfficial
78 lessons · used by 2 teachers
Sign in to copy it to your workspace. It’s free.
10 steps · 2 quizzes · open any step, or read it here
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.
Interactive · One sign-up page, read element by element — try it in the lesson
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.
You need a browser. No accessibility background.
Web accessibility means people with disabilities can use the page: people who are blind and use a screen reader, people with low vision who zoom to 200% or need strong contrast, people who can't use a mouse and work with a keyboard, switch or voice control, Deaf and hard-of-hearing people, people with cognitive or learning disabilities. It also helps everyone else: a phone in sunlight, a broken trackpad, a noisy open-plan office.
WCAG (the Web Content Accessibility Guidelines) is the W3C standard most teams measure against. Version 2.2 became a W3C Recommendation in October 2023. It is organised in four principles, known as POUR:
| Principle | The question it asks | An example success criterion |
|---|---|---|
| Perceivable | Can people get the content, with whichever senses they use? | 1.1.1 Non-text Content: images have text alternatives |
| Operable | Can people use every control and move through the page? | 2.1.1 Keyboard: everything works from a keyboard |
| Understandable | Can people follow the content and the way it behaves? | 3.3.2 Labels or Instructions: fields say what they want |
| Robust | Can browsers and assistive technology read the code reliably? | 4.1.2 Name, Role, Value: controls expose what they are |
Each principle holds guidelines, and each guideline holds testable success criteria with a number (1.4.3) and a level:
Version 2.2 added nine success criteria, among them 2.4.11 Focus Not Obscured (Minimum) (AA, covered in the focus step) and 2.5.8 Target Size (Minimum) (AA, targets of at least 24 by 24 CSS pixels, with exceptions). It also removed 4.1.1 Parsing, which modern browsers made unnecessary.
Try it: four barriers a team really shipped. Sort each one into the principle it breaks.
Interactive · Sort four real barriers into POUR — try it in the lesson
Takeaway: POUR names four different ways a page can shut people out, and level AA is the bar most teams are held to.
A screen reader (NVDA or JAWS on Windows, VoiceOver on Macs and iPhones, TalkBack on Android) turns the page into speech or braille. It doesn't see your layout. It reads what the browser exposes in the accessibility tree: for each element a role (heading, link, button, edit text), a name (the words that identify it) and its state (required, checked, expanded). Exact wording differs between screen readers, but the parts are the same.
The keyboard sees another slice of the page: Tab moves only between interactive elements (links, buttons, fields), in the order of the code, and a ring shows which one has focus. And a sighted user with low vision sees colours and sizes, so contrast decides whether text can be read at all.
One sign-up page, three ways in. Every fix in this lesson follows the same loop:
Try it: press Next element to move down the Brightdesk sign-up page as a screen reader does. On each element, read what is announced and why it fails, press Fix this one, and read it again.
Interactive · Read the sign-up page the way a screen reader does — try it in the lesson
The page looked finished the whole time. Every barrier was in what the page exposes, not in how it looks: a missing name, a missing role, a removed focus ring, a grey too pale to read.
Takeaway: an accessible page gives every element a name, the right role and a visible focus, with enough contrast to read. Find, fix, check, one element at a time.
Contrast ratio compares the relative luminance (brightness) of two colours, from 1:1 (the same colour) to 21:1 (black on white). It is a number, so it is tested, not judged by eye: any contrast checker (in the browser's developer tools, or a free web checker) gives it.
What WCAG 2.2 asks at level AA:
| What | Minimum ratio | Success criterion |
|---|---|---|
| Normal text | 4.5:1 | 1.4.3 Contrast (Minimum) |
| Large text: at least 24 px, or at least about 18.7 px bold (18 pt / 14 pt bold) | 3:1 | 1.4.3 Contrast (Minimum) |
| Parts of controls you need to see (a field's border, a checkbox, a focus ring) and meaningful graphics | 3:1 against what is next to them | 1.4.11 Non-text Contrast |
At level AAA (1.4.6 Contrast (Enhanced)) the text minimums rise to 7:1 and 4.5:1. Logos and disabled controls are exempt.
Two habits that save rework: check the ratio when a colour is chosen, not after launch; and remember that a pale grey placeholder or hint is still text. #767676 on white is 4.54:1 and passes; #777777 is 4.48:1 and fails. The line is that sharp.
Try it: three parts of a sign-up form are too pale. Drag each slider until its ratio passes. Notice which minimum each one needs.
Interactive · Measure and fix the contrast on a sign-up form — try it in the lesson
Takeaway: 4.5:1 for normal text, 3:1 for large text and for the parts of controls people need to see. Measure it, every time.
1.1.1 Non-text Content (level A) asks for a text alternative for every image that carries meaning, and for decorative images to be hidden from assistive technology. In HTML that is the alt attribute, and it is always a decision about purpose, not appearance:
alt="", an empty alt. The screen reader skips it.Don't start with "image of" or "picture of": the screen reader already says it is an image. An icon inside a button gets its name on the button (aria-label, or visually hidden text) and aria-hidden="true" on the icon itself.
Try it: four images on Brightdesk's support portal. Pick the markup for each and read what a screen reader would say.
Interactive · Give each image on the support portal the right text alternative — try it in the lesson
Takeaway: ask what the image is for. A link names its destination, a chart gives its point, a decoration stays silent.
Four questions on the first part of the lesson.
Question 1. A video for new employees has no captions. Which principle does it break?
Question 2. A help-centre page should meet WCAG 2.2 level AA. What must it meet?
Question 3. Grey body text on a white page measures 4.2:1. At level AA, does it pass?
Question 4. A wavy line between two sections is pure decoration. What alt text should it have?
2.1.1 Keyboard (level A): everything that can be done with a mouse can be done with a keyboard (the one exception is input that depends on the path of the movement, such as freehand drawing). Many people depend on it: screen reader users, people with tremors or limited hand movement, people using switches or voice control (which act like a keyboard), and power users.
How the keyboard moves:
Most keyboard failures come from one habit: building a control out of a <div> or <span> with a click handler. It looks right and works with a mouse, but it isn't focusable, doesn't react to Enter or Space and has no role. A real <button>, <a href>, <input> or <select> gets all of that from the browser for free. Avoid positive tabindex values (tabindex="3"): they pull elements out of the reading order.
Try it: a ticket toolbar in the support portal. Tab through it, find the control Tab never reaches, then fix it and close the ticket with the keyboard alone.
Interactive · Tab through a ticket toolbar without a mouse — try it in the lesson
Takeaway: use the native element that does the job. A <div> that acts as a button shuts keyboard users out.
Reaching a control isn't enough: people have to see where focus is.
outline: none, added because the ring "looked ugly" on a mouse click. If the default ring doesn't suit the design, design a better one; :focus-visible shows it for keyboard users without showing it on every mouse click.scroll-padding on the scrolling container, as tall as the sticky bar, so the browser scrolls focused elements clear of it.WCAG 2.2 also added 2.4.13 Focus Appearance at AAA (how big and how contrasting the indicator is). Even at AA, a ring with 3:1 contrast against its surroundings (1.4.11) is the safe habit.
Try it: Tab down the help centre's article list. First the focus is invisible; then, lower down, the cookie bar swallows it. Fix both.
Interactive · Find the focus on a help-centre page — try it in the lesson
Takeaway: a keyboard user must always be able to see the focus, and nothing your page puts on top may hide it completely.
Every control needs a name, and the user needs a way to know what to enter:
The patterns to use:
<label for="email"> tied to the field's id. Clicking the label then puts the cursor in the field, a bonus for everyone. Add autocomplete="email" and the browser can fill it in.aria-describedby, so they are read after the name.aria-label="Attach a file" on the button, aria-hidden="true" on the icon. Better still, show the word.The first rule of ARIA: if a native HTML element does the job, use it. ARIA changes what assistive technology hears, never how the element behaves.
Try it: three controls from Brightdesk's contact form. For each, pick the markup and listen to what a screen reader would say.
Interactive · Give every control a name a screen reader can say — try it in the lesson
Takeaway: a visible label tied to its field, and a name on every button. If the screen reader says only "edit text" or "button", it isn't done.
Many screen reader users find their way through a page by its headings: they open a list of headings, or jump from one to the next with a key (H in NVDA, JAWS and VoiceOver's quick navigation). Headings are their table of contents.
What to do:
<h1> to <h6>, not a big bold <div> or a <p><strong>. Text that only looks like a heading fails 1.3.1 Info and Relationships (A): the structure is visible but not in the code.<h1> that says what the page is, <h2> for its sections, <h3> for parts of a section.Try it: a help article in the support portal. Set each line's level and watch the headings list a screen reader would show.
Interactive · Fix the headings of a help article and watch its outline — try it in the lesson
Takeaway: headings are the page's outline in the code. One H1, sections as H2, no skipped levels, and words that say what is in each section.
Accessibility that is checked once, before a big launch, decays with every sprint. What lasts is a short pass that anyone on the team runs on every new feature, in about the time it takes to make a coffee:
Automated checkers (Lighthouse in Chrome, axe and similar browser extensions) are worth running too: they catch missing alt attributes, low contrast and missing labels in seconds. But they find only part of the problems. No tool can tell whether an alt text is right, whether the focus order makes sense or whether a label is clear. The manual pass is the part that matters.
When a check fails, file it like any other bug: what, where, the steps to reproduce, who it affects and the success criterion. "Fails 2.1.1 Keyboard: the date picker can't be opened with Enter or Space" is something a developer can fix and a tester can verify.
Try it: the team built a new "Export tickets" page. Run the five checks on it and name what each finding fails.
Interactive · Run the five checks on a new feature before release — try it in the lesson
Takeaway: five checks, every release, by whoever builds the feature. Find, fix, check, and write the success criterion in the bug.
Six questions on the whole lesson.
Question 1. A custom "Close ticket" control is a div with a click handler. What is the most robust fix?
Question 2. The design removes the focus outline with outline: none and adds nothing in its place. Which success criterion does that fail?
Question 3. A sticky cookie banner completely covers the link that has keyboard focus. Which success criterion, new in WCAG 2.2, does that fail?
Question 4. An email field has only placeholder text "Work email" inside it. What is the problem?
Question 5. A button shows only a paperclip icon. A screen reader says "button". Which fix gives it a good name?
Question 6. Which of these does WCAG 2.2 level AA require? (pick all)
Workshopy shares this lesson under CC BY 4.0. Anyone may use and change it, with credit to you. Anyone can learn it here, free. A copy in your workspace is yours to change and run live; your students never need an account.
Version 1Current
· First published
Copies are made from the current version. A copy you already have doesn’t change.
WorkshopyOfficial10 stepsQuiz9 interactiveDiagram
gitversion controlbeginners
WorkshopyOfficial16 steps2 quizzes15 interactiveDiagram
workshopyproduct touronboarding
WorkshopyOfficial10 steps2 quizzes10 interactive
data-literacystatisticsmean and median
WorkshopyOfficial10 steps2 quizzes9 interactive
designusability testingthink-aloud
WorkshopyOfficial10 steps2 quizzes10 interactive
designempathy maphow might we
WorkshopyOfficial9 steps2 quizzes9 interactive
designcoloraccessibility
Comments
No comments yet. Be the first to say how it went.