as 13 guidelines under 4 principles Perceivable Users must be able to perceive the information being presented Operable Users must be able to operate the interface Understandable Users must be able to understand the information on the interface Robust Users must be able to access the content as technologies advance
Accessible Rich Internet Applications (ARIA) ARIA is a specification from the W3C and created to improve accessibility of applications by providing extra information to assistive technologies, such as screen readers, via attributes which could be added to HTML. Roles States and Properties
Drag and drop Live regions Modal States and Properties Button Checkbox Link Radio Scrollbar Searchbox Slider Switch Tab Tabpanel Option Progressbar Textbox Treeitem Widgets Banner Complementary Contentinfo Form Main Navigation Search Application Landmarks
presses to navigate 6 items 6 key presses to navigate 6 items IE defines SVG elements as focus-able. The first keypress puts focus on the anchor and second moves the focus to the SVG.
class=”paragraph”>I’m a cute butterfly<div> vs <h1>header</h1> <p>I’m a cute butterfly</p> <h1 role=”tab”>header<h1> vs <div role=”tab”> <h1>header<h1> </div> If you an use a native HTML element or attribute with the semantics of behavior you require already built into it, then do so Do not change the native semantics
processes Actively managing, controlling standard accessibility processes Using standard, documented processes for accessibility across the organization Encouraging discipline and increasing the repeatability of accessibility processes Performing accessibility activities in an ad hoc, uncontrolled and reactive manner Initial (Chaotic) We are here A11y Maturity Model
danielwang
jponch
maltzj
bkeepers
addyosmani
thekraken
michaelherold
pedronauck
brianwarren
mraible
philhawksworth
sergeychernyshev
jnunemaker
