Description
Let's face it...ARIA (Accessible Rich Internet Applications) can be very overwhelming. Because of this, we can end up using it incorrectly, or not at all.
Some of you may have heard of the first rule of ARIA: Don't use ARIA. We should always default to native HTML. There is a time and a place for using ARIA to make your content accessible to assistive technologies (AT). That's the purpose of this session:
What we'll cover in this session:
What is ARIA?
Where does ARIA come from?
Who is ARIA for?
What can ARIA do?
When shouldn’t I use ARIA?
When should I use ARIA?
How does Drupal use ARIA?
What confusion is there on how/if/when to use ARIA?
We'll wrap up with some ARIA resources Q & A.
Kat Shaw
Lead Engineer @ LullabotKat is a Lead Engineer (CPACC & Acquia certified) who’s continued her work as an advocate of digital accessibility with her team at Lullabot. She’s been working in web development since 1999, and developing and maintaining Drupal sites since 2012, with a focus on remediating accessibility issues in Drupal. Kat has worked on several accessibility projects including assisting with accessibility testing for the Olivero and Claro themes.
Prior to her work in accessibility, Kat has won the Digital Government Achievement Award and honorable mentions for her work developing apps for government agencies. She served as Secretary for the KC Metro Area Government Webmasters group for most of her decade-plus membership, and has volunteered at and attended several National Association of Government Web Professionals conferences.
