ARIA audit

[imakewebthings]

There are probably a number of aria-* attributes that could be utilized. Go through core and all the extensions and see what we can do.

From vick08 on Twitter:

I suggest aria-hidden=true on the offscreen content to prevent keyboard access to it.

[imakewebthings]

Some other changes I feel confident about:

• Change the deck.navigation snippet to use role=navigation.
• Give the deck.status snippet a role of status.
• When navigation elements are disabled (due to being on first or last slide) give them aria-disabled=true.
• Toggle aria-hidden as appropriate for the deck.goto form.

Possibilities that may or may not be helpful (If anyone reads this and has feedback, would be appreciated):

• Give the deck container a menu role when in that view via deck.menu extension. Each slide would be given a menuitem role and the aria-selected state would be maintained as the deck is navigated from the menu view. Focus management and key bindings to "active" the slide/menu-item would need to be rethought to fall in line with typical widget key bindings (I'm thinking of the Enter key in particular.)

[imakewebthings]

In master. The doc change needed is for the added setAriaHiddens option in core.

[imakewebthings]

This is included in the 1.1.0 release.