Just found this article stating that using the #language #attribute for individual words within a text is not a good idea when you want #ScreenReader users to have a good #UX. It's just overengineered #a11y.
I'm a bit surprised as you always read otherwise (as the article also mentions).
Are some screen reader users here that can share their experiences? I'm really curious now 
@dnikub Yes, I agree with Domingos. Kerstin Probiesch has also written an article about this, although this also heavily emphasizes the case in PDF documents. The problem is that, for the screen reader to switch the language, one voice has to stop mid sentence, switch the voice to one that speaks the other language, speak the word or phrase, then switch back, which can take half a second each. It ruins the whole sentence melody, sounds as if you were to take a breath in mid sentence, disconnecting the words in a very unnatural manner for no apparent reason. I find it quite annoying if it happens too often. I tend to switch off language switching for that reason. Full sentences or paragraphs are no issue, single words in a sentence quickly become a huge annoyance.
@tajpulo @Marco @dnikub Because “the screenreader” is not a singular piece of software. “The screen reader” works on top of the browser, and then uses the user’s preferred language to do the speech output. Common words are incorporated into the languages, for example no German language struggles with the word ”computer”, but good languages are already large. There are many considerations and it’s not “just do this to fix it”.
