@feditips@paul@SmartmanApps@gytis On iOS, voiceover doesn’t have a problem with underscores at the end of hashtags, but underscores in the middle of hashtags is extremely verbose and very hard to listen to. I can’t even understand what your hashtag was above earlier in the thread. While I personally won’t follow hashtags with under scores, under scores at the end appear to be OK on iOS because voiceover will just truncate how many underscores there are so it’ll say like three underscores or nine underscores I haven’t tried it with NVDA on windows yet, but I absolutely would not want underscores in the middle of hashtags. This is what camo case/Pascal case addresses. It’s also just easier to read on mobile devices if you use Pascal case/camelcase. Camelcase it’s where you capitalize every word after the first word. Pascal case capitalizes every word in the #HashtagIncludingTheOneWord. As for underscores and hashtags, while I personally don’t get it, you can still put hashtags with underscores at the end to be the least disruptive. #LikeThis________
July 17 is #AltTextCoverDay, we all know how important alt text is here, but did you know most book covers, including audiobook covers, never have alt text? Next monday, July 17, post the alt text of your books / your favorite book covers!
Reply to this post if blind and low vision folks can DM you for help getting alt text of their fave book covers to post.
@TheVoiceGuy@devinprater@jon I’m saving up for the Optama next year, which is basically a Braille laptop that is modular, with the ability to choose what Braille display you want on the computer. I also don’t think it has a screen either. I haven’t confirmed this, but I actually would love a laptop without a screen. The battery life on that thing would be astronomical! I red on a mailing list that they are looking to make the Bios accessible too! about hymns, I have determined that hymns makes products that have a lot of neat features but they usually do not withstand the test of time. An exception to this rule is the booksense. That one lasted a really long time, and it was a great portable device, but I have never been impressed with him’s latest offerings. On this player, they are running android 11 and I think that was a unfortunate decision, to run an older OS, that will cost them longevity with this
Since we moved to the Fediverse can we all set an autocorrect to change that silly #A11y into #Accessibility? This way, even if you accidentally typed this silly hashtag, it will change into a far better hashtag.
Hoping #NVDA experts can assist. so, I use field codes a lot in my manuscripts, but NVDA keeps reading the field code when it is visually displaying the field result.
I tried a fresh copy and it is fixed, via a portable, well, fresh copy, but for the life of me I can't figure out what setting could be causing this. Anyone got any ideas?
The only add ons I am running are the VLC media player add on.
When I run a fresh copy of NVDA, NVDA correctly reads the field value instead of the field code or part of the field code.
Hey internet friends, can you all try this RSS feed in your reader of choice and tell me if it works? You can delete it afterwards if you want but this is gonna be my backup blog, just in case #Wordpress becomes too difficult to use after/when/if they shut down the classic editor. I still hate the block editor, BTW https://sightlessscribbles.micro.blog/feed.json