Accessibility lab exercise
Lab 1: Keyboard Navigation Test
Keyboard Navigation: a test to verify that the content is accessible by keyboard
users.
Many people who are blind, who have low vision, or who have mobility issues use
only the keyboard for navigation. Some users may need more time to read the
content, respond to a request or complete a form on a web page so they need a way
to turn off or adjust the time limits. To provide the access for these groups of users
all content must be keyboard accessible, including links, form controls, interactive
elements, etc.
What do we test?
• The operation of all links, form controls, dialogs, scripts, and methods that
provide time limits
• The logical navigation and focus indication of the content
• Make sure no trapping content
• When controls receive focus or change state
• When content is added or removed from the current page
• Test consistent navigation for similar pages
Common keystrokes used during Keyboard Navigation
• TAB and SHIFT+TAB – to move focus back and forth between links and form
controls
• F6 – to moves between the frames and address bar of IE
• ENTER or SPACE – to activate links and buttons or check and uncheck
checkboxes
• ALT+DOWN ARROW – to drop down option menu of combo or select boxes
• UP/DOWN ARROW – to select the options in the combo or select boxes
• LEFT/RIGHT/UP/DOWN ARROW – to move between radio buttons or move
the cursor in the input text field or text area
• ESC – to close a dialog or a dropdown list
Lab Exercise:
Step 1: Take away the external mouse. Here we will use only keyboard to navigate the web pages.
Step 2: Open a chrome web browser with latest version and open one of the websites given below.
Step 3: You can use one of the following websites to test the keyboard navigation.
https://www.fitbit.com/global/us/home
https://www.kohls.com/
https://www.foxnews.com/
https://tahoe.com/
https://www.dropbox.com/
Step4: Use only keyboard to navigate every single screen and make sure that and come up with 15
issues. Report each issue with screen shots and description in the following format.
Each issue should be reported as 1 defect. So each table should have a valid defect. Compile all these
issues in a word document as one single report for Keyboard testing.
I will upload the rest in pdf file.