Question for blind and low vision people and other users of screen readers:

what are the main obstacles they encounter when browsing the web? That is, the things that they would like those of us who are in charge of them, to fix.

Please boost

#accesibility #screenreaderusers #jaws #NVDA

Any #ScreenReaderUsers attempted to do any of the #LinkedInLearning courses? Thought that I would mention that I gave the “What is Power Automate” a go. I was quite happy that I got through the first chapter with surprising ease. Given that it was a Video course, I expected less.

@nellie_m @devinprater Hashtags at the end are preferred, at least for me personally, but if there are only a small number of them it doesn't bother me to see them in the text.
Please also note the tips about casing your hashtags from above to enable #ScreenReaderUsers (initial cased hashtag for example) to understand their meaning correctly.
it depends on the individual reader and their disability IMO.
Almost more important than the answer though is the fact that you asked. Thank you very much. #Accessibility #A11Y #Inclusion

#ScreenreaderUsers , I'm using the #Pinafore web client on Safari and I like the experience so far. However, I'm finding that using the keyboard shortcuts "J" and "K" cycle through a series of toots with no end in sight, unless I press "period" to scroll to the top to read my last unread toot. Is there any way of knowing when I've read the last unread toot? Has anyone else experienced this? If not, what should I be doing instead?

#ScreenreaderUsers , I'm using the #Pinafore web client on Safari and I like the experience so far. However, I'm finding that using the keyboard shortcuts "J" and "K" cycles through a series of toots with no end in sight, unless I press "period" to scroll to the top to read my last unread toot. Is there any way of knowing when I've read the last unread toot? Has anyone else experienced this? If not, what should I be doing instead?

#camelCase, #PascalCase or #snake_case for #screenReaderUsers?

After answering many questions on #accessibility and #screenreaders used by #blind, #LowVision, #PartiallySighted, #VisuallyImpaired 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. #AltText, 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: #ThisIsWhatAnAccessibleHashtagLooksLike. 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! 😘
#FediTips #Mastodon #ScreenReaderUsers #inclusivity #community

Just realised my OP asking about #MathJax implementation with VLEs and the experience of #screenreaderusers with that option may be of interest to the #mathstodon hashtag gang. Anyone got any experience with mathjax and blackboard VLE? Trying to gauge if CDN or own installation is a better route, or just generally gather info in how it works with VLEs. Already had some great help, but anyone wiling/able to chip in welcome and appreciated!

A few accessibility tips:

- use alt text on your media!
@alt_text or @PleaseCaption can remind you about this.

- hashtags at the bottom are more friendly for screen readers

- use case to help screen readers understand hashtags

#MastodonTips
#ScreenReaderUsers

@bjmendelson

@niamhpage like #ScreenReaderUsers, or some other capitalisation?

Question for #ScreenReaderUsers: If I say something like "emoji art follows" is it easy to skip the rest of the post with your #ScreenReader?

I'm specifically thinking about doing those wordle result posts where it's already behind a CW and I can start with the written description but it would also be fun to add the emoji representation after that. Would it be better to split it into a separate post that specifies the overuse of emoji in the CW text?

Question for #ScreenReaderUsers: If I say something like "emoji art follows" is it easy to skip the rest of the post with your #ScreenReader?

I'm specifically thinking about doing those wordle result posts where it's already behind a CW and I can start with the written description but it would also be fun to add the emoji representation after that. Would it be better to split it into a separate post that specifies the overuse of emoji in the CW text?