When using @MonaApp with #VoiceOver, is it possible to share an image attached to a post with another app? When I use the "view media" rotor action, and then triple-tap on what VoiceOver claims is the image, I get sharing options related to the alt text, or detected text, or something, but not the image itself. In the end I had to take a screenshot of the image and use that instead.
If you are #blind and you have been locked out of being able to use your InstantPot after the inaccessible app update, please email support@instantpot.com and refer to Case 02284154 asking that they restore #VoiceOver#accessibility to their #iOS app.
I just realized that if you're formatting to an abbreviated weekday then VoiceOver (at least Ava and Zoe Premium) will only fully pronounce some of the days.
I guess it's because the ones that aren't pronounced are actual words with other meanings? 🤔
Text(oneShowDay.formatted(.dateTime.weekday(.abbreviated)))
I've just pushed a bunch of #accessibility changes for screen readers to the main branch of FediThready. ( It makes long texts into post sized chunks)
I've run through it with #VoiceOver and it seems ok. HOWEVER it all feels like it's "usable" instead of "good".
If there's a #a11y geek out there who uses screen readers regularly I would REALLY appreciate some suggestions on how to make this actually feel good for folks who rely on screen readers.
This tech could have revolutionized the voice-over industry in the 90's... but instead it was lost to time. Hear Al Lowe talk about Sierra On-Line's secret in-house studio weapon: https://youtu.be/oOZhpcJIyd8
It's June 10, 2024, at 4:00 PM Central US time. Almost every blind person that owns an iPhone has installed the iOS 18 beta. Some are playing retro games with the new, AI driven screen recognition. Others are gladly using DecTalk as their main voice, the Enhanced Siri voices that use ML to speak using emotion and context, as their reading voice, Eloquence as their notification voice (sent to one ear to minimize distractions), and finding it amazing that VoiceOver emphasizes italic text, and emboldens bold text. Others are finding it amazing that they can navigate their whole phone using Braille screen input, searching to find things by typing a few letters, or just swiping down through everything. A few are connecting their multi-line Braille displays, and feeling app icons and images, made much more understandable through touch, using an AI filter.
The next day, when news of all these features filters down to Android users, they quickly begin hammering Google, wanting DecTalk and Eloquence on their Pixel phones, like iOS users have. But Google is silent as always, only just now having given Chromebook users high quality Google TTS voices.
Note: great liberty has been taken to imagine the coolest outcome for the vague feature announcements Apple gave for VoiceOver users. We'll see just how cool, or not, they actually are on June 10.
If you were wondering whether the new #Sonos app is as bad with #VoiceOver as people said, I can confirm that it is.
The first element that receives focus has no #accessible role or name, i.e. VoiceOver doesn't announce anything for it. The screen is split up into sections, like "Recently Played", "Your Services", and "Sonos Favourites", but none of these have headings. And, as previously noted, explore by touch doesn't work; VO seems to just see that blank element I mentioned as being stretched across the entire screen.
As a result of all this, the "Search" button requires 32 swipes from the top of the screen to reach, at least with my setup. If you have more services and/or more favourites, that number of swipes will be higher. #accessibility
Actors: If you’re an American or have American friends/colleagues and family, encourage them (and I encourage you) to contact your representative and both your senators and tell them your needs in regards to the No Fakes Act: https://www.congress.gov/event/118th-congress/senate-event/335702
Looking for a voice actor/narrator for an audiobook production. I need a woman with a low voice and a US accent. This is a paid project. No audio editing needed. I've got a team for that already.
You can find my email in the weblink in my bio to get in touch!
Sometimes, you might think that previous #accessibility wisdom has been superseded by new "facts". Maybe someone told you that #screenReaders don't work well with a particular design pattern, but you tested #ScreenReader X and it seemed to work fine. Perhaps you heard that an interactive HTML input doesn't persist with forced colours styling, but you tried a High Contrast mode in Microsoft Edge and it seemed to be there.
There are three considerations usually missing here:
How are you defining and evaluating the working state? Do you have a functional, accurate understanding of the #accessTechnology or accessibility feature you are asserting things about?
You tested one thing in relation to a statement about multiple things, e.g. a statement is made about screen readers, plural, and you only tested with #VoiceOver (it's always VoiceOver). Beyond posting on the web-a11y Slack, how do you propose testing more broadly, if you plan to at all?
Possibly the most critical at all: is this question worth its overheads? If answering it conclusively would require me to test ten screen readers with 45 speech engines, or seven browsers with 52 permutations of CSS properties, maybe following the advice is "cheaper" than determining whether the advice is still completely relevant.
Important disclaimer: this relates specifically to cases where following the advice would not actively make things worse for users.
TL;DR: when you know doing a thing won't make things bad, doing the thing is usually quicker than evaluating whether not doing the thing is also bad.
New blog post! Free #accessibility consulting for #tidal! #music recommendations from yours truly! #ScreenReader testing! Click here and find out how #NVDA clearly wins this iteration of the series:
Hi dear #iOS users! I have a Health widget on my home screen. Is there a way to make it show steps instead of calories, percentage and what not, or it will be reason number 7001 why I don't like Apple's policies? And if it's the later, please suggest a #VoiceOver accessible app for that? Thanks!
It's April, people are already talking about WWDC and looking forward to IOS 18.
IOS 17.5 beta has dropped and fixes for serious issues with VoiceOver's Hebrew text to speech, introduced in IOS 17 have not been addressed by Apple.
I'm a fan of IOS devices and their commitment to accessibility.
However, when half a year after introducing a but that causes the Hebrew TTS to say a long string of gibberish (xb7xd78), every time it encounters an apostrophe is making doubt Apple's commitment to it's users outside the US.
Sounds like J or ch are written using a Hebrew letter plus an apostrophe. So every time VoiceOver sees teh word Chat it says C-xb7xd78-ats.
The blind IOS community here as distributed a custom punctuation pronunciation file that helps by telling VoiceOver not to pronounce apostrophes, but this still causes such word's to be mispronounced. Tsats instead of Chats, but at least it's bearable.
I don't think such a glaring bug would have been ignored by Apple if it happened in English.
I got into control center (the little swipe down quick control thing on iOS) with VoiceOver on, and now I can't pop my way out of it, because there's nothing to navigate to, to dismiss... is this an apple bug, or is there a way to back out I don't know? #VoiceOver#iOS#a11y
A VoiceOver user reached out to me because they had trouble finding their saved favorites.
In trying to think of ways to address this I realized that there's a ton of unused space before you start searching for a new location that would be perfect for showing your saved favorites.
How did I not think of this before?
I'll also be making tweaks to the main UI to point out that favorites are available.
Nutzt hier jemand auch #mona mit #voiceover und kann mir sagen, wie ich verhindere, dass ich auf den falschen Beitrag antworte? In letzter Zeit passiert es mir oft, dass VO einen Beitrag ansagt, die Interaktion jedoch zwei oder drei Beiträge darüber stattfindet. Führt manchmal echt zu Verwirrung und unnötiger Mehr-Arbeit. ^^
We’ve covered the epic HeardThat app on the show before, assisting people to hear in noisy environments, and we’ll be evaluating their new external microphone solution shortly. They’ve just released an iOS update, and while the app was useable with #VoiceOver before, it’s fully accessible now. Thanks to them for their interest and responsiveness.
VoiceOver question - if I hear “scroll area, content is empty” does that mean that area is not accessible? I assume so but I don’t want to judge until I’m sure there’s no way to navigate into the area.
@JenMsft I found a long-standing bug in #MicrosoftEdge on #Ios. when using #Voiceover, the items in the open tab list are not spoken. It just says, “Draggable.” Only after I open it, will voiceover tell me what it is. This bug is present on my #iPhone13ProMax running #ios17.4. Would you be willing to look into this & ensure its resolution? I sent feedback about it through the app.