Plural accessibility in voice and text

(#947) Feature Open: Under consideration accessibility profiles

Thread

Comment by @chiaracoetzee
RexSystem 1 vote edited originally by @chiaracoetzee on GitHub 1 reply
Per my comment above I have a prototype of this feature up at https://github.com/chiaracoetzee/fluxer-subprofiles/tree/features/subprofiles based on @haileyscommit's design and it's working well on our home server. It's web/desktop client only not mobile right now. Would need a lot more prep before submitting a proper PR. Supports both GUI subprofile selection and PluralKit-style prefixes, and can import a system from a PluralKit JSON export dump. Tested with a large imported system with 60+ members. Some screenshots below for reference. image image image
Comment by Speykious
Speykious 1 vote originally by @Speykious on GitHub
Looks pretty good from the screenshot! Just a few things about design:
  • I'd ensure that the Import from PluralKit and Add Subprofile buttons look like the rest of the buttons on the platform; right now the icon is above the text instead of on its left. The rounding is also off. Looking at your PluralKit modal commit, it looks like you used plain HTML <button>s, it would be better to use Fluxer's own Button (fluxer_app/src/features/ui/button/Button.tsx) component instead. Same for the other buttons if you did it that way there too.
  • I'd slightly increase the width of the subprofile switching modal in the second screen so that Last Used doesn't span two lines of text.
Also, I think the vocabulary is a bit inconsistent. In one place we're talking abut "subprofiles", in another it's "personas", and in another it's "subprofiles & personas". I think it should just be "subprofiles", it's the most neutral word that corresponds to the broadest application of this feature imo.