Okay, I will say it: I find how #hashtags are being auto-corrected to lowercase in the #mastodon interface really damn annoying.

I *know* what I'm doing when I spell a #LongAnnoyingHashtag in camel case: it's way more readable that way. Why do I have to jump through hoops to have it tooted out like that?..

Suivre

@rysiek hmm here it remembers the casing I used last time and usually proposes it again…

· · Web · 2 · 0 · 0

@mmu_man ah interesting, indeed! That happens. So it's only on the first hash use. That's way better, but it would still be nice for it to not change the case the first time around...

@rysiek
The reason is the caps hashtags are harder for screen readers, it's an accessibility feature.
@mmu_man

@YRthegdnamestkn @mmu_man interesting! I would have thought a CamelCase hashtag is easier to read correctly (consider: #ExpertsExchange vs. #ExpertSexChange). Do you have more context on this to share?

@rysiek @YRthegdnamestkn @mmu_man camel case / medial capitals hashtags are readable by screenreaders; all-lowercase are generally not.

Be kind: use camel case! (See pinned toot if need be.)

@YRthegdnamestkn @rysiek @mmu_man

I was told by screenreader users that CamelCase hashtags are better than all lower case, because it cues the reader to know where to split the words?

@mmu_man @rysiek Casing is stored in the database, first use defines it, admins can fix casing on individual hashtags, benefit is when the more correct casing is suggested to the user typing all-lowercase

@Gargron @mmu_man @rysiek

Think it would be more useful if it just worried about spelling and didn't worry about case?

At least on my posts, 100% of the time it suggests removing CamelCase, I have to keep overriding it.

"casing is stored in the database"

is everything a snowclone opportunity to you, @Gargron
Inscrivez-vous pour prendre part à la conversation
Mastodon G3L

Instance de l'association G3L basée à Valence, Drôme, France