Accessible Rich Internet Applications (ARIA)
In her blog post for this week, Kelsey writes about Arguing w/ ARIA. Well, if a web developer argues with ARIA, as a non-developer, I definitely struggled with ARIA.
Conceptually, I understand the basics of what it is meant to do and why it is needed. And from where I’m sitting at the moment, it seems like a very good idea.
Where do you start?
At the end of my ARIA experiment, I found this ARIA Tooltip Example, which included five steps or considerations to make when thinking about ARIA. Something like this list would have been really helpful from the beginning as a step-by-step process for ARIA beginners.
How do you determine what is needed?
Once I chose some aspect to work on, I also struggled with scope. What needs to be labeled and what doesn’t (some examples seemed redundant, like <button role=”button>)? Where do I attach the ARIA information? How much is too much?
Where are the examples?
When learning CSS and HTML, or working with other accessibility features, I often look up examples on the web to learn from or adapt for my own project. Because ARIA is so new, I could not find a lot of examples available online (and the ones I did find often were above my skill set). Hopefully as ARIA is adopted more widely, more examples are made available, especially ones aimed at beginners.
Web developer and accessibility gurus of the world! Make examples and share them!
So is it worth it?
Yes. ARIA was much more challenging to figure out how to implement, but it seems clear to me that making interactive elements accessible is very important on today’s Web. From forms like a job application to interactive elements in news stories to online quizzes for school, the web only grows increasingly more interactive and dynamic. It is important that we use ARIA (or something similar) to make sure the web doesn’t also continue growing more inaccessible.