Written by

in

#ID24 @yatil: ARIA stands for accessible rich internet applications, emphasis on internet applications.

Comments

11 responses to “”

  1. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: Not originally intended for websites. Interesting historical tidbit.

  2. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: First rule of ARIA: If you can use native HTML element, do that instead of repurposing another element and adding ARIA.

  3. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: Second rule: Don’t change native semantics unless you have to.

  4. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: Third rule: All interactive controls must be keyboard accessible, and there are specific rules.

  5. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: If role=button, element must be able to receive focus, and enter and space should both activate.

  6. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: Fourth rule: Don’t use role=presentation or aria-hidden on a focusable element.

  7. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: If aria-hidden=true or role=presentation are used incorrectly, things can go very wrong.

  8. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: ARIA support varries across browsers and screen readers.

  9. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: ARIA is a complicated spec to implement for browsers and assistive tech, which means it’s also complicated for devs.

  10. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: Now showing an example of using th as a button. See rule one above for why this isn’t good.

  11. Amanda CAARSON
    Amanda CAARSON

    #ID24 @yatil: aria-label will override an already-existing accessible name.