Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Tech Talk: a11y testing at the HTO team

Tech Talk: a11y testing at the HTO team

Camunda Tech Talk

Niklas Kiefer

July 25, 2023
Tweet

More Decks by Niklas Kiefer

Other Decks in Technology

Transcript

  1. What’s in • Why a11y testing matters • Different strategies

    for your development routines ◦ manual vs. automatic testing ◦ unit vs. integration testing • Code examples
  2. Accessibility (a11y) “Accessibility is the practice of making your websites

    usable by as many people as possible. We traditionally think of this as being about people with disabilities, but the practice of making sites accessible also benefits other groups such as those using mobile devices, or those with slow network connections.” https://developer.mozilla.org/en-US/docs/Learn/Accessib ility/What_is_accessibility
  3. a11y testing - Why it matters • regularly test your

    components against a set of defined rules and best practices • automatic testing: catch bugs earlier ◦ “find on average 57% of WCAG issues automatically”, cf. https://github.com/dequelabs/axe-core • get a better understanding of how our products works for a wider range of users
  4. Manual testing • Tab like crazy • Use dev tools

    • Use screen readers or voice recognition tools • Conduct a11y audits
  5. Conduct a11y audits • Use the techniques mentioned before •

    Collect critical a11y issues • Act on them • Example
  6. Automated testing • Unit tests - test your components •

    Integration tests - test Tasklist e2e scenarios
  7. • HTO team docs • Web Content Accessibility Guidelines •

    Carbon a11y guidelines • axe dev tools Helpful resources