Karl Groves

Understanding the cost of not being accessible

Screenshot of “Understanding the cost of not being accessible”

the single worst accessibility-related business strategy you can take is to stay in that audit-fix-audit-fix cycle

  1. screenshot of Accessibility Beyond Code Compliance

    Aaron Gustafson avatar Aaron Gustafson

    Accessibility Beyond Code Compliance

    Design systems (and pattern libraries within them) codify your organization’s design and coding guidelines in such a way that the software you produce is consistent and the teams working on delivering that software are able to be more efficient because they aren’t having to design and build every interface from scratch. Having a design system that is accessible enables teams to avoid introducing new accessibility bugs in the process of creating bespoke interfaces. It also means finding and fixing an accessibility bug in the design system should fix it in all of the products using that design system. (That last part isn’t always perfect, but I don’t have time to get into that today.)

  2. screenshot of Alt vs Figcaption

    Elaina Natario

    Alt vs Figcaption

    While both the alt attribute and the figcaption element provide a way to describe images, the way we write for them is different. alt descriptions should be functional; figcaption descriptions should be editorial or illustrative.

  3. screenshot of How A Screen Reader User Surfs The Web

    Léonie Watson avatar Léonie Watson

    How A Screen Reader User Surfs The Web

    In this webinar you’ll learn how and why semantic HTML helps screen reader users browse your website, whilst being mostly transparent to people who do not use an Assistive Technology (AT). Join Léonie Watson, a blind screen reader user, as she explores the web, and find out about some unexpected properties of HTML elements that not only have a huge impact on accessibility, but also turn out to be pretty good for performance too.