Discussion
@svavar @klikini we intentionally have gotten rid of a segregated “accessibility” section because our user research showed people won’t use those features because “those are for disabled people and I’m not disabled”. Especially for things like color deficiency which mostly affects men.
When we put these features right alongside other settings more people discover and use them
@danirabbit @svavar @klikini Were it me designing the system, I'd have a dedicated Accessibility & Affordances preference section, that collects every affordance in one place, that are ALSO distributed in the settings of every feature they effect.
I might even call the preference section "Accessibility", but call each setting in it "Affordance", so in Appearance -> Colour Vision Affordance.
It is not a Designer's job to say "No", it is a Designer's job to provide the enablement of "Yes".
@metaning good thing you’re not designing the system I guess
@danirabbit Well, I think the global hierarchical menubar is the most important UI invention and paradigm in the history of computing, so nice as Elementary is, it's probably never going to be for me. Though, "Affordance" is usually the term used for accessibility options when dealing with the physical world, if the term is problematic?
You obviously have the data from your users, though.
@danirabbit @svavar I see...could the settings appear in both places so people who are in denial about having a disability can discover them and use them, while people who accept that they have a disability can still find them where they're expecting them to be? The latter bit seems especially important for people who will have difficulty navigating the UI until they find the setting(s) they're looking for!
@klikini we haven’t had a segregated accessibility section for years, this change happened a long time ago. You can always use search if you’re having trouble locating certain settings as well
Install bonfire.cafe
Get the full app experience
