Category: tab

Keyboard Accessibility from Lauke

Patrick Lauke’s keyboard accessibility presentation at Future of Web Design Tour 2009 in Glasgow. September 14. Keyboard accessibility – basic steps towards a more usable and accessible site. Keyboard Access for Google Map

  • If you style :hover, also :focus and :active.
  • Don’t suppress outline completely (reintroduce :focus and suppress :active).
  • Leave tabindex alone – source order.
  • JavaScript on hover (mouseover/mouseout) also on focus/blur (if focusable element).
  • Lightboxes have issues.
  • Only attach behaviour to focusable elements.

MORE:
Keyboard-accessible Google Maps
http://dev.opera.com/articles/view/keyboard-accessible-google-maps/

Enhanced Keyboard-accessible Google Maps
http://learningtheworld.eu/2009/keyboard-accessible-google-maps/

Tab Index – why and why not

WCAG Guidelines 9.4 (Priority 3) says to create a logical tab order through links, form controls, and objects. The “tabindex” attribute is great because it does exactly that — it specifies the position of the current element in the tabbing order for the current document. But are they needed?

Download Web Axe Episode 24 (Tab Index — Why)

[Transcript]

The basic code:


Links: