Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

A11yCamp2015_Agile Accessibility

91 views

Published on

  • Be the first to comment

  • Be the first to like this

A11yCamp2015_Agile Accessibility

  1. 1. AGILE ACCESSIBILITY NinjaTactics for Definition of Done Dominance! Lisa Herrod A11y Bytes Conference 2015
  2. 2. Accessibility is Agile!  It’s flexible  Loves role-play  Happy being shared  Lives for design artifacts  User Research is it’s playground Lisa Herrod 2015 @InclusiveUX
  3. 3. Our Star of the Day…! 3.3.1 (A) (W00t! GO NUTS!) ERROR IDENTIFICATION Lisa Herrod 2015 @InclusiveUX
  4. 4. Accompanied by… Client: Pet Lovers International Product Owner: Pam Scrum Master: Boss Scrummer Lisa Herrod 2015 @InclusiveUX
  5. 5. (Oh yes… I can draw!) …and most importantly Lisa Herrod 2015 @InclusiveUX
  6. 6. Content Author Developer Visual Designer UX/CX Researchers, Designers Testers Accessibility Specialists AKA Lisa Herrod 2015 @InclusiveUX
  7. 7. Shot on Location at…  The office of Bright Ideas  Product Backlog  Sprint Backlog  Sprint  Design Artifact Central Lisa Herrod 2015 @InclusiveUX
  8. 8. For the top events of 2015  Definition of Ready AND  Definition of Done Lisa Herrod 2015 @InclusiveUX
  9. 9. Lisa Herrod 2015 @InclusiveUX
  10. 10. http://www.scruminc.com/scrumlab-open/
  11. 11. Input from end-users, customer, team & other stakeholders
  12. 12. 3.3.1 Error Identification (A) If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. Which team roles might have input here? Lisa Herrod 2015 @InclusiveUX
  13. 13. Depending on the team…  User Experience  Content Author  Developer  Interaction Design  Visual Design  Others? Lisa Herrod 2015 @InclusiveUX
  14. 14. Product Backlog or Features PO &Team collaborate Features/ User Stories A11y is introduced Company accessibility policy Accessibility specialists UX, Dev,Testers Grouping stories important Definition of READY… Lisa Herrod 2015 @InclusiveUX
  15. 15. 1/3 on average 1/3 of items in backlog are of no value to the end user Lisa Herrod 2015 @InclusiveUX
  16. 16. 65% of features in the average product are never really used by the end user Jeff Sutherland, CEO Scrum Inc Lisa Herrod 2015 @InclusiveUX
  17. 17. Definition of Ready  Stories must be of use to the End User  Actionable  Does the team have A11y skills  Estimated Accurately  WhichWCAG Success Criteria were identified  Gain a11y time by culling the 1/3 in backlog  Prioritised to business value  What is the companies Accessibility Policy? Lisa Herrod 2015 @InclusiveUX
  18. 18. Sprint Backlog or Stories User Stories are refined More A11y is introduced via Acceptance Criteria! Company accessibility policy Accessibility specialists UX, Dev,Testers Grouping stories important Lisa Herrod 2015 @InclusiveUX
  19. 19. User Stories Product User StoryTitle User Story ID 44 Acceptance Criteria ACCESSIBILITY Pet insurance Online quote AS A dog owner I WANTTO obtain an insurance quote online SOTHAT I can find out the cost of insuring my dog each year. 3.3.1 Error Identification (A) If utilized, form validation errors are presented in an efficient, intuitive, and accessible manner. (UX, C, Dev, IxD,V)
  20. 20. UX: “We’ll need to consider form design (Interaction) grouping like form elements (Content, UX) and ensuring it’s an accessible form” Dev: “We’ll need to associate labels and input fields too, perhaps legends..?”
  21. 21. 3.3.1 Error Identification (A) Which artifacts might we have A11y input on? Potential touch points: Scenarios, user journey, wireframes? Prototypes?Complete functional modules?
  22. 22. During a Sprint
  23. 23. DoD is a Social Contract within the team It can exist between roles & can occur at various levels, e.g. Production & Sprint Backlogs It means a feature is Done, Complete, Signed –off, bug-free at feature level, ready for end-users. Where a11y is specified in the Acceptance Criteria of a User Story, it means that success Criteria should PASS! Ensuring Definition of Done Lisa Herrod 2015 @InclusiveUX
  24. 24. Suppose a user story required the user to complete a series of forms to obtain a quote for pet insurance And assigned to it was accessibility acceptance criteria: 4.1.2 Markup … facilitates accessibility appropriately, including forms, form labels, frame titles, etc. Time Permitting… Lisa Herrod 2015 @InclusiveUX
  25. 25. Developer ‘Adem’ is assigned the user story. Wireframes associated with the user story were designed by UX designer ‘Lisa’, who is also noted. In this instance Adem will implement the form with all appropriate accessible form elements, as per Lisa’s design. User Story Success Criteria Developer UX Visual Design Content US 878 4.1.2 AC LH Lisa Herrod 2015 @InclusiveUX
  26. 26. User Stories Product User StoryTitle User Story ID 44 Acceptance Criteria ACCESSIBILITY Pet insurance Online quote AS A dog owner I WANTTO obtain an insurance quote online SOTHAT I can find out the cost of insuring my dog each year. 4.1.2 Markup … facilitates accessibility appropriately, including forms, form labels, frame titles, etc. Lisa Herrod 2015 @InclusiveUX
  27. 27. Success Criteria Identified User Stories Team Member Support Role DoD (Sprint) 1.1.1 98 100 SP SP D AC D AC Equivalent alternatives (e.g. descriptions) to complex images are provided. 1.2.1 106 SP - A descriptive text transcript is provided for audio content (audio podcasts, MP3 files, etc.). A text or audio description is provided for non-live, web-based video-only (e.g., video that has no audio track). A final example, collaboration Content Author (A) Lisa Herrod 2015 @InclusiveUX
  28. 28. Thank-you! LisaHerrod @Scenariogirl @InclusiveUX

×