If you have a disability and self-host (or want to): what is actually missing?
I build free Android apps for Nextcloud, and the longer I do it the more obvious it gets that accessibility is something I check at the end, if at all. I suspect that is true for a lot of this community. We optimize for privacy and control, and then ship something that only works if you can see it, tap precisely, and read fast.
So I would rather ask than guess.
If you use a screen reader, switch control, voice input, magnification, or anything else, I am curious about:
- Where does self-hosting break down for you right now? Setup, the web UI, the mobile clients, the docs, something else?
- Which big tech service do you keep because nothing self-hosted replaces it accessibly? Be specific if you can.
- What would make a self-hosted app usable where a mainstream one currently wins? Proper labels, bigger touch targets, keyboard-only flows, sensible focus order, offline voice input, something I have not thought of?
- What do people like me get wrong when we say an app is "accessible"?
I am not selling anything and there is nothing to sign up for. My apps are free and open source and will stay that way. I am asking because concrete feedback is worth more than another accessibility checklist, and because if a few of us act on what comes out of this thread it is a better use of a weekend than another theme toggle.
If you would rather not post publicly, a DM is fine.
PS: Do not downvote because you feel like accessibility is not for you. I am not looking for profits. I genuinely want to help people that want to make use of technology but something is missing for them to make the jump to selfhost.