@FediTips It depends on the fedi client actually, but it's up to the client not the screen reader itself. If the client truncates the link as displayed visually, E.G> with an elipsis, then the screen reader should probably also see that and truncate. But if the text of the link is displayed in full, then the screen reader will read it in full. The client I'm using actually speaks directly through the screen reader and thus also has it spoken fully, it's a client designed specifically for blind users. In sum, if it's displayed visually in full, that text is given to the screen reader, and thus it's going to read it in full too, as it will act based on what it is given with minimal transformation for just blocks of text. Transformation comes into play for complex elements like those in HTML, E.G. speaking the word link before reading out the name of a link, but text is text and unless the app goes out of its way to expose something different to the screen reader than what is shown, which is platform, screen reader and framework ddependent, what you see is ideally what you get in terms of text.
=> More informations about this toot | View the thread | More toots from x0@dragonscave.space
=> View FediTips@social.growyourown.services profile
text/geminiThis content has been proxied by September (3851b).