A11y user stories csun 2018
Download as PPTX, PDF7 likes1,995 views
This document discusses how to incorporate accessibility into an agile development process using user stories. It defines what agile is and how it works iteratively using user stories to define requirements from the user's perspective. The document provides examples of user stories written from the perspective of people with different disabilities or impairments. It also discusses how to fully define user stories to specify requirements and ensure the user's needs are met based on their abilities. The goal is to help development teams understand diversity and disability to build more inclusive digital products and services.
![Agile workflow
Agile often involves a series of iterations or sprints
Work for each sprint is defined in a ‘user story’ expressed
from the perspective of an end-user goal:
as a [role / person]
I want / need [some requirement or feature]
so that [goal / value / reason]](https://image.slidesharecdn.com/a11yuserstoriescsun2018-180322153516/85/A11y-user-stories-csun-2018-9-320.jpg)
A11y user stories csun 2018
- 1. User stories for accessibility Accessibility in an agile world? creating an inclusive digital world intopia.digital @intopiadigital Andrew Arch @amja Sarah Pulis @sarahtp
- 3. Agile is … A development methodology that is • Iterative • Incremental • Evolutionary Rather than specification driven with a long development phase that thinks about the user at the end
- 4. Agile is … The Manifesto for Agile Software Development values • Individuals and Interactions over processes and tools • Working Software over comprehensive documentation • Customer Collaboration over contract negotiation • Responding to Change over following a plan Leading to opportunities to incorporate, and adjust to, user needs as they are discovered
- 5. Image courtesy of @DTA
- 6. Agile is … … a collection of values, principles, behaviours, and practices enabling teams to build services iteratively, delivering early and often. Agile is a state of mind rather than a process to be followed Courtesy @RodBMolina
- 7. How does Agile work?
- 8. Agile operating model Image courtesy of @DTA and @RodMolina
- 9. Agile workflow Agile often involves a series of iterations or sprints Work for each sprint is defined in a ‘user story’ expressed from the perspective of an end-user goal: as a [role / person] I want / need [some requirement or feature] so that [goal / value / reason]
- 10. Benefits of user stories • Define problems faced by people with varying ability • Articulate user’s needs clearly • Less prescriptive than requirements documentation • Result in shared understanding of the outcome for the user • Promote discussion and collaboration When applied to accessibility for people with disability, they can help demystify WCAG
- 11. WCAG 2.0 framework WCAG 2.0 Perceivable Text Alternatives Time-based Media Adaptable Distinguishable Operable Keyboard Accessible Enough Time Seizures Navigable Understandable Readable Predictable Input Assistance Robust Compatible Principles Guidelines Success Criteria A: AA: AAA:
- 13. Completing a user story Teams have a checklist of criteria which must be met before a user story can be considered “done” Definition of Done For role based stories can include • Feature is tested for accessibility For person/persona based stories • Features works for the user with their technology or limitations
- 14. User stories for accessibility
- 15. Components of a user story •The user •A real person from user research or usability testing •A persona that has a disability or impairment •The outcome when interacting with the system •The goal or value that is delivered
- 16. Common Persona Attributes • Name: naming your persona makes them more real. • Motivations: why would the user use your product? • Goals: what do they want to achieve, and how can your product help? • Frustrations: what problems does your user have with certain tasks? • This is where disability or impairment can be described along with assistive technology or adaptive strategies used • Demographics: age, gender, location, occupation. • Picture: giving the user a face makes them more real and relatable. • Quote: what memorable quote sums up your user and the problem you want to solve for them?
- 17. Attributes for Diverse Personas Alternatively, add additional diversity related attributes • Ability: the level of ability the user has – do they have any impairments? • Aptitude: how experienced is the user with the web? Do their abilities create any specific difficulties when using a computer? • Attitude: what are their attitude towards life, or towards the web? • Access points: does this user need assistive technologies or rely on adaptive strategies to access the web?
- 19. Sample user stories As a sighted non-mouse user I need better keyboard focus so I can see where I am in a page as I tab through it As a sighted user with poor concentration I need visible labels on all form fields so I can understand what information is requested As a sighted user with cognitive issues I need all instructions to appear on screen and specify the exact requirements so I can understand all information needed
- 20. Sample user stories As a screen reader user I need alt-text on informative images so I can understand all the important information on a page As a screen reader user I need all link text to be meaningful so that I can navigate more easily As a low vision user or colour deficient user I need more obvious link indicators so I can see where to click on a page
- 21. Sample user stories As a hearing-impaired person, I need captions on the videos in order to fully understand the eLearning modules As a low vision user, I need to increase the font size in order to read the screens As a front-line user under pressure to meet KPIs I need clear link text in order to know intuitively where to go next
- 22. Helping specify the requirement To help the developers implement the user stories correctly • Add an explanation of the issue on the page • Add a possible solution to resolve the issue • Prioritise the issue • Reference the WCAG Success Criteria (if applicable) • Point to the Quickref (not the TR)
- 24. Create an understanding of disability Have a team presentation / discussion about diversity • Talk about ageing, culture, disability and the overlaps • Watch the W3C Perspectives videos Make diversity and disability real by • Relating to grandparents • Discussing personas • Including team in usability sessions
- 25. Point out that accessibility IS usability for some ‘Accessibility is just the beginning. It is usability that makes the difference.’ Patti Moore UX Australia keynote 2016 ‘Wasting time is the worst customer experience’ Gerry McGovern, 27/3/17 http://gerrymcgovern.com/wasting- time-is-the-worst-customer- experience/
- 27. Definition of done For role based stories can include • Feature is tested for accessibility For person/persona based stories • Features works for the user with their technology or limitations More specifically • All tasks finished (with the ability of the user in the story) • All tests passed (including using the feature with the user’s ability • Code checked in to version control
- 28. Would this pass?
- 29. Let’s continue the conversation Andrew Arch & Sarah Pulis andrew@intopia.digital sarah@intopia.digital http://intopia.digital/ @amja @sarahtp creating an inclusive digital world intopia.digital
Editor's Notes
- #6: Change of approach – brings the user to the front, and throughout, the process
- #7: My colleague, Rod Molina who’s an Agile Coach sums it up as Agile …
- #8: What is this iterative thing?
- #10: This is similar to the “actions” we we’re talking about yesterday with the presentation cognitive walkthroughs
- #11: Less prescriptive than requirements documentation
- #12: WCAG 2.0 success criteria are written as testable statements that are not technology-specific. 4 principle; 12 guidelines; 61 criteria Can be overwhelming
- #13: User stories make accessibility real – no longer the elephant in the room
- #19: Sarah Horton and Whitney Quesenbury describe 8 personas Barclays Bank describe 7 personas
- #23: WCAG not always applicable, eg important things on the RHS for screen magnifier users (or mobile phone) minimise number of tabs to get to important information/actions on a page
- #26: Patti Moore – can a person use the product effectively Gerry McGovern – can a person use the product effectively
- #28: Second set from Karl Groves
- #29: Can also apply users stories to design sprints – might have prevented this getting into development if the design had specified the tab order