Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

#techInColor 2017: Practical Web Accessibility Testing

424 vues

Publié le

From my 2017 #techInColor lightning talk for Philly Tech Week.

Summary
=======
Thinking about accessibility in every step of your process ensures legal compliance but helps create a well-designed, more inclusive product that reaches a broader range of people. Testing your site or application for common accessibility user experience problems helps reduce barriers between you and your intended audience.

Watch a recorded screencast of this presentation on YouTube (10m 6s): https://youtu.be/0uoH66mnqNw

Publié dans : Technologie
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1lite.top/q7m9i ◀ ◀ ◀ ◀
       Répondre 
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici
  • Get Paid To Write Articles? YES! View 1000s of companies hiring online writers now! ♣♣♣ http://ishbv.com/easywriter/pdf
       Répondre 
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici

#techInColor 2017: Practical Web Accessibility Testing

  1. 1. Practical Web Accessibility Testing May 2, 2017 #techInColor 2017
  2. 2. PRACTICAL WEB ACCESSIBILITY TESTING Introduction About Me UI Developer at Think Company User Acceptance Tester at Comcast (Left: photo of me with long hair, caption: UX; Right: photo of me with fresh haircut, caption: UI) Who Is This Talk For Web professionals People who want to design better experiences People interested in including everyone Those interested in starting a11y testing or advocacy in their organization
  3. 3. Overview Why should we start accessibility testing? Who are we testing for? What are some tools we can use? What are some top concerns? What else can we do?
  4. 4. Why Do We Want to Do A11y Testing? Practical Web Accessibility Testing
  5. 5. Why Do We Want to Do A11y Testing? Prevent legal action Better code and technology Reach more customers It’s the right thing to do
  6. 6. The Audience Practical Web Accessibility Testing
  7. 7. The Needs of Our Audience Visual Auditory Motor and Mobility Cognitive
  8. 8. The Tools Practical Web Accessibility Testing
  9. 9. Manual Screen Reader Testing Practical Web Accessibility Testing The Tools Online Checkers and APIs W3C Validator WebAIM WAVE (Web A11y Evaluation Tool) Tenon Deque aXe (Browser Extension) Readable.io and Juicy Studio: Readability Test Color Contrast Checkers WebAIM: Color Contrast Checker Colour Contrast Analyser (CCA) by Paciello Group Contrast Ratio by Lea Verou Color Contrast Analyzer (Chrome Extension) Contrast Ratio Checker (Chrome Extension) NVDA (NonVisual Desktop Access) (with Firefox) JAWS Screen Reader (with IE, Edge incompatible) VoiceOver (primarily iOS, also available on macOS) TalkBack (Android) Switch Access AbleNet Switches (such as the Blue2) iOS Switch Control Android Switch Access
  10. 10. The Concerns Practical Web Accessibility Testing
  11. 11. Keyboard Navigation Practical Web Accessibility Testing The Concerns Conveying Information Proper HTML form elements and labels Logical heading structure Unlabeled elements in native applications Use of Color Use of only color to convey information Sufficient color contrast No keyboard support Focus management Visual focus indicator “Skip to”/in-page links Single page application routing Alternatives to Multimedia Closed Captioning Video Descriptions ALT attributes for images Transcriptions
  12. 12. What Else? Practical Web Accessibility Testing
  13. 13. Developers Practical Web Accessibility Testing What Else Can We Do?* Product Make accessibility a business case and priority Require accessibility in your company’s definition of “Done” Design/UX Include people with disabilities in personas Annotate wireframes Consider accessibility and AT when designing Clarify requirements Include accessibility from the beginning Use automated testing tools QA Test with keyboard Test with AT and also use them Write accessibility test cases Use testing tools Research Look at accessibility history in the organization and make recommendations Conduct user testing with real people *Credit Marcy Sutton, Sr. FE Engineer at Deque
  14. 14. In Conclusion Empathize with others Consider who we might be forgetting Look into available tools Research and evaluate high priority concerns Get everyone involved
  15. 15. As designers, we disable people when we don’t get it right. “ -Jamie Knight Senior Accessibility Specialist at BBC
  16. 16. Thank You

×