@adamwill, I have been instructed by @sdharane to start working on testing the subject.
I believe that we could re-use Gnome tests that we already have. We could switch on accessibility (various types of it) and just create another bunch of needles to match them with the changed graphics.
When an increased number of needles is a concern, we could theoretically run different Gnome tests with various accessibility settings, for instance we could run Calculator with increased fonts, and Text editor with different color combinations, etc. This would save some needle space.
What do you think about this?
I think it's a bad idea to mix two test purposes ("does this app work?" and "does a11y work?")
Say the app breaks, and we don't get an immediate fix - now we don't have a test of whatever a11y functionality the test is also covering, until the app is fixed. And, of course, vice versa.
So despite the needle load I think we should make this a separate test :/
I guess the idea here is to automate https://fedoraproject.org/wiki/QA:Testcase_Gnome_Accessibility ? It should be noted that we currently have no release criteria for this, so failures of this test would not be release blocking.
btw, most of the changes we can test apply to the settings dialog itself, so they can be quite easily tested. However, I'm not sure how far we want to go with making sure they also apply to other types of application. For instance, the "always show scrollbars" setting does not seem to take effect for Firefox or Evolution, for me - I'm not sure if we should report that as a bug and test it, or what. We may need advice from @catanzaro et. al. here.
Firefox isn't a GTK app so I wouldn't necessarily expect it to respect GNOME settings. Better if it does, of course.
Not sure why Evolution doesn't respect the always show scrollbars setting? Other WebKitGTK apps like Epiphany and Geary certainly do. But note this only disables overlay scrollbars; it doesn't force scrollbars to appear when no scrolling is possible.
Suggestion of the testing plan
Displaying Accessibility Menu: - Verify if the accessibility menu is always visible when set so - check if the character icon is placed in the top right corner of the page and if it can be activated to open the accessibility menu.
Visual Options: - Test high contrast is present when set. - Check the ability to toggle shapes, enlarge text, and cursor size. - Verify if scroll bars are always displayed when set.
Hearing Options: - No specific testing functionality mentioned for users with hearing impairments as I do not have an idea how openQA could do it.
Typing Options: - Verify the availability of the virtual keyboard and check its functionality when typing.
Pointing and Clicking Options: - Test pointer size and ensure it is sufficiently visible. - Verify the ability to search for the pointer. - Test click delay and ensure the functionality of simulated secondary clicking.
Zooming Options: - Check the zoom function and verify if it's possible to enable zoom and how well it works.
What do you think about it? Also, besides this, I could switch on several features and have one of the application tests run in that environment.
See #321
Metadata Update from @lruzicka: - Custom field story_points adjusted to 6
Log in to comment on this ticket.