Ratings: unify voting/like terminology across aplus & mB

[hom3mad3]

Description:

There is a mismatch in terminology and display requirements between the aplus and mB projects, it was brought up here #1669 (comment)

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

Participants:

@goapunk
@hom3mad3
@TeaJayyy
@CarolingerSeilchenspringer

[CarolingerSeilchenspringer]

@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]

@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]

@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.

[t-j-q]

@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+.