From Fedora Project Wiki

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 gedit, use ATK).

How to test

  1. Open a terminal.
  2. Start the Orca screen reader by entering orca.
  3. Listen for the initial startup narration from Orca.
  4. Open an ATK-based application, for example, gedit.
  5. Navigate around the application using keyboard shortcuts and listen to the feedback from Orca.
  6. Create a sample text in the application and ensure Orca narrates the text and application actions correctly.
  7. Close the application and listen for Orca's feedback.

Expected Results

  1. Orca should successfully start and give feedback on its startup status.
  2. On launching the ATK-based application, Orca should narrate relevant details about the application's window and available controls.
  3. As you navigate through the application and perform actions, Orca should provide corresponding audio feedback without noticeable delays or inaccuracies.
  4. Closing the application should also result in appropriate feedback from Orca.

Optional

For comprehensive testing:

  1. Test with different ATK-based applications to ensure consistent behavior across various programs.
  2. Modify Orca's settings (like speech rate or verbosity) and verify if the changes take effect when interacting with ATK-based applications.
  3. Try out other accessibility tools that use the AT-SPI2 framework and observe their interaction with ATK-based applications.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_at_spi2_atk&oldid=686622"