When you aim for accessibility, you're guaranteed to hear about WAI-ARIA. But what is ARIA? When do you use it -- and more important, when don't you? We'll take an ebook and learn how to use ARIA to gain accessibility for modern, dynamic content. We'll learn when you can trust HTML to do the right thing, when ARIA is necessary, and where ARIA is necessary but not enough. The workshop focuses on practical examples.
47. HTML5 WAI-ARIA
input required input aria-required=“true”
button div role=“button”
div hidden div aria-hidden
hr div role=“separator”
nav div role=“navigation”
ul div role=“list”
input placeholder=“Text!” input aria-placeholder=“Text!”
48. –
™ Don’t use it if HTML already does the job
™ Don’t add it anyway “just in case.”
™ Do add redundancy if necessary.
™ Do add redundancy for DPUB-ARIA.
Redundant Semantics
51. THEY BOTH
LOOK REAL TO
US!
Screen
Reader
Speech
Recognition
Other AT
ONLY THE
<BUTTON> IS
REAL!
52. –
™ ARIA doesn’t change browser behavior.
™ Keyboard handling is your job!
™ ARIA gives info to screen readers, speech
recognition, and other AT.
For Assistive Tech Only