Website Accessibility Tip of the Week: Keyboard Navigation
The keyboard accessibility guideline is based on the second Web Content Accessible Guide (WCAG) 2.0 principle, Level A: Principle 2 – Operable and states: User interface components and navigation must be operable.
The WCAG 2.0 Guideline 2.1. Keyboard Accessible was created based on that principle stating: Make all functionality available from a keyboard.
The WCAG 2.0 Success Criterion 2.1.1 Keyboard states: All functionality of the content must be operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
Keyboard Accessible Best Practices
- Create links and link text using the link annotation (the link button) and link structure elements in PDF documents.
- Provide interactive form controls when building web forms and forms in PDF documents.
- Ensure correct tab and reading order, this facilitates a user who is using the tab key to move around the content in the correct order, especially in PDF documents.
- Provide keyboard-triggered event handlers
See the additional resources below to learn more details about the WCAG 2.0 Guideline 2.1. and Success Criterion 2.1.1.:
Discover more website accessibility resources on the Trent University Marketing & Recruitment website
Posted on December 12, 2016