Server admins!
If you're creating custom emoji, remember to fill in the section marked "Shortcode" with a short text description of the emoji. Blind people's screen reader software will be able to read the shortcode aloud so that they can hear what the emoji is.
If the emoji's shortcode includes multiple words, split them up with underscores like_this or CamelCase, so that screen readers will be able to read each word correctly.
It shouldn't be doing that if you're on a current version of Mastodon.
Older versions of Mastodon did this automatically, but current versions should keep whatever case you used in the hashtag.
Does your Friendica server have this bug?
I'm using the web interface and the "hint" hashtag often has no-caps, but my CamelCase hashtag stays CamelCase when I post.
I think you are right about people not using CamelCase being the reason, but I figure the more I use it, the sooner the hints will be CamelCase too.
@feditips Are underscores preferred over camel case to separate words for screen readers or there is no difference?
There's no difference as far as I know.
(However, hashtags on Mastodon can only use CamelCase, so underscores won't work if you're making hashtags.)
I thought #Hash_tags_with_under_scores works on Mastodon. I'm not sure how they work with #screenReaders.
Edit: add screenshot
@SmartmanApps @feditips @gytis
Here's a couple old underscore tags that are populated
#TheReasonIDislike____is____
#____Needs____Because
I wonder how it sounds in #ScreenReaders
Interesting, I did NOT know that underscore works on hashtags on Mastodon! TIL!
Smartman, there are a few results for those tags on mstdn.social, it's possible that your server hasn't noticed these posts yet. But if you post using those tags with a public visibility setting you should be able to find them on your server too.
@feditips @SmartmanApps @gytis
@trendytoots has one of them trending on July 27th on Mastodon Social.
@feditips @SmartmanApps @paul @gytis This is my biggest problem with Mastodon. The whole point of hashtags, is to get around the problem with text search (which, it turns out is identical with hashtags) - you only ever see things.... if you (or your server) already knew about them. We desperately need an actual, Mastodon-wide search
I'm guessing multiple underscores is not a good idea? But I could be wrong?
Hey @weirdwriter how does the hashtag #TheReasonIDislike____is____ sound in your screen reader? Does it repeat the underscores that are next to each other?
@paul @SmartmanApps @feditips @gytis With #NVDA, it depends on the punctuation level (how much punctuation you have NVDA set to read aloud). At "Some", it reads "The Reason I Dislike Is" & "Needs Because". At "Most", it reads "The Reason I Dislike Four Line Is Four Line" & "Four Line Needs Four Line Because". It's not our product, but I just tried Narrator for you; out of the box it reads "TheReasonIDislikeUnderscoreUnderscoreUnderscoreUnderscoreIsUnderscoreUnderscoreUnderscoreUnderscore"
Having touch-typed since I was 17 (a "couple" of years ago), I actually prefer using the shortcode instead of stopping to click on the emoji and find the icon.
this is :slight + Enter
This is :heart + Enter
Much faster!
Yes, you can type emoji on Mastodon using colon and the name of the shortcode.