# data[].attributes.blurb.html
The first rule of ARIA suggests it is better avoided if there is an HTML equivalent. Yet sometimes, the right use of ARIA can improve your UI better for end users. In this talk, we’ll look at practical examples of effective ARIA usage and how they work in assistive technologies. Find out more about the patterns that have broad support and which ones to avoid. Let’s look at ARIA, the good parts!

# data[].attributes.slidedeck.data[].slides[].desc.html
full transcript of a previous iteration of this talk (the captions in this deck are empty)

# data[].attributes.resources.data[].desc.html
The WAI-ARIA standard

# data[].attributes.resources.data[].title
Post by Eric Eggert on aria-label and the replies to it

# data[].attributes.resources.data[].desc.html
Eric Eggert asked: “Is there a good overview on the ARIA roles that overwrite their contents when aria-label is used (button, a,…) and those who do not (nav, region,…)? I looked into the ARIA standard, but didn’t find it.”

# data[].attributes.resources.data[].title
WAI: How people with disabilities use the web

# data[].attributes.resources.data[].title
Scott O’Hara - output: HTML’s native live region element

# data[].attributes.resources.data[].title
WebAIM: To ARIA! The Cause of, and Solution to, All Our Accessibility Problems

# data[].attributes.resources.data[].title
Marco Zehe: use WAI-ARIA menus with care

# data[].attributes.resources.data[].title
WAI-ARIA recommendation on managing focus

# data[].attributes.resources.data[].title
Marco Zehe: if you use role=application, please do so wisely

# data[].attributes.resources.data[].title
GitHub issue: “aria-relevant: find real-world use cases, consider deprecating it”

# data[].attributes.resources.data[].title
Aaron Leventhal: “How Blink implements aria-owns”