Seeing the discussion below show up on Matrix (I know it’s GNOME, but bear with me!)
…reminded me of posts like this that were made around the launch of the Shake Cursor effect, and made me wonder, is there a possible case to be made that:
- Anything considered an Accessibility feature, by definition impacts some aspect of the device’s operation
- Folks who may benefit from that Accessibility feature may not know that they need it, or think of themselves as having the specific impairments that would lead them to explore the Accessibility settings
- Therefore, those folks might only explore the settings that are grouped by the specific aspect of their device’s operation
So, for example, if I’m finding that I’m missing some alert that’s supposed to be triggering the system bell, I might go look at the Sound section to see if I maybe need to pick a different sound or crank up the volume somehow - not realizing that there’s also the option in Accessibility for a visual bell. If there were an option for a visual bell in the Sound settings as well, perhaps that would help? (I think that analogy would extend for most things, like shaking the cursor and the Mouse section, etc.)
KDE Plasma doesn’t have an overwhelming number of different options crammed into Accessibility or anything, but I was still wondering if it might make sense to either show possibly helpful settings within other settings modules, or at least make reference to them (in my example above, maybe even a small banner or context help popup on the Sound page that says “Having trouble hearing the system bell? A visual bell is available in the Accessibility settings panel!”)
If this is a worthwhile idea I’d be happy to try to figure out how to make it work - if it’s not really relevant then please feel free to ignore. Thanks!