SELF-GUIDED BA PRACTICE Packages available · Access after confirmed paymentSee packages ↗

Requirements

Accessibility Requirements Meaning: What They Are and How to Write Them

Requirements · Published · Updated · 9 min read · By BA Mentorship Editorial (AI-written)

Part of our guide to business analyst skills.

What accessibility requirements mean

An accessibility requirement is a statement of what a system must do, or how it must behave, so that people with disabilities can use it as fully as everyone else. That includes people who are blind or have low vision, people who are deaf or hard of hearing, people with motor impairments who cannot use a mouse, and people with cognitive or learning differences. You can find a short definition in the accessibility requirement glossary entry.

Accessibility also helps people with temporary or situational limits: a broken wrist, a phone screen in bright sun, a noisy train with no headphones. When you design for the edges, the middle usually gets better too.

Most teams treat accessibility as a quality attribute, so it often sits with the non-functional requirements. In practice, many accessibility needs turn into concrete behaviour, such as 'every form field has a label a screen reader can read'. That is why the line between the two types is blurry. If you need a refresher, read Functional vs Non-Functional Requirements: Examples.

Where the rules usually come from

Many organisations base their accessibility requirements on the Web Content Accessibility Guidelines (WCAG), published by the W3C. WCAG is built on four principles: content must be perceivable, operable, understandable and robust. Each success criterion has a conformance level: A (the basic minimum), AA (the level many organisations aim for) and AAA (the strictest). Some countries and sectors also have laws or procurement rules on digital accessibility. These rules vary and change, so check with your legal or compliance team and the official sources rather than relying on a blog post.

  • Visual: text alternatives for images, enough colour contrast, content that still works when zoomed.
  • Hearing: captions for video, transcripts for audio, no information given only by sound.
  • Motor: every action possible with a keyboard alone, no tiny targets, no actions that need precise timing.
  • Cognitive: plain language, clear error messages, consistent navigation, time limits that users can extend.
  • Assistive technology: correct structure and labels so screen readers and voice control tools can work with the page.

Accessibility vs usability requirements

People often mix these up. Usability is about whether a typical user can complete a task easily. Accessibility is about whether people with disabilities can complete the task at all, often through assistive technology. A screen can be very easy for a mouse user and still be completely blocked for a keyboard user.

Accessibility vs usability requirements

AspectAccessibility requirementUsability requirement
Main questionCan people with disabilities use it at all?Can typical users complete tasks easily?
Typical sourceWCAG, company policy, contracts, local rulesUser research, design standards, product goals
ExampleAll booking steps work with a keyboard onlyA new user books an appointment without help
How it is testedKeyboard checks, screen reader checks, automated scans, expert reviewUsability testing with real users, task observation, feedback
If it is missedSome users are fully blocked, with possible legal or contract riskUsers get frustrated, make errors or give up
Both are quality requirements, but they answer different questions and are tested in different ways.

Both belong in your requirements, and they often support each other. Clear error messages, for example, help everyone. The difference matters when you write the test: an accessibility check usually refers to a specific guideline or assistive technology, while a usability check usually refers to task success with real users.

How to write accessibility requirements, step by step

  1. Agree the target standard. Ask the sponsor and the legal or compliance team which standard and level apply, for example WCAG level AA. Record it as a constraint so nobody argues about it later.
  2. Identify affected users and journeys. List the key journeys (sign up, search, pay, get help) and the user groups who might be blocked in each. Personas with disabilities help here.
  3. Elicit real needs. Talk to users who rely on assistive technology, support staff who hear complaints, and any internal accessibility specialist. Review existing audit reports if there are any.
  4. Write each requirement as a testable statement. Avoid 'the system must be accessible'. Write 'all booking steps can be completed using only a keyboard, in a logical order, with a visible focus indicator'.
  5. Link each requirement to a guideline. Add the WCAG success criterion or company policy reference so testers know exactly what to check.
  6. Turn them into acceptance criteria. Add accessibility checks to user stories and, where it makes sense, to the team's Definition of Done. Our guide to acceptance criteria and Gherkin shows the format.
  7. Plan the testing. Agree who runs keyboard, screen reader and automated checks, and include users with disabilities in UAT where you can. Trace every requirement to at least one test case.
From vague wish to testable requirement6 steps in order: 1. Agree the standard: Confirm the standard and level with the sponsor and compliance, and record it as a constraint. 2. Map journeys and users: List the key journeys and who could be blocked in each one. 3. Elicit real needs: Talk to assistive technology users, support staff and accessibility specialists. 4. Write testable statements: Describe observable behaviour, not a feeling like 'accessible'. 5. Add criteria and references: Link each requirement to a guideline and write acceptance criteria for it. 6. Test and trace: Run keyboard, screen reader and automated checks, and trace each requirement to test cases.1Agree the standardConfirm the standard and level with thesponsor and compliance, and record it asa constraint.2Map journeys and usersList the key journeys and who could beblocked in each one.3Elicit real needsTalk to assistive technology users,support staff and accessibilityspecialists.4Write testable statementsDescribe observable behaviour, not afeeling like 'accessible'.5Add criteria and referencesLink each requirement to a guideline andwrite acceptance criteria for it.6Test and traceRun keyboard, screen reader and automatedchecks, and trace each requirement totest cases.
Six steps that turn 'make it accessible' into requirements a team can build, test and sign off.
Diagram in words
  • 1. Agree the standard: Confirm the standard and level with the sponsor and compliance, and record it as a constraint.
  • 2. Map journeys and users: List the key journeys and who could be blocked in each one.
  • 3. Elicit real needs: Talk to assistive technology users, support staff and accessibility specialists.
  • 4. Write testable statements: Describe observable behaviour, not a feeling like 'accessible'.
  • 5. Add criteria and references: Link each requirement to a guideline and write acceptance criteria for it.
  • 6. Test and trace: Run keyboard, screen reader and automated checks, and trace each requirement to test cases.

For the technical vocabulary, the MDN accessibility documentation explains terms like ARIA, focus and semantic HTML in plain language. You do not need to code, but knowing these words helps you talk to developers and testers with confidence.

Worked example: a booking form at Marigold Health Clinics

Marigold Health Clinics, a fictional company, is rebuilding its online appointment booking. The flow has three steps: choose a time, confirm details, see confirmation. Helena, the project sponsor, has written one line in the brief: 'The new booking form must be accessible.' Nadia, the business analyst, knows that line cannot be built or tested as it stands.

Turning 'accessible' into something testable

Marigold Health Clinics, a fictional company, during a backlog refinement session for the new online appointment booking form.

  1. Helena Project sponsor

    The brief says the booking form must be accessible. Isn't that enough? Everyone knows what accessible means.

  2. Nadia Business analyst

    It's the right goal, but the developers can't build it and Riya can't test it as written. Which standard are we aiming for? Has compliance given us a level?

  3. Helena Project sponsor

    Compliance said WCAG level AA for all patient-facing pages.

  4. Riya QA tester

    That helps. But I still need to know which checks to run. Keyboard only? Screen reader? Contrast? Time limits?

  5. Nadia Business analyst

    Let's walk through the three booking steps and ask who could get stuck at each one. Then we write one testable requirement per need and link it to the AA criterion.

  6. Riya QA tester

    Good. I'll turn each one into a scenario so we test it the same way every sprint.

The people and the company in this scene are fictional.

Nadia asks for the target standard first, then works journey by journey.

After the session, Nadia replaced the single vague line with five requirements, each linked to a source:

  1. AR-01: All three booking steps can be completed using only a keyboard, with focus moving in reading order and a visible focus outline. (WCAG keyboard and focus criteria)
  2. AR-02: Every form field and error message has a text label that a screen reader announces. (WCAG labels and error identification)
  3. AR-03: Body text has a contrast ratio of at least 4.5:1 against its background. (WCAG contrast, level AA)
  4. AR-04: The session expires after 15 minutes of no activity. At least 2 minutes before expiry, the patient sees a warning with an 'Extend' button that restarts the 15-minute timer. (WCAG timing adjustable)
  5. AR-05: The 'How to prepare for your visit' video has captions and a text transcript. (WCAG captions)

Riya, the QA tester, then turned AR-01 into a Gherkin scenario so the team could test it the same way every time.

AR-01 as a Gherkin scenario

AR-01: keyboard-only booking

Feature: Book an appointment without a mouse

Scenario: Patient completes booking using only the keyboard1

Given the patient is on the 'Choose a time' step

And the patient uses no mouse or touch input

When the patient presses Tab2

Then focus moves to the next control in reading order

And the focused control shows a visible focus outline3

When the patient selects a time slot and presses Enter

Then the 'Confirm details' step opens

And the screen reader announces 'Step 2 of 3: Confirm details'4

  1. One need per scenario. The scenario tests one need, keyboard access, so a failure points to one clear cause.
  2. Observable action. Tab is a real key the tester presses. Focus order should follow the visual reading order of the page.
  3. Visible focus. Keyboard users need to see where they are. Without an outline, the page may work but users cannot tell which control is active.
  4. Screen reader check. This line links AR-01 to AR-02: the step change is announced, so blind users know the page has moved on.
One requirement, one scenario, with each line something a tester can actually do or see.

Riya also wrote a test for AR-04: leave the form untouched for 13 minutes, check that the warning appears, press Extend, and confirm the timer restarts at 15 minutes. Each of the five requirements ended up with at least one test case in the traceability matrix, so Helena could see exactly what 'accessible' meant at sign-off.

Common mistakes with accessibility requirements

  • Writing 'the system must be accessible' and stopping there. Nobody can build or test a feeling.
  • Leaving accessibility until UAT. Fixing a missing label late is cheap. Rebuilding a custom date picker that keyboard users cannot reach is not. Raise accessibility at refinement.
  • Relying only on automated scanners. Tools catch some issues, like missing alt text or low contrast, but they cannot tell whether focus order makes sense or an error message is clear. Manual checks are still needed.
  • Treating it as a developer-only topic. Content, design, PDFs and emails also need to be accessible. The BA can make sure these are in scope.
  • Forgetting other channels. Downloadable forms, text message reminders and call centre scripts are part of the journey too.
  • Promising legal compliance. A BA can document the target standard, but whether a product meets the law is a question for legal or compliance specialists.

Accessibility requirement habits

Good habit

  • Agree the standard and level with compliance before writing requirements.
  • Write each requirement as observable behaviour with a clear test.
  • Add accessibility checks to acceptance criteria and the Definition of Done.
  • Include people who use assistive technology in research and UAT where possible.

Risky habit

  • Write 'must be accessible' and assume everyone will interpret it the same way.
  • Leave all accessibility testing to the last week before go-live.
  • Treat an automated scan as proof that the product is accessible.
  • Assume only web pages matter and forget PDFs, emails and videos.
Small habits at the requirements stage save a lot of rework before go-live.

Quick checklist before you call a requirement done

Use this list when you review your accessibility requirements with the team, or before you hand them over for testing.

  • The target standard and level are written down and agreed.
  • Each requirement describes behaviour a tester can observe.
  • Each requirement links to a guideline or policy reference.
  • Keyboard, screen reader and contrast needs are covered for every key journey.
  • Time limits, error messages and media such as video and audio are covered.
  • Acceptance criteria exist, and at least one test case traces to each requirement.
  • Owners for manual and automated accessibility testing are named.

Writing clear, testable quality requirements is one of the core skills covered in Business Analyst Skills: 12 Core Skills & How to Build Them. To see how requirements like these become step-by-step tests, read Writing Test Cases From Acceptance Criteria.

Silent clip, about 19 seconds. BA Lab screen recording: a Jira-style story and a Confluence-style requirements page. All data in it is fictional.

Frequently asked questions

Are accessibility requirements functional or non-functional?

Most teams list them as non-functional, because they describe a quality of the whole product. Many of them still describe concrete behaviour, like keyboard navigation or field labels, so you will often see them written as functional requirements or acceptance criteria too. What matters is that they are clear, testable and not forgotten.

Who is responsible for accessibility on a project?

Everyone shares it. The BA makes sure needs are captured and testable, designers handle contrast and layout, developers build correct structure, testers check it, and content writers keep language clear. The sponsor owns the decision on the target standard, usually with advice from legal or compliance.

Do I need to memorise WCAG as a business analyst?

No. You need to know that it exists, understand the four principles and the A, AA and AAA levels, and know how to look up a success criterion when you write a requirement. Your accessibility specialist or QA team can help with the technical detail.

How do you test accessibility requirements in UAT?

Combine automated scans with manual checks: complete key journeys using only a keyboard, try them with a screen reader, zoom the page, and check captions and error messages. Where possible, invite users who rely on assistive technology to take part, and trace every requirement to a test case.

Is digital accessibility a legal requirement?

In many places there are laws or public sector rules about digital accessibility, but they differ by country, sector and type of organisation, and they change over time. This article is not legal advice. Ask your legal or compliance team and check the official government sources that apply to you.

This article was written by an AI system and published automatically after automated accuracy, safety and quality checks. All companies, people and numbers in the examples are fictional. BA Mentorship does not issue professional certifications and cannot guarantee any job or interview outcome. Spot an error? Email our support team and we will check and correct it.

Key terms in this article

Browse the full glossary

CHECK BEFORE CONTINUING

Keep your work safe