Manager checklist
The following checklist is intended to guide managers on the review of keyboard accessibility. It should be used during the review phase to ensure compliance of the site.
Areas of importance to be reviewed for keyboard access are also covered specifically in the relevant category factsheet:
- Navigation
- Content
- Coding
- Forms
- Interactive site features (e.g. Interactive Maps, Slideshow, Image Gallery, etc.).
Level A
- KYB_A1:
- Is the site keyboard accessible (i.e. there are no keyboard traps within the navigation, content, links, form elements, buttons or any other object control within interactive or static content of the site)?
- KYB_A2i:
- Is all content keyboard accessible (i.e. all interactive features and static content can be fully accessed and operated with the keyboard alone)?
- KYB_A2ii:
- Is all content keyboard accessible (i.e. the TITLE attribute has not been used on links to present information not otherwise present on the page)?
- KYB_A2iii:
- Is all content keyboard accessible (i.e. the TITLE attribute has not been used on images to present information not otherwise present on the page)?
- KYB_A3:
- Does the item presentation (e.g. navigation, content, links, form elements, buttons or any other object control) change on keyboard focus?
- KYB_AA1:
- Is there a highly visible keyboard focus indicator on all items (e.g. navigation, content, links, form elements, buttons or any other object control)? Note: Although this is a AA issue, its impact on users is very high and addressing it as if it were a Level A, high impact issue is recommended.
- KYB_A4i:
- Does all content appear on keyboard focus (i.e. the appearance of content such as tool tips is consistent with its appearance on mouse over)?
- KYB_A4ii:
- Is the keyboard focus order meaningful – does the TAB order preserve meaning and operability (i.e. the TABINDEX attribute has not been used as this may interfere with built-in logical tab order)?
- KYB_A5i:
- Are standard keyboard shortcuts operable (i.e. the ACCESSKEY attribute has not been used as this may interfere with the shortcuts of the browser, operating system, or assistive technology)?
- KYB_A5ii:
- Are standard keyboard shortcuts operable (i.e. can the navigation be operated through standard keyboard means such as using the TAB key to move across the top menu and the up and down arrow keys to move up and down the navigation dropdown)?
- KYB_A6:
- Is all page content and instructional text device-independent (i.e. “click” alone is not used)?