From Fedora Project Wiki

Revision as of 15:56, 28 May 2024 by Sumantrom (talk | contribs) (Created page with "{{QA/Test_Case |description=This test case ensures that the Assistive Technology Service Provider Interface (AT-SPI2) functions correctly in Fedora, facilitating accessibility features like screen readers and automated UI testing tools. |setup= # Install the pre-release version of Fedora that is to be tested on a bare metal or virtual machine, making sure that AT-SPI2 is included in the installation. # Install an accessibility tool that relies on AT-SPI2, such as Orca sc...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Description

This test case ensures that the Assistive Technology Service Provider Interface (AT-SPI2) functions correctly in Fedora, facilitating accessibility features like screen readers and automated UI testing tools.

Setup

  1. Install the pre-release version of Fedora that is to be tested on a bare metal or virtual machine, making sure that AT-SPI2 is included in the installation.
  2. Install an accessibility tool that relies on AT-SPI2, such as Orca screen reader.

How to test

  1. Start the system and log into the desktop environment.
  2. Enable the Orca screen reader via the accessibility menu or using a command in the terminal.
  3. Navigate through various system menus and applications using keyboard shortcuts and listen to the feedback from Orca.
  4. Open a document in a text editor and a web page in a browser, ensuring that Orca reads the content correctly.
  5. Use tab and arrow keys to navigate through UI elements on the desktop and within applications, verifying that all elements are announced by Orca.
  6. Optionally, test other AT-SPI2 dependent applications or features.
  7. Log out and back into the system and repeat steps 2 to 5 to ensure consistency.

Expected Results

  1. AT-SPI2 must initialize correctly and without errors upon system start.
  2. Orca should be able to verbalize the contents and controls of the UI accurately.
  3. Navigation through UI elements must be fluid and correctly vocalized, with no elements being skipped or misrepresented.
  4. Repeated logins should yield consistent AT-SPI2 and Orca performance without degradation.

Optional

Testers may also want to explore how AT-SPI2 handles dynamic content updates in applications like email clients or instant messaging to assess its real-time response capabilities.


Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_at-spi2-core&oldid=710721"