[FEATURE] Congrats message

[YuriDevAT]

[FEATURE] Congrats message

[CorinaMurg]

I am working on the alphabetical sorting of the list, and one idea is for each group of tags to be a bit on its own. Visually it would be easier to look up the group starting with a certain letter. We could also mark (and let the screen reader announce) the completion of a group. And the ellipsis (...) could indicate that a group is not yet completed.
A very simplistic design to illustrate this (it was done in Excel!):

This could take care of letting users know when they completed one group.
We don't need to have the heading with the group's letter, but at least a gap between each group.

And then of course, announce 50% and 100% completion.
We could also add a countdown when there are only 10 or just 3 left to submit.

[YuriDevAT]

Great idea! This makes it easier to follow the progress.

[CorinaMurg]

@YuriDevAT
Do you think this is ready to move forward? By this I mean define the issue more clearly and implement it? I think I was waiting for us to have a UI design ready, but now I realize that the JS parts of this issue could be implemented regardless of the design.

[YuriDevAT]

Yeah of course. The content of the message can be separated from the design, I would say. This issue is more about deciding how many messages will there be and what they are going say.

[CorinaMurg]

@YuriDevAT
Right now we have an ariaMessage that updates with each new added tag, so a screen reader user will hear "23 added" etc.
This changes to a congrats message at 50% and 100% completion.

Do we want this info displayed also on screen? Not sure if it's necessary since we have the progress bar, but it would be more specific than the progress bar, which some users might prefer.

Not sure what would be best.
Then the other option is to keep it the way it is, and just add the congrats messages, just as we planned with this issue.

[YuriDevAT]

Yes @CorinaMurg , my suggestion would be as I added it into the design, having the progress showing as a number as well.

Depending on the effort it takes, I would have implemented it with my styles PR already. If it takes more, a new issue for this would be the better choice I guess.