liqd / adhocracy4

The core library for the e-participation projects by Liquid Democracy
https://liqd.net/software
GNU Affero General Public License v3.0
100 stars 16 forks source link

Ratings: unify `voting/like` terminology across aplus & mB #1673

Open hom3mad3 opened 2 months ago

hom3mad3 commented 2 months ago

Description:

There is a mismatch in terminology and display requirements between the aplus and mB projects, it was brought up here https://github.com/liqd/adhocracy4/pull/1669#discussion_r1724784354

aplus: Uses "vote" terminology without displaying text, relying on hidden messages for screen readers. mB: Uses "like" terminology and requires visible "Likes/Dislikes" text.

Proposed Action

Unify the approach by displaying text on both platforms or use same wording for the screen reader option Use CSS to hide or show the respectives text as needed per platform, reducing complexity and avoiding custom logic.

mB aplus
rating-mb ratings-aplus

Participants:

@goapunk @hom3mad3 @TeaJayyy @CarolingerSeilchenspringer

CarolingerSeilchenspringer commented 2 months ago

@hom3mad3 @goapunk @TeaJayyy sounds plausible. I would argue for "like/dislike" as in mB we have voting as another feature. The question to me is if we want to stick to the current design in a+ or also change to the like/dislike from mB. I add @MarleyMi with the questions if we have some insights from the a+ usertesting regarding the rating.

hom3mad3 commented 2 months ago

@hom3mad3 @goapunk @TeaJayyy sounds plausible. I would argue for "like/dislike" as in mB we have voting as another feature. The question to me is if we want to stick to the current design in a+ or also change to the like/dislike from mB. I add @MarleyMi with the questions if we have some insights from the a+ usertesting regarding the rating.

if we decide to have a more complex element with different wording, then would make sense to refactor the ratings component to account for different use cases

CarolingerSeilchenspringer commented 2 months ago

@hom3mad3 @TeaJayyy I think we should have the same wording for our core features throughout our platforms. Makes not only development easier but also PM/PR work.

TeaJayyy commented 2 months ago

@hom3mad3 @CarolingerSeilchenspringer I also prefer the like/dislike option although, generally speaking, I visioned a "support" functionality, without dislikes. For the moment having like/dislike is a good start and using the thumbs is more clear than arrows. Design-wise I agree that a+ and mb should be closer together regarding their core features. The main problem is that I'm not sure when we can tackle this due to budget constraints for a+.