SUMMARY Entries in system settings usually have a ">" icon to indicate that clicking on this entry will reveal more tabbed entries. Like Mouse & Touchpad or Keyboard. The Accessibility Entry does not have such icon, despite clicking it leading to more subentries. STEPS TO REPRODUCE 1. Open System settings 2. Observe OBSERVED RESULT Accessibility doesn't have an ">" icon EXPECTED RESULT Accessibility should have an ">" icon SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 Kernel Version: 6.11.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B450M DS3H
Can confirm
Technically this is correct as is, because clicking on thje "Accessibility" list item takes you to a single page, not a group of pages. However on a practical level, I can appreciate that the result sure *looks* like a group of pages, because it has a sidebar that you use to select pages. However technically speaking the sidebar selector that gives you this impression is implemented entirely within the base Accessibility page, and does not use the System Settings' app's own grouping mechanism. This is because we explicitly don't want to use it; we want this page to be exposed to the user as one page, with the view switcher being an internal implementation detail. We don't want it to be exposed as like 7 pages. I see three options here: 1. Say it's intentional and close the bug on these technical grounds 2. Say it's intentional but admit that the lack of an arrow is a bit odd, and work on a way to let this and similar pages manually opt into showing an arrow 3. Re-think grouping on the page, and split this KCM into like 8, and use the standard grouping mechanism. --- Disadvantage of #1 is that it's unsatisfying and will feel rude to the bug reporter and anyone else who brings this up. Disadvantage of #2 is that it will require more technical work to re-implement something we already have for pages using the standard system. Disadvantage of #3 is that we'll lose the ability to show a single base "Accessibility" page we can easily direct people to.
It may be worth noting, that the only reason why I discovered this in the first place, is that I tried to reduce the settings' window width. If you normally do that in these nested-groups, the contents readjusts, where it only shows [middle sub list | detailed setting], where as with accessibility it shows [left main list | middle sub list | detailed setting]
*** Bug 494400 has been marked as a duplicate of this bug. ***