Accessibility Acceptance Criteria by Melanie O'Brien - Ensuring Inclusive Design

Accessibility Acceptance Criteria by Melanie O'Brien - Ensuring Inclusive Design
Slide Note
Embed
Share

Delve into Melanie O'Brien's Accessibility Acceptance Criteria (AAC) methodology, a set of 10 criteria embedded in user stories to enhance accessibility compliance and usability. Learn how to write inclusive Agile acceptance criteria and understand the importance of accommodating individuals with disabilities and specific accessibility needs. Explore practical applications and key success criteria distilled for effective implementation.

  • Accessibility
  • Inclusive Design
  • AAC
  • User Stories
  • Agile

Uploaded on Mar 10, 2025 | 1 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. Accessibility Acceptance Criteria (AAC) Melanie O'Brien Digital Accessibility Manager PG1 | 10/03/2025

  2. Contents 1. Background & context 2. List of 10 AACs 3. How we implement them PG2 | 10/03/2025

  3. Why we created the AACs

  4. PG4 | 10/03/2025

  5. What are Accessibility Acceptance Criteria (AAC)

  6. What are the AACs A set of 10 accessibility criteria included in user stories to improve accessibility compliance & usability. What they're not Define the A11y boundaries of a user story WCAG success criteria Accessibility requirements Confirm when a story is closed Define testable conditions for A11y PG6 | 10/03/2025

  7. Accessibility Acceptance Criteria o Write A11y ACs for the Agile team (BA, developer and tester). o Explain to the team why they are needed for a person with a disability and people with accessibility needs. PG7 | 10/03/2025

  8. PG8 | 10/03/2025

  9. Key WCAG, A & AA success criteria distilled into 10 A11y ACs PG9 | 10/03/2025

  10. A11y Acceptance Criteria List

  11. Accessibility Acceptance Criteria 1. Keyboard Accessibility 2. Content on hover 3. Page title 4. Visible focus 5. Semantic markup used appropriately 6. Form control labelling and inline errors 7. Screen reader 8. Zoom & resize 9. Alt text 10. Orientation & reflow PG11 | 10/03/2025

  12. AACs - Deep Dive

  13. AAC #1 keyboard accessibility. Given I m a keyboard user when I encounter interactive content I can control it solely from the keyboard. Maps directly to success criteria 2.1.1 keyboard and 2.1.2 keyboard trap. PG13 | 10/03/2025

  14. AAC #5 Semantic mark up used appropriately Given I navigate with assistive technology when I encounter content which looks different then I can perceive this difference. E.g. heading structure, ordered and unordered lists. Maps to WCAG SC 1.3.1 Info & relationships PG14 | 10/03/2025

  15. AAC #7 Screen reader Given I use a screen reader when a visual change occurs on the page then I can understand the change audibly. E.g. search results displaying while searching, errors displaying after activating submit button. Maps directly to success criterion 4.1.2 Name, role, value. PG15 | 10/03/2025

  16. AAC #6 Form control labelling and inline errors Given I use a screen reader when I focus on form controls then I can understand what type of data is required. Maps to WCAG SC 1.3.1 Info & relationships, 3.3.1 Error identification and 4.2.1 Name, role, value. PG16 | 10/03/2025

  17. User story example

  18. User story PG18 | 10/03/2025

  19. New functionality PG19 | 10/03/2025

  20. AAC5 AAC2 AAC4 AAC1 AAC7 AAC4 AAC5 AAC4 PG20 | 10/03/2025

  21. Who uses the AACs in product delivery agile squads

  22. Who uses the AAC o Accessibility Analysts: to communicate key A11y info to the squad about the component. o BAs: to flesh out the user stories to incorporate A11y at the requirement phase in the delivery cycle. o Developers: as a guidepost and instructions about how to build accessible products. o Testers: to refer to when performing QA testing. PG22 | 10/03/2025

  23. Support

  24. Supporting resources A11y SME support Companion doc Training Teach the Agile teams about the AACs and how to use them. Companion document; testing with the AACs ("How to guide") Provide guidance from A11y analyst PG24 | 10/03/2025

  25. Summary

  26. Summary The AACs are a collection of 10 Acceptance Criteria specifically for accessibility to make it easier for A11y to be included early on. They can be incorporated into user stories to improve usability and compliance to WCAG 2.1 A & AA. They define the boundaries of a user story, confirm when a story is working as intended and define testable conditions for A11y. PG26 | 10/03/2025

  27. Thank you PG27 | 10/03/2025

More Related Content