Published lesson · 30 minutes

Run an accessibility review and fix the highest-impact issue

Objective: Review a small website with keyboard and automated checks, then prioritise a concrete fix based on who it affects and what it prevents.

The core idea

This lesson introduces run an accessibility review and fix the highest-impact issue. Review a small website with keyboard and automated checks, then prioritise a concrete fix based on who it affects and what it prevents. Begin with one small goal and make sure the result serves a real visitor or collaborator. The examples use fictional community information, so they can be adapted without exposing anyone’s private details.

The key idea is this: Automated tools can identify some missing names, contrast risks and invalid relationships, but they cannot decide whether an instruction makes sense or whether a sequence feels predictable. Human checks are needed alongside automated reports. Keep that idea separate from visual decoration or tool-specific habits. When you can explain why a choice helps the intended task, it becomes easier to review the result and to choose a different approach when the situation changes.

Put it into practice

Apply it to this situation: Review a fictional community events page by first naming the task: find an event, understand its date and contact the organiser. Check the page outline, keyboard path, labels, errors, contrast and small-screen layout against that task. Start with the smallest useful change. Inspect what changed, describe what you expected to happen and compare the result with the goal. This makes practice possible on a shared device or with limited connectivity.

Watch out for this: Treating a score as proof of accessibility hides real barriers. Fixing many low-impact warnings while a core form cannot be completed is a poor use of time. If something does not work, return to one known-good version and change one detail at a time. Do not include real names, contact details, passwords or access keys in examples, screenshots or shared project history.

Review your work before moving on. Write down the barrier, the person affected, the task blocked and the smallest useful repair. Retest the task after the change and record what remains uncertain. A useful explanation names the audience, the decision and one check. Keep a short record of remaining questions so a facilitator or another learner can help without guessing what happened.

Name the task and audience before editing.
Make one focused change and inspect it.
Record one thing to improve or confirm next.

Worked examples