Skip to main content

Keyboard assisted test

Identify issues in the keyboard tab order.

Many users rely on keyboards to navigate the web. For a smooth keyboard navigation experience, the keyboard assisted test helps you check for the following points:

  • Whether the keyboard tabs are ordered logically
  • Whether the visibility of a hidden element is set correctly.

Steps to run and review a keyboard assisted test

Before you run a keyboard assisted test, install and launch BrowserStack Accessibility Toolkit.

A keyboard assisted test involves the following steps:

Run a keyboard assisted test

  1. Launch BrowserStack Accessibility Toolkit.
  2. In the Assisted Test tile, click Select test.
    Click Select test to open an assisted test
  3. From the Starting test drop-down, select the Keyboard assisted test type.
    Assisted Test Type
  4. Select the test scope:
    • Full page: Select this option to test the entire page.
    • Part of a page: Select this option to test a part of the page. If you select this option, you are prompted to manually select a DOM section on the page.
  5. Click Start test. The assisted test detects the tab stops or interactive elements.
  6. The assisted test confirms whether any tab stops were missed. Select Yes or No to confirm.
  7. After all the elements are selected, the assisted test captures screenshots of the elements.

Review keyboard assisted test issues

After you run the keyboard assisted test, the test identifies the elements that are not in the tab order. Follow these steps to review the issues:

  1. For each identified element, answer the question - Is it possible to navigate to this element solely using the keyboard? The question has the following possible answers: Answer the assisted test questions
    • There is no way to navigate to this element: This means that the element is not in the navigation order and cannot be accessed using a keyboard. Also, there is no alternative way to access the element.
    • There is a way to navigate to this element (e.g. arrow keys), and it is in the expected navigation order: This means that the element is in the navigation order, and there is another way to access the element like using the arrow keys on the keyboard.
    • There is a way to navigate to this element (e.g. arrow keys), however it is not in the expected navigation order: This means that the element is not in the navigation order, and there isn’t any other way to access it.
  2. Click Next. The test shows the identified issues.
  3. Click the component to view the issue summary and its fix. Click component to view issue summary
  4. Click Save & end test. The assisted test prompts you to save the test report.
  5. Enter the report name and click Save. You can share the Accessibility Testing Dashboard link to the report or download the report in CSV format.

Next steps

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Download Copy