Accessibility Testing
Overview
The Accessibility Testing feature allows users to evaluate the accessibility of websites directly within the TestGrid platform. This feature provides insights into how well a website complies with WCAG standards, helping to ensure that web applications are usable by people with disabilities. The testing is performed within a TestGrid device cloud’s web browser, enabling a streamlined workflow.
Step 1: Log in with your credentials and navigate to the device cloud module.
Step 2: Initiate a web browser session by spinning up a Device Cloud web browser within the TestGrid device cloud.
- Now, navigate to the specific webpage for which you want to conduct accessibility testing and click the “Accessibility Testing” button, which is available within the user interface of the device cloud browser, to initialize accessibility testing.
Step 3: Once the user clicks the “Accessibility Testing” button, a unique run number is automatically generated for the new accessibility test session.
- Subsequently, the user must either provide a “Project Name” to create a new project and store this session within it or merge the session with existing ones.
- Select the “Use same details for current session” checkbox to generate accessibility metrics for different webpages accessed within the same session under the same “Project Name”
Step 4: Finally, click on the “Save” button.
- Upon clicking the “Save” button, several prompts will be rendered automatically, including “Page information updated successfully,” “Successfully captured current page,” and “Successfully created accessibility run page.”
- These prompts serve as confirmation that the page has been successfully updated to include accessibility testing metrics, and its parameters are also included in the results.
Step 5: Further continue with the flow of the specific webpages and repeat the process of clicking on the “Accessibility Testing” button.
- To ensure comprehensive accessibility analysis for a defined user journey, generate accessibility metrics for each distinct webpage accessed sequentially within the same session, mirroring the webpage flow.
Notes: For a specific session, the accessibility testing metrics will encompass all accessed webpages where the “Accessibility Testing” button was clicked.
Step 6: Once the flow of the webpages in the website that is to be tested is completed, navigate back to the dashboard and click on “Accessibility Testing”.
Step 7: Navigate to the “Project Name” that was previously used to create the current project and store the associated accessibility test session.
Step 8: Navigate to the specific “Run” which was automatically generated earlier for the specific accessibility test session or the run number of the accessibility test execution.
Step 9: Finally, find the page-wise summary that details the accessibility test session executed for the specific “Run”.
Step 10: Navigate to the “All Issues” section to view all accessibility testing issues for each specific page.
- This section details all the issues found during the test session, noting their severity and providing a “Description,” a “Help” section with resolution advice, and an “HTML Snippet” to assist users in resolving the issue.
- Additionally, the user can categorize accessibility issues based on two parameters: 1. Severity and 2. WCAG Guidelines.
Step 11: To share the specific accessibility test session’s results with team, click the share button (highlighted below) and then the green “Copy Link” button.
- Anyone with the copied link can then access the results.
Step 12: Within the Accessibility Test UI (as highlighted in the image below), users can find and utilize specific options to rename or delete an existing accessibility test session instance.
Notes: Users can also generate JIRA bugs for specific accessibility issues found during the test session by clicking the highlighted button in the below screenshot. These bugs can be raised directly through TestGrid’s JIRA integration.
