Please log in to watch this conference skillscast.
Most developers agree that their apps should be “accessible,” but what does that even mean? Even if you’d like to have an accessible application, you find roadblocks along the way: lack of documentation, push-back from product priorities, no standards for mobile devices, and perhaps most importantly, not understanding what users really want. As Accessibility Lead for iTriage, Kelly has worked with advocacy groups such as the Blind Institute of Technology to uncover what makes an app truly accessible, and the actual developer time investment required. Spoiler alert: it’s easier than you might think! Join Kelly as she explores common pain points suffered by many technology users, how the Android platform is quickly gaining on iOS in accessibility features, and how you can make your app accessible to all. You will finish up with code samples of common pain points, including Material Design examples, and learn how easily they can be fixed.
YOU MAY ALSO LIKE:
- Got The Perfect Agile Model? Here’s What You Should Know About Agnostic Agile (in London on 16th August 2017)
- Whole Team Approach to Agile Testing (in London on 6th - 8th November 2017)
- Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests (in London on 7th - 8th November 2017)
- Agile Testing & BDD eXchange 2017 (in London on 9th - 10th November 2017)
Accessibility in Action: Technical Solutions to the Accessibility Challenge
Kelly Shuster is an Android Developer at Ibotta in Denver. Prior to mobile development, she worked as an Embedded Firmware Engineer focused on disk drive read channel optimization. She holds a degree in Electrical & Computer Engineering, and enjoys sharing technical knowledge wherever she goes, from local meetups to international conferences alike.