https://bugs.kde.org/show_bug.cgi?id=494469
cwo <cwo....@posteo.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cwo....@posteo.net
--- Comment #5 from cwo <cwo....@posteo.net> ---
(In reply to Nate Graham from comment #2)
> I see three options here: [...]
> 3. Re-think grouping on the page, and split this KCM into like 8, and use
> the standard grouping mechanism. [...]
> Disadvantage of #3 is that we'll lose the ability to show a single base
> "Accessibility" page we can easily direct people to.
I have a different related proposal:
- Merge some of the groups where the separation is somewhat arbitary in the
first place. Modifier Keys, Keyboard Filters, and Activation Shortcuts (which
gives a way to enable/disable the features of the first two) could be one
entry, "Keyboard Accessibility" (or similar). Mouse Navigation and Shake Cursor
could be something like "Mouse Accessibility". Color Blindness Correction and
the Zoom page once it lands could be part of a "Display Accessibility" page.
- Make this much smaller number of pages individual kcms in the Accessibility
group with the regular grouping mechanism, rather than one kcm. That solves
this issue and makes the pages more accessible through search.
- Create a proper Accessibility landing page as the entry point for all
accessibility-related things. This would work similar to kcm_landingpage, with
a very restricted number of toggles (Enable Screen Reader could go here maybe),
and a list of curated links to other kcms, including the others in the
Accessibility group but not restricted to them. A fair number of open feature
requests are about things that are relevant to accessibility, but configured
elsewhere (Screen scaling and font size, pointer speed, keyboard repeat
rate...). We can mostly centralize this on the landing page (with maybe an
occasional cross-kcm link on the individual accessibility kcms).
--
You are receiving this mail because:
You are watching all bug changes.
