To ARIA, or not to ARIA -- That is the question. Whether ‘tis nobler in the design to craft a menagerie of outrageous code Or to take arms against increasing tech debt And by opposing, end them. To craft UX, to screen-read -- No more! -- and by screen-read to say we END The heartache, and the thousands of flaws that our code is failing to. ‘Tis an application Devoutly to be wished. To craft UX, to screen-read -- To screen-read -- perchance to dream: ay, there’s the rub, for in that screen-reader of perfection what audience may come When we have refactored our code to serve all who doest live the mortal coil, must be our cause. SparkNotes Version: ARIA is simpler than it looks (and can often be skipped entirely!). This session’s main goal is to make it easier and design for all. As we should, as we must, as we are Architects of a digital future driven by empathy.

Susan LaRonde
Susan is a Web Manager in the College of Education at the University of Texas at Austin. She has been advocating for and working on web accessibility since meeting John Slatin, author of “Maximum Accessibility,” in 2002.

Charles Leverington
Forever a n00b, Charles is a Sr. Developer/Analyst for the Moody College of Communication at the University of Texas at Austin. When not playing in web-dev and DevOps tool-kits, Charles plays with his kids, LEGOs, Blizzard's suite of digital games, and advocates as an a11y with a Design for All mentality.

https://2018.texascamp.org/sessions/a11y--aria-rules-to-use-or-not-to-use