Day 47: ARIA Live Regions, Part 2

Published on 16 Jan 2019

• journal
• was
• aria
• spas

Yesterday during my Part 1 learning, I watched videos that gave me a great idea of how live regions worked. Today I looked over documentation to see what W3C had to say about it.

Read the WAI-ARIA documented parts on:

• aria-live (property)
• aria-atomic (property)
• aria-relevant (property)
• aria-busy (state)

• The politeness value of aria-live is just a strong suggestion to user agents and AT, but may be overridden by user agents, AT, or the user.
• Some ARIA roles (i.e. log, status) already have default aria-live politeness levels (implicit value for role) when aria-live is not set.
• aria-relevant indicates what notifications the user agent will trigger when the accessibility tree within a live region is modified.
• aria-relevant values include:
  • additions
  • additions text
  • all
  • removals
  • text
• aria-busy is a state, not a property.
• aria-busy exists to indicate an element is being modified and that AT may want to wait until the modifications are complete before showing them to the user.