Support Mobility

#a11y Accesibility logo

WCAG 2.0

TIPS

  • Provide keyboard equivalents to all mouse functions or gestures.
  • Support Tab and Arrow key navigation. Tab to control and use arrow keys to navigate within control.
  • Use standard keyboard interaction as defined in WAI-ARIA design patterns.
  • Ensure there are no keyboard traps.
  • Provide highly visible focus indicators so users know where they are.
  • Provide appropriate page structure: headings, landmarks, skipto links

Testing

  • Unplug your mouse. Can you access and interact with your application?
  • Include skipto.js into your application and test page structure and landmark implementation, See https://github.com/moekraft/accessNav

Resources

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s