Mindly.Social

0 posts0 participants0 posts today

Robin Frost Has MovedRe: Last boosted post "floating widgets" sounds like just what the world and especially <a href="https://mastodon.social/tags/ScreenReaderUsers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ScreenReaderUsers</a> for the <a href="https://mastodon.social/tags/Blind" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Blind</a> need.

Anshuquestion for screen reader users. I'm reading an article about optimizing web for accessibility, and it says that alt texts should not be long, optimally less than 100 characters because NVDA reads alt text in those batches, and JAWS reads all at once which is overwhelming if the text is too long. your opinion on that?<a href="https://pounced-on.me/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accessibility</a> <a href="https://pounced-on.me/tags/screenreaderusers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#screenreaderusers</a>

IrenerdQuestion for blind and low vision people and other users of screen readers: what are the main obstacles you encounter when browsing the web? That is, the things that you would like those of us who are in charge of them, to fix.Please boost <a href="https://col.social/tags/accesibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accesibility</a> <a href="https://col.social/tags/screenreaderusers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#screenreaderusers</a> <a href="https://col.social/tags/jaws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jaws</a> <a href="https://col.social/tags/NVDA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NVDA</a>

Osamu<a href="https://mindly.social/tags/camelCase" class="mention hashtag" rel="tag">#camelCase</a>, <a href="https://mindly.social/tags/PascalCase" class="mention hashtag" rel="tag">#PascalCase</a> or <a href="https://mindly.social/tags/snake_case" class="mention hashtag" rel="tag">#snake_case</a> for <a href="https://mindly.social/tags/screenReaderUsers" class="mention hashtag" rel="tag">#screenReaderUsers</a>?

CassanaAfter answering many questions on <a href="https://pagan.plus/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accessibility</a> and <a href="https://pagan.plus/tags/screenreaders" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#screenreaders</a> used by <a href="https://pagan.plus/tags/blind" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blind</a>, <a href="https://pagan.plus/tags/LowVision" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LowVision</a>, <a href="https://pagan.plus/tags/PartiallySighted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PartiallySighted</a>, <a href="https://pagan.plus/tags/VisuallyImpaired" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VisuallyImpaired</a> people, I think it would be good to summarise them in their refined forms in one spot for easy reference. 1. Writing well as a general advice stands, however, I wrote my post in English and naturally included some points specific to English. Screen readers are programmed to work best with languages according to their spelling conventions regarding capitalisation, punctuation, and symbol usage; covering anything from casual to academic writing styles. Substituting letters with symbols/numbers falls outside of such conventions, meaning words will not read correctly. 2. <a href="https://pagan.plus/tags/AltText" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AltText</a>, and the time it takes to write them, is very much appreciated, regardless of length or level of detail. However, the more detail you can put in the more we can appreciate the image and your reasons for sharing it. 3. Multi-word hashtags in CamelCase, yes: <a href="https://pagan.plus/tags/ThisIsWhatAnAccessibleHashtagLooksLike" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ThisIsWhatAnAccessibleHashtagLooksLike</a>. It does not matter where you place them; either in the post's text or at the end. The best analogy for screen reader users being able to deal with hashtags in text is that we've become used to them in the same way we're used to people saying "uh", "ummm", or other extraneous vocalisations when talking. Bonus: By all means, use emojis for that extra bit of expression, but in moderation. Final thoughts: Screen readers can be customised by the user to make it work best for them, including minimising any annoyances. The above points will help loads regarding shared content. Assume that a screen reader user has optimised their settings to deal with the rest. Once again, thanks for reading! 😘 <a href="https://pagan.plus/tags/FediTips" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediTips</a> <a href="https://pagan.plus/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a> <a href="https://pagan.plus/tags/ScreenReaderUsers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ScreenReaderUsers</a> <a href="https://pagan.plus/tags/inclusivity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#inclusivity</a> <a href="https://pagan.plus/tags/community" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#community</a>

Recent searches

Search options

Administered by:

Server stats:

#screenreaderusers