The following be the basic test cases for the default packages added to the workstation. I request feedback on all of these. Feel free to edit and change parts that need more fleshing out.

at-spi2-atk : https://fedoraproject.org/wiki/QA:Testcase_at_spi2_atk
at-spi2-core : https://fedoraproject.org/wiki/QA:Testcase_at-spi2-core
brltty : https://fedoraproject.org/wiki/QA:Testcase_brltty
orca : https://fedoraproject.org/wiki/QA:Testcase_orca

@jkonecny , the a11y folks feel, they would benefit from testing the WebUI installer for the a11y test day. we are 3 weeks out on this. Please let us know, if that will be a good idea and can we get a iso for this test day if rawhide can't handle the change. @adamwill , had thoughts and I would like him to share the best way we can do this! :)

Hi @sumantrom, we are postponing Web UI from Fedora 41 to Fedora 42. So the testing is not necessary. We are planning to deliver more changes which we are not able to do to Fedora 41.

Hello,
thank you very much for this initiative. As a blind user and therefore end user of assistive technology, I highly appreciate that.
I read test cases on Wiki and I have few remarks.
- I feel that tests for at-spi2-atk, at-spi2-core and orca are kinda overlapping. Basically... at-spi2* tests use Orca to prove that at-spi is working. It is fine as a starter but I think this should be improved and hopefully automated. Maybe you could use accerciser package for this? It is more low level than Orca.
- In general, I think tests should have more specific test scenarios. e.g. let's focus on one graphical application (for example Gedit) and let's describe expected results more precisely. Again, this is something for the future. What I mean is for example.

As you navigate through the application and perform actions, Orca should provide corresponding audio feedback without noticeable delays or inaccuracies.

But what is the corresponding feedback?

• This case in at-spi2-atk test set caught my attention:

Closing the application should also result in appropriate feedback from Orca.

What should this feedback be? In real world, Orca usually reads immediatelly something what is displayed in a window which receives focus after the application is closed. Maybe this can be specified as well.
- Note for Brltty: This can be used with Orca as well and it is a frequent use case. It should be covered, but this is rather integratio test, I know.
Feel fre to ping me if you would like more details or if you would like me to help you defining test scenarios.
Best regards,
Vojtech Polasek

Hello,
thank you very much for this initiative. As a blind user and therefore end user of assistive technology, I highly appreciate that.

thanks a lot for the reviews! we are still on track and I will get this sorted today!!

I read test cases on Wiki and I have few remarks.
- I feel that tests for at-spi2-atk, at-spi2-core and orca are kinda overlapping. Basically... at-spi2* tests use Orca to prove that at-spi is working. It is fine as a starter but I think this should be improved and hopefully automated. Maybe you could use accerciser package for this? It is more low level than Orca.

I have come up with this test case for accerciser package
https://fedoraproject.org/wiki/QA:Testcase_accerciser
This is really nice tool, why was this not included in the workstation package set?
I took the list of package from the PR you sent to Comps XML. I believe this is very important packages for developers to know if the application they are developing or using has a11y support.

• In general, I think tests should have more specific test scenarios. e.g. let's focus on one graphical application (for example Gedit) and let's describe expected results more precisely. Again, this is something for the future. What I mean is for example.
  As you navigate through the application and perform actions, Orca should provide corresponding audio feedback without noticeable delays or inaccuracies.
  But what is the corresponding feedback?

• This case in at-spi2-atk test set caught my attention:
  Closing the application should also result in appropriate feedback from Orca.
  What should this feedback be? In real world, Orca usually reads immediatelly something what is displayed in a window which receives focus after the application is closed. Maybe this can be specified as well.

• Note for Brltty: This can be used with Orca as well and it is a frequent use case. It should be covered, but this is rather integratio test, I know.
  Feel fre to ping me if you would like more details or if you would like me to help you defining test scenarios.
  Best regards,
  Vojtech Polasek

Test Day event is now live!

Test Day App : https://testdays.fedoraproject.org/events/190
Test Day wiki : https://fedoraproject.org/wiki/Test_Day:2024-06-19_Fedora_41_A11Y

Fedora Magazine Post to follow!!

Folks, please let me know if something doesn't look right. I am a little under the weather and it will be awesome if someone can actually go ahead and recheck!
I will be looking through the test cases and the feedback @vpolasek gave :)
@vpolasek , can you check the test case and make minor wording adjustments ; that will be helpful