Description
This test case is designed to thoroughly assess Accerciser, an accessibility tool used to explore and evaluate the accessibility features of applications in Fedora. It checks for Accerciser's integration, functionality, and compatibility with different applications.
Setup
- Install the pre-release version of Fedora that is to be tested on a bare metal or virtual machine, ensuring that Accerciser is included in the installation.
- Verify that AT-SPI2 is correctly installed and functional, as Accerciser depends on this service to operate.
How to test
1. Launch Accerciser:
- From the application menu.
- Using the command line by typing accerciser in the terminal.
2. Inspect a running application using Accerciser:
- Choose an application like Gedit - Explore the accessibility tree, focusing on different UI elements like buttons, menus, and input fields.
3. Modify properties:
- Open an application such as Gedit (a text editor)
- With Accerciser, connect to the chosen application and locate the 'Accessibility Tree' panel.
- Navigate through the tree structure, which represents the GUI elements of the application. Focus on various components such as menus, buttons, text fields, and links. Try to perform actions like "window.minimize" ideally minimising the window.
- For each selected component in the tree, observe and record the following properties in Accerciser:
a. **Role**: The function of the UI element (e.g., button, link, text field). This helps identify what kind of interaction is expected from the user.
b. **State**: Current status of the element (e.g., enabled, focused, visible). This indicates the element’s interaction state with the user.
c. **Properties**: Additional information like name, description, and value. These properties provide more context about the element, such as what text a button contains or what information a label conveys.
- Perform actions in the main application (like opening menus, selecting items, entering text) and watch how these actions reflect changes in the accessibility tree. Verify that:
- Changes in the UI (like enabling or disabling a button) are immediately reflected in the state of the corresponding element in the accessibility tree.
- The roles and properties are consistent with the visible UI elements and their expected functions.
- Use Accerciser’s interactive features to modify properties (if applicable) and observe how the application responds. For example, change the accessible name of a UI element and check if the new name is reflected both in the accessibility tool and visually in the application.
4. API Browser:
- Navigate through the API browser to check the methods and properties of accessible objects. - Verify the accuracy and completeness of the displayed information.
5. Repeatability:
- Restart Accerciser multiple times. - Reconnect to the same and different applications to ensure consistent functionality and stability.
Expected Results
1. Accerciser should launch successfully from both the menu and command line. 2. Accerciser must connect seamlessly to applications and correctly display detailed information about the accessibility tree. 3. Any modifications made through Accerciser should take immediate effect in the target application without errors. 4. The API browser should provide detailed and correct accessibility information without missing data. 5. The tool should not cause significant system slowdowns or become unstable during tests. 6. Accerciser should demonstrate consistent behavior across restarts and when switching target applications.
Optional
For further exploration, testers can attempt to use Accerciser with newer or less common applications and GUI frameworks to check for any discrepancies or limitations in its compatibility and functionality.