screen readers would read

"text, like hash this, does"

Thanks for the feedback, to both of you.

Yeah, I was wondering that. I can imagine arguments for either option being better than the other.

On one hand, I imagine that constant interruptions with the word 'hash' or the word 'hashtag' are annoying, but on the other hand I assumed that it was preferable to the big wall at the end.

However, I also assumed that people would simply skip the narration of the post once they reach a wall of hashtags.
But then again, I can also imagine that sometimes there's content after the wall, so that isn't exactly foolproof and you might end up skipping too much.

I only tested the inbuilt Android screen reader, which prefaced every hashtag symbol as the word "hashtag", but I also imagined other screenreaders simply not reading out hashtags until after the post or upon being specifically prompted.

That's why I wanted to ask to make sure. 😅 It seems like it's a preference thing with no clear answer, so far.

The frustrating thing about all this is that HTML already has features to, for example, distinguish headers and footers from a post's body. Social media just doesn't use it, simply smacking a post's content onto the site in plain text, leaving the screenreader to guess what's going on.

It definitely is the site's responsibility, but writing proper #semanticHTML is unfortunately not a priority.

With any software you expect the end user to merely use the default settings and customise nothing. I try my best to make sure things work for these people, but without being blind myself, it's difficult to test.

As a note on the subject, I always place hashtags at the end of posts. Even for me, a dyslexic throwing them in the main text can make it harder to read.