Mastodon: [Accessibility] Screen readers like #HashtagsLikeThis, but the Mastodon UI only offers #hashtagslikethis

[Cassolotl]

Screenshot:

Edit: Gargron said:

I don't think the autosuggest in the OP comes from the database at all, actually. It's localStorage and there is no reason for that to store lowercased tags, you could just store them the way the user typed them before. I think that might be the main bug here.

---

• [x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.

[contraexemplo]

+1. It's incredibly annoying to write hashtags right only to be corrected by Mastodon's UI.

[Cassolotl]

"""corrected""" :D

[mal0ki]

This has been bothering me for a while, yeah.

[ThibG]

Yeah, that has been bothering me as well. Not sure how we could handle it, though. All hashtags stored so far are lowercased. We can't store every capitalization either. We could maybe have the suggestion copy the capitalization for the substring that has already been typed, but it's not really a good fix either.

[Cassolotl]

It sounds like if people want to make a post that is accessible to screen readers they have to do it the long way, taking more effort and risking misspellings and stuff. :/

[Gargron]

Well, the obvious solution is to change the tags index to case-insensitive instead of lowercasing before saving. Then, whatever casing the first use of a hashtag is, it will keep that for all others.

On the other hand, I don't think the autosuggest in the OP comes from the database at all, actually. It's localStorage and there is no reason for that to store lowercased tags, you could just store them the way the user typed them before. I think that might be the main bug here.