From Fedora Project Wiki
(Created page with "{{QA/Test_Case |description=This test case ensures that the `at-spi2-atk` module correctly bridges ATK-based applications to the AT-SPI2 accessibility framework. |setup= 1. Ensure you have a Fedora system with a graphical interface. 2. Install the `at-spi2-atk` and `orca` (a screen reader that uses AT-SPI2) using the package manager: `sudo dnf install at-spi2-atk orca`. 3. Have an application that uses the ATK toolkit ready for testing (many GNOME applications, like `ged...") |
No edit summary |
||
| Line 2: | Line 2: | ||
|description=This test case ensures that the `at-spi2-atk` module correctly bridges ATK-based applications to the AT-SPI2 accessibility framework. | |description=This test case ensures that the `at-spi2-atk` module correctly bridges ATK-based applications to the AT-SPI2 accessibility framework. | ||
|setup= | |setup= | ||
# Ensure you have a Fedora system with a graphical interface. | |||
# Install the `at-spi2-atk` and `orca` (a screen reader that uses AT-SPI2) using the package manager: `sudo dnf install at-spi2-atk orca`. | |||
# Have an application that uses the ATK toolkit ready for testing (many GNOME applications, like `gedit`, use ATK). | |||
|actions= | |actions= | ||
# Open a terminal. | # Open a terminal. | ||
| Line 19: | Line 19: | ||
# Closing the application should also result in appropriate feedback from Orca. | # Closing the application should also result in appropriate feedback from Orca. | ||
|optional=For comprehensive testing: | |optional=For comprehensive testing: | ||
# Test with different ATK-based applications to ensure consistent behavior across various programs. | |||
# Modify Orca's settings (like speech rate or verbosity) and verify if the changes take effect when interacting with ATK-based applications. | |||
# Try out other accessibility tools that use the AT-SPI2 framework and observe their interaction with ATK-based applications. | |||
}} | }} | ||
[[Category:Package_at_spi2_atk_test_cases]] | [[Category:Package_at_spi2_atk_test_cases]] | ||
[[Category:Critical_path_test_cases]] | [[Category:Critical_path_test_cases]] | ||
Latest revision as of 18:13, 12 August 2023
Description
This test case ensures that the at-spi2-atk module correctly bridges ATK-based applications to the AT-SPI2 accessibility framework.
Setup
- Ensure you have a Fedora system with a graphical interface.
- Install the
at-spi2-atkandorca(a screen reader that uses AT-SPI2) using the package manager:sudo dnf install at-spi2-atk orca. - Have an application that uses the ATK toolkit ready for testing (many GNOME applications, like
gedit, use ATK).
How to test
- Open a terminal.
- Start the Orca screen reader by entering
orca. - Listen for the initial startup narration from Orca.
- Open an ATK-based application, for example,
gedit. - Navigate around the application using keyboard shortcuts and listen to the feedback from Orca.
- Create a sample text in the application and ensure Orca narrates the text and application actions correctly.
- Close the application and listen for Orca's feedback.
Expected Results
- Orca should successfully start and give feedback on its startup status.
- On launching the ATK-based application, Orca should narrate relevant details about the application's window and available controls.
- As you navigate through the application and perform actions, Orca should provide corresponding audio feedback without noticeable delays or inaccuracies.
- Closing the application should also result in appropriate feedback from Orca.
Optional
For comprehensive testing:
- Test with different ATK-based applications to ensure consistent behavior across various programs.
- Modify Orca's settings (like speech rate or verbosity) and verify if the changes take effect when interacting with ATK-based applications.
- Try out other accessibility tools that use the AT-SPI2 framework and observe their interaction with ATK-based applications.