Today was a short day. I wanted to finish adding ARIA role requirements to my spreadsheet, then take a peek at the next section to plan for my current study week.
Things I accomplished
- Completed my cheat sheet for ARIA role requirements (how to use ARIA roles right).
- Read over the next WAS Body of Knowledge section “Create accessible single-page applications”.
What I learned today
I was surprised that the timer role didn’t have any requirements but the accessible name. Maybe I thought there would be a required marker, of sorts, to read out as the time ticked down? It’s a subclass of the status role, and has 22 inherited states and properties. I haven’t created one myself, so there’s more to explore!
In case you missed it
This is a continuation from Day 44 where I consulted the WAI-ARIA docs about requirements that come along with each role.
