Tips from the trenches Accessibility Testing
Download as PPTX, PDF0 likes280 views
The document discusses the importance of integrating accessibility (a11y) into the software development life cycle (SDLC), emphasizing that it is everyone's responsibility and should start early in the planning phase. It outlines the Web Content Accessibility Guidelines (WCAG) and the common errors found in web pages, along with strategies for inclusive design, testing, and planning to enhance user experience for individuals with disabilities. The content also highlights the need for usability testing and real user feedback to effectively identify and address accessibility issues.
Tips from the trenches Accessibility Testing
- 1. Manoj Kumar Kumar Tips from the Trenches: Accessibility Testing @manoj9788
- 2. Tips for today! A Primer on Accessibility A Good-For-All SDLC Accessibility Testing Q&A
- 3. A Primer on Accessibility
- 6. Develop for the future Abilities in Decline: The Persona Spectrum Microsoft Inclusive Design Kit
- 7. Digital Accessibility If your app isn’t accessible, you are creating barriers & making their impairment a disability
- 8. The Web Accessibility Initiative at the World Wide Web Consortium outlined four main web accessibility principles in the Web Content Accessibility Guidelines : WCAG
- 9. WCAG Conformance Levels Level A Level AA Level AAA Basic Level of A11Y Most Common Barriers Highest Level of A11Y 13 38 61 Web Content Accessibility Guidance : W3C
- 10. A11Y Standard - WCAG
- 12. We all need to understand that accessibility (a11y) isn’t “someone else’s job” ; Accessibility is everyone’s responsibility and its even better if it starts from us as <role you play>.
- 13. Early planning on Accessibility leads to multiple benefits: • Reducing legal risks • Strengthening brand presence • Improving customer experience • Inclusive and productive teams Inclusive design practices should be advocated. • Product roadmap with user personas with disabilities • Design of user interaction considers experiences other than screens when accessibility is a consideration. • The result is, interaction that is more human-centered, natural, and contextual. Understand the guidelines and select the conformance levels adhere to. • The conformance levels should be built into the project's formal technical specifications and included as part of the budget. Accessibility at Analysis &Planning Phase
- 14. Accessibility at Design Phase Start as early as possible from UX prototypes Introduce Design kit, GEL and bake in A11Y. Define Inclusive Colour Contrast Design ethos. Avoid tech that are known to be inaccessible Conduct usability testing outside of your organization.
- 15. Accessibility at Development Phase Inclusive mindset Design what everyone can use and not what is easy to develop Workshops on A11Y specific to creating accessible components. Learning on Focus order Using ARIA judiciously
- 16. Accessibility at Testing Phase Consider people with disabilities for user testing Automated Accessibility is not a silver bullet solution, but still good enough find about 40-50% of A11Y issues Test and ensure quality of A11Y at all the levels of Test Pyramid Consider adding A11Y tests as part of your build Use Screen readers
- 18. There is no substitute for real user feedback. Include people with disabilities to test
- 19. What can you test? Test for Keyboard navigation Test for Touch Target Size Test for Landmarks Test for color contrast ratio Test for Form labels Test with Assistive devices
- 20. Let’s roll the wheels for good… Photo by Tim Mossholder on Unsplash
- 23. Inclusive Path to Production
- 24. Common A11Y errors Low contrast text Missing alternative text for images Missing form input labels Empty links Missing document language Empty buttons WebAIM says 97.4% of home pages had detected WCAG 2 failures. https://webaim.org/projects/million/#wcag
- 26. Thank you!
- 28. Inclusive Path to Production
- 29. Common A11Y errors Low contrast text Missing alternative text for images Missing form input labels Empty links Missing document language Empty buttons WebAIM says 97.4% of home pages had detected WCAG 2 failures. https://webaim.org/projects/million/#wcag
- 32. Link to look at demo https://github.com/manoj9788/webdriverio- a11y-demo
- 33. Thank you!
Editor's Notes
- #13: An accessible site is one whose content can be accessed regardless of any user's impairments and whose functionality can also be operated by the most diverse range of users possible. As developers, it's easy to assume that all users can see and use a keyboard, mouse, or touch screen to interact with your page. This can lead to an experience that works well for some people but creates issues for others that range from simple annoyances to complete blockers.
- #14: Accessibility deserves dedicated thinking and planning, but it should not be done in isolation. Rather, it should be integrated into your organization’s processes. There may be legal requirements which should be taken into consideration. Many organizations use WCAG as a target for accessibility. For example, an organization may set its target to meet WCAG 2.0 Level A or Level AA success criteria. Developing an accessibility policy is a good way to clarify and communicate its target. Early planning on Accessibility leads to multiple benefits: Inclusive design practices should be advocated. Think about user personas with disabilities design of user interaction considers experiences other than screens when accessibility is a consideration. Think through and accept a conformance levels adhere to. The conformance levels should be built into the project's formal technical specifications and included as part of the budget.
- #15: (Global Experience Language)
- #16: Checklists often work well for the developer mindset and are essential at the planning stage when product requirements are defined, at the design stage in the creation of the design, and during development when implementation of the product begins. https://www.w3.org/TR/2006/WD-WCAG20-20060427/appendixB.html Most of the things can be built using native HTML constructs
- #18: Start early with Accessibility. Starting early has many benefits including that it is much less costly than assessing accessibility at the end of a project. Involve the whole team. Ensure that all concerned (project board, team members, designers, content providers and developers) all understand the requirements for accessibility. Once the "why" of accessibility is understood, the "how" is easy to implement and can eventually be introduced as a best practice within the organization. The most robust way to ensure long-term accessibility is to ensure that the accessibility knowledge is incorporated and remains within the organizations. https://github.com/dequelabs/axe-core/blob/develop/doc/rule-descriptions.md
- #21: We will see a voice over demo Color contrast in devtools + Axe plugins Mac based color changer App demo on unit and integration
- #24: Now, I’d like you to visualize some of the learnings that you had from previous slides and from the hands-on demo. I present you here an ideal Inclusive Path to production with accessibility test strategy.
- #25: 96.7% of all errors detected fall into these six categories. Addressing just these few types of issues would significantly improve accessibility across the web.
- #26: Thanks for joining the session, I consider that our Passion led us here. You’ve already made steps to ensure you care about inclusive culture and inclusive tech disruptor. I do hope had some nice takeaways from this session and make the world digitally connected with inclusivity.
- #27: Thanks for the opportunity to talk about an important topic that I always care about, this conference had a few other talks in the space for Inclusiveness, which is great. Happy Thanks Giving, Merry Christmas and Happy new year!
- #29: Now, I’d like you to visualize some of the learnings that you had from previous slides and from the hands-on demo. I present you here an ideal Inclusive Path to production with accessibility test strategy.
- #30: 96.7% of all errors detected fall into these six categories. Addressing just these few types of issues would significantly improve accessibility across the web.
- #31: Thanks for joining the session, I consider that our Passion led us here. You’ve already made steps to ensure you care about inclusive culture and inclusive tech disruptor. I do hope had some nice takeaways from this session and make the world digitally connected with inclusivity.
- #34: Thanks for the opportunity to talk about an important topic that I always care about, this conference had a few other talks in the space for Inclusiveness, which is great. Happy Thanks Giving, Merry Christmas and Happy new year!