A lot of blind and partially-sighted people use the Fediverse through screen readers, apps that read on-screen text aloud.
Long strings of emoji can cause problems for screen readers, because they take a long time to say out loud. They can't be skipped because it is impossible for apps to know when emoji contain useful information.
If you want to make life easier for screen reader users, use just one emoji at a time.
For example, 😄 is fine but 🙂 😋 😚 😆 😄 😞 👍 causes difficulties.
If you're an instance owner, please make sure your emoji use text descriptions (alt text, shortcodes) that are descriptive and suitable for screenreaders.
For example, "SmilingCat" or "smiling_cat" will work great, but "smilingcat" may cause problems because the screen reader will not know where to put the space.
Apparently, the situation is that it uses whichever capitalisation was used first, rather than favouring lower case.
If CamelCase was used first, it would correct to that.
Obviously CamelCase should be preferred, but I am not a developer so not sure how easy this would be to fix?
Workaround for this is to press space (and *not* enter) after you have written the hashtag, this keeps the hashtag as-is and closes the suggestion box.
Couldn't find any existing issue, so I have opened an issue for this. Please give it a thumbs up if you want this fixed:
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!