This hands-on course helps you build confidence in identifying accessibility needs, breaking down requirements, and writing clear acceptance criteria at both the component and flow level. You’ll explore real-world examples, collaborate with peers, and complete a series of guided activities that make accessibility part of everyday delivery – not an afterthought.

What you’ll learn

  • Understand the difference between accessibility requirements and acceptance criteria
  • Recognise how people with different disabilities interact with digital products
  • Write effective accessibility acceptance criteria for common UI components
  • Identify accessibility risks at the page or user flow level
  • Use the seven user groups method to ensure no one is left out
  • Write clear, testable “pass/fail” accessibility checks
  • Turn test statements into positive, observable acceptance criteria
  • Collaborate across roles to embed accessibility into day-to-day delivery

Who this course is for

  • Product owners and business analysts
  • UX and UI designers
  • Content designers and technical writers
  • Developers and testers
  • Anyone responsible for writing or reviewing user stories
  • Teams looking to make accessibility part of their everyday process

Knowledge level

No prior accessibility knowledge is required.

Technology requirements

We use online tools such as FigJam to work together during this course. You won’t need to install or create an account to use these tools.

Delivery options

Instructor-led training for organisations

  • Duration: 3 x 2-hour sessions, over 3 weeks
  • Cost: $6,000 AUD (+ GST)
  • Attendees: Up to 20

Contact us to book training

Course outline

Session 1

  • Accessibility requirements
  • Digital Accessibility Policies
  • Measuring accessibility
  • Accessibility acceptance criteria

Session 2

  • How do you create accessibility acceptance criteria?
  • Why so many steps?
  • Why write the tests before our acceptance criteria?
  • Step 1. Choose a page or user flow you want to review
  • Step 2. Pick one user group to focus on
  • Step 3. Consider how this group might interact with the page or flow
  • Step 4. List potential barriers they may encounter
  • Activity: Identifying accessibility barriers
  • Step 5. Turn each barrier into a test question
  • Step 6. Reframe each test as a positive statement
  • Step 7. Repeat for each user group
  • Activity: Creating page and user-flow acceptance criteria
  • Your acceptance criteria reference library

Session 3

  • Why should you care about component level accessibility criteria?
  • Same steps as last time?
  • Step 1. Choose a component you want to review
  • Step 2. Pick one user group to focus on
  • Step 3. Consider how this group might interact with the component
  • Step 4. List potential barriers they may encounter
  • Step 5. Turn each barrier into a test question
  • Step 6 and 7
  • Activity: Writing come acceptance criteria
  • Answers for a button
  • Answers for a text input component
  • Answers for a select component
  • Answers for a modal component
  • Wrapping up