UX and research · Beginner · 14 min
Add accessibility requirements to a design brief
By Padding · Updated 18 Nov 2026
Any document editor · WCAG 2.2 · November 2026
You will add an accessibility section to a design brief that names who could be shut out, sets a WCAG 2.2 target and lists testable requirements with how and when each one is checked.
On this page
Accessibility usually enters a project at the end. Someone runs an audit a week before launch, finds that the date picker cannot be used without a mouse and the error messages are red text only, and the team patches what it can. The patches are expensive because the design decisions behind them were made months earlier, by people who were never told they mattered.
The fix is to write accessibility into the brief, next to the problem and the outcome, before anyone sketches a screen. Then it is an input that shapes the design, not a test the design fails. In this tutorial you add an accessibility section to an existing brief: who might be excluded, which standard you will meet, and a list of requirements written so that someone can check each one and say yes or no.
The running example is the Larkfield Clinic brief from Turn a feature request into a user-centred design brief. Larkfield, a fictional community clinic, plans an appointment booking app with six screens: Home, Choose a service, Pick a time, Your details, Confirm and Booked, followed by a reminder before the appointment. If you have your own brief, use it instead; every step works the same way.
Step 1 · Make room in the brief and name an owner
Open your brief. Below Constraints (or wherever your brief lists the fixed things the design must work within), add a heading called Accessibility. Give it four empty sub-headings, which the next steps fill in:
- Who could be shut out
- Standard we will meet
- Requirements
- How we will check
Under the main heading, write one line naming the person responsible for this section and the date it will be reviewed with the team. For Larkfield: "Owner: lead designer. Reviewed at the kick-off on 25 November."
An owner matters because accessibility requirements cut across roles. A designer chooses colours, a developer builds the date picker, a content writer words the error messages, and the clinic decides whether the phone line stays open. Without one person keeping the list, each role assumes another has it.
If your brief already mentions accessibility as a single constraint ("must be accessible"), delete that line and point to the new section instead. A one-line constraint cannot be checked, so it tends to be ignored.
Check it worked
Your brief has an Accessibility heading with the four sub-headings, placed before any section about designs or screens. There is one line naming an owner and a review date. No other part of the brief says "must be accessible" without pointing to this section.
Step 2 · Walk the task and note who could be shut out
Requirements start from people, not from a standard. Under Who could be shut out, make a table. The rows are the steps of the main task, in order. The columns are five kinds of difference that change how someone uses a screen:
- Seeing: blind people using a screen reader, people with low vision who zoom to 200% or more, people with colour vision deficiency.
- Moving: people who use a keyboard, switch or voice control instead of a mouse or touch, people with tremors who struggle with small targets.
- Hearing: Deaf and hard of hearing people, who miss anything only said aloud or signalled by sound.
- Thinking and remembering: people with dyslexia, a learning disability, anxiety or memory difficulties, and anyone unwell or stressed.
- Situation: anyone in a temporary or passing state, such as one hand holding a child, a cracked screen, bright sunlight or a slow connection.
Go through each row and ask, column by column: what on this step could stop someone with this difference from finishing? Write a short phrase in the cell. Leave a cell empty if nothing comes to mind, but do not skip the question.
For Larkfield, a few cells:
- Pick a time / Seeing: available and full slots shown only by colour; a calendar grid that a screen reader reads as a list of numbers with no dates.
- Pick a time / Moving: slots chosen by dragging along a timeline; tiny time buttons packed together.
- Pick a time / Thinking: the slot is held for a few minutes with a countdown, which adds pressure.
- Your details / Thinking: asked for a patient number they do not have to hand; asked to type a code from a text message within 60 seconds.
- Booked / Hearing: confirmation given only by a short sound.
- Reminder / Situation: a reminder text with a link that only works on a desktop browser.
Clinics serve people who are older, ill, in pain or worried, so expect the Thinking and remembering and Situation columns to fill up. Those are the columns teams most often leave empty.
This table is a set of informed guesses, like the guessed rows elsewhere in your brief. Mark it "to be checked with disabled participants" and see Include disabled people in your user research for how to do that.
Check it worked
Your Who could be shut out table has a row for every step of the task, including anything after the last screen such as a reminder or a confirmation email, and all five columns. At least one cell in each column is filled in. Every filled cell names something specific on that step, not a general phrase such as "may be hard to use".
Step 3 · Set the standard and what it covers
Under Standard we will meet, write one sentence that names the standard, the level and the scope. For most projects that sentence is:
The booking app, including the reminder messages and any page linked from them, will meet WCAG 2.2 at level AA.
WCAG (the Web Content Accessibility Guidelines) is published by the W3C. Version 2.2 became a W3C Recommendation in October 2023. Its success criteria come in three levels:
- A: the minimum. Failing these blocks some people completely.
- AA: A plus a further set. This is the level most organisations, public bodies and contracts ask for.
- AAA: the strictest. The W3C itself does not recommend requiring AAA for whole sites, because some criteria cannot be met by all content.
Meeting AA means meeting every A and AA criterion that applies. Pick AA unless you have a reason not to, and if your organisation has a policy, a contract clause or a law that names a level or version, quote it here with its source. If the rule you are under names WCAG 2.1, meeting 2.2 AA also covers 2.1 AA, since 2.2 only adds criteria (and removes one obsolete one).
Then write the scope as plainly as the target. List what is in: every screen, the reminder text and email, the confirmation page and any PDF. List anything out, with a reason and a date when it comes in. "Out: the clinic's existing patient portal, which this project links to but does not change. Raised with the practice manager." Scope gaps are where accessibility quietly fails, because a fully accessible booking flow that ends in an inaccessible portal still shuts people out.
Check it worked
Your Standard we will meet section has one sentence naming WCAG 2.2, a level and what it covers. If an outside policy or law sets the level, it is quoted with a source. There is an in-scope list that includes everything after the last screen, and every out-of-scope item has a reason.
Step 4 · Turn each barrier into a testable requirement
A standard is too broad to design from. The Requirements section is where you turn the barriers in your table into statements a designer can design to and a tester can check. Make a second table with five columns: ID, Requirement, Screen, Source, Barrier it removes.
Write each requirement so that someone could look at a design or a working screen and answer yes or no. Three rules help:
- Name the thing, not the quality. "Available slots are shown by text and colour, not colour alone" can be checked. "Slots are clear" cannot.
- Put a number in it when the standard gives one. Contrast ratios, target sizes and zoom levels all have numbers.
- Cite the WCAG success criterion by number in Source when there is one, so anyone can read the full wording.
Larkfield rows (each is one row of the table):
- A-01. Available, full and selected slots differ by text or shape as well as colour. Pick a time. WCAG 1.4.1 Use of Color (A). Colour vision deficiency.
- A-02. Body text has a contrast ratio of at least 4.5:1 against its background, and large text at least 3:1. All screens. WCAG 1.4.3 (AA). Low vision, bright sunlight.
- A-03. Buttons, slot boundaries and form field borders have at least 3:1 contrast with what is around them. All screens. WCAG 1.4.11 (AA). Low vision.
- A-04. Every slot and button can be reached and chosen with a keyboard alone, and the focused item is always visible and not hidden behind a sticky header. All screens. WCAG 2.1.1 (A), 2.4.7 (AA), 2.4.11 (AA). Keyboard and switch users.
- A-05. Choosing a slot never needs dragging; a single tap or click is enough. Pick a time. WCAG 2.5.7 (AA). Tremor, one-handed use.
- A-06. Every tap target is at least 24 by 24 CSS pixels, or spaced so that a 24 pixel circle on each does not overlap another. All screens. WCAG 2.5.8 (AA). Tremor, cracked screen.
- A-07. At 320 CSS pixels wide, and with text zoomed to 200%, every screen works without scrolling sideways and no text is cut off. All screens. WCAG 1.4.10 (AA), 1.4.4 (AA). Low vision, small phones.
- A-08. If a slot is held for a limited time, the person is warned before it runs out and can extend it with one action. Pick a time. WCAG 2.2.1 (A). Anxiety, slower readers, screen reader users.
- A-09. Every field has a visible label; errors are shown in text next to the field, say what is wrong and how to fix it. Your details. WCAG 3.3.1 (A), 3.3.2 (A), 3.3.3 (AA). Cognitive, screen reader users.
- A-10. Name, email and phone fields are marked so the browser can fill them in. Your details. WCAG 1.3.5 (AA). Memory, motor.
- A-11. Signing in or verifying a phone number does not depend on remembering or retyping a code; pasting and password managers work. Your details. WCAG 3.3.8 (AA). Memory, dyslexia.
- A-12. Details already entered are never asked for again in the same booking. Your details, Confirm. WCAG 3.3.7 (A). Memory, fatigue.
- A-13. "Booked" is announced to screen readers when the page updates, and is never given by sound alone. Booked. WCAG 4.1.3 (AA). Blind and Deaf patients.
- A-14. The clinic's phone number and help link sit in the same place on every screen. All screens. WCAG 3.2.6 (A). Anyone who gets stuck.
You will not reach every criterion in WCAG this way, and that is fine at brief stage. The table holds the requirements that shape design decisions on your screens. The full criteria list is still the target from the previous step, and the checks in the last steps catch the rest.
Check it worked
Every filled cell in your Who could be shut out table is covered by at least one requirement, or has a note saying why it is not. Each requirement can be answered yes or no by looking at a design or a working screen. Every row that comes from WCAG names the success criterion by number and level.
Step 5 · Add the requirements WCAG does not cover
WCAG covers web content. It does not decide whether your service is usable by someone who will never open the app, how plain your wording is beyond a few criteria, or what happens when a booking goes wrong. Your barrier table will have cells that no success criterion answers. Add them as requirements with Source set to the project, so it is clear they are a team decision, not a legal minimum.
Larkfield rows:
- L-01. Patients can still book every appointment type by phone, at the same times and with the same choice of slots as online. Whole service. Larkfield requirement. People who cannot or will not use the app.
- L-02. Screen text is written for a reading age of around nine to eleven, tested with a readability check and with patients. All screens. Larkfield requirement. Learning disability, stress, English as a second language.
- L-03. Patients choose how they get reminders (text, email, phone call or letter) and can change it later. Reminder. Larkfield requirement. Deaf patients, people without smartphones.
- L-04. Before confirming, patients see every detail of the booking on one screen and can change any of it. Confirm. Larkfield requirement, going beyond WCAG 3.3.4, which only requires this for legal, financial or data-changing submissions. Anyone who makes a mistake.
- L-05. The reminder link opens the booking on any phone browser without signing in again. Reminder. Larkfield requirement. Situational, memory.
Keep this list short and specific. Its job is to stop the team believing that passing an AA audit means the service works for everyone.
Check it worked
Your Requirements table has at least two rows whose Source is your project rather than a WCAG criterion, each with a barrier from your table in the last column. There is a requirement about the route for people who will not use the digital product at all, or a written note saying why one is not needed.
Step 6 · Say how and when each requirement is checked
A requirement no one checks is a wish. Under How we will check, add three columns to the requirements table, or make a matching table keyed by ID: Check, Stage, Who.
Use four kinds of check, and pick the earliest stage where each one can catch a problem:
- Design review, on wireframes and mockups: colour contrast with a contrast checker, target sizes measured in the design file, labels and error text present in the designs, the phone route shown on every screen.
- Build check, on working code: keyboard-only run through the whole task, zoom to 200% and a 320 pixel wide window, an automated checker for the issues machines can find.
- Assistive technology check, on working code: the full task with a screen reader on desktop and on a phone, and with voice control if your patients use it.
- Research, on prototypes and live code: usability sessions where disabled patients book a real appointment type. This is the only check that tells you whether the barrier table was right.
Larkfield examples:
- A-02: contrast checker on every text colour pair in the mockups. Design review. Designer.
- A-04: complete a booking using only the keyboard, noting any point where focus disappears. Build check and again before launch. Developer, then tester.
- A-08: let the hold timer run down with a screen reader on; confirm the warning is read out and extending works. Assistive technology check. Tester.
- L-02: readability score on all screen text, then three patients read the Your details screen aloud and explain it back. Design review, then research. Content writer, researcher.
Finally, add one line to your project's definition of done: "A screen is not done until every requirement tagged to it has passed its check at the current stage." This is what turns the section from advice into part of how work is accepted.
Check it worked
Every requirement has a check, a stage and a named role. At least half of the requirements can be checked at design review, before any code is written. At least one check involves disabled people using the product, and your definition of done refers to this table.
Step 7 · Review the section with the team and record changes
Book thirty minutes with the people who will design, build, write and approve the work. Share the brief before the meeting and ask each person to read only the Accessibility section and mark any requirement they think they cannot meet, or do not understand.
In the meeting, go through the marked requirements one at a time. For each, record one of three outcomes next to it:
- Agreed: the requirement stands as written.
- Changed: reworded, with the new wording and the reason.
- Deferred: moved out of this release, with the date it comes back and who agreed. Deferring an A or AA criterion means you no longer meet your stated target, so update the Standard we will meet sentence to say so, rather than leaving a target the plan cannot reach.
Watch for two common moves. The first is replacing a requirement with "we will use an accessible component library". Libraries help, but the date picker on Pick a time still has to pass A-04 to A-06 in your app, so keep the requirement and note the library as how you plan to meet it. The second is moving all checks to a final audit. Keep the stages from the previous step; an audit at the end is a backstop, not the plan.
Date the section, and add the review to the brief's change log if it has one.
Check it worked
Every requirement that was marked before the meeting now shows agreed, changed or deferred. Every deferred item has a return date and a name. If anything at level A or AA was deferred, the Standard we will meet sentence says so. The section has a review date and the names of the people who reviewed it.
Next steps
Your brief now treats accessibility as something the design starts from. The barrier table is still a set of guesses, and the requirements will meet their first real test when designs exist.
- Include disabled people in your user research to check the barrier table with the people it describes.
- Run a heuristic evaluation to review early designs against the brief before user testing.
- Plan a usability test to build the research checks into a test plan.
- Build accessible forms in HTML to see how requirements like A-09 and A-10 look in code.
Part of these paths
Related tutorials
- Turn a feature request into a user-centred design briefYou will turn a one-line request into a one-page brief that names the people affected, what they are trying to get done, what is known and what is guessed, ready to hand to a team.
- Include disabled people in your user researchYou will have a research plan and a per-participant session setup that let disabled people take part on their own terms, from recruitment and consent to session length, assistive technology and payment.
Need this done for you?
Padding does this work for growing companies, from the first diagnosis to a system that keeps working.
Get new tutorials