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. ^^
My patrons convinced me to give voice acting my new game a try. Like, me voice acting it all by myself. The acting part doesn't really scare me, nor does using the audio in-game.
Recording, editing, naming and iterating on 350 audio files sounds like a huge pain, though. No way I'm doing it manually. Is there an existing free tool for this or do I have to code my own? 🤔
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.
voiceover users, is there a way to make Voiceover stop moving my focus? I'm talking about that thing where when you go to a new screen, it tries to move focus onto an element it shares in common with the previous screen. For example, when I minimize a YT video, it auto-focuses on the mini player. I've lost count of how many times I've intended to watch a new video, only for focus to move back to the mini player mid-gesture. It makes me feel like a tech noob and I hate it. #blind#iphone#apple#voiceover
IPhone users. I have a question. I have noticed a serious bug as of late. Every once in a while, my virtual keyboard will just disappear from the screen. This is the behavor that I would expect when I am actually using an external keyboard. However, this happends when I don’t even have anything hooked up. So, this of course, makes it so that I cannot edit stuff. I have restarted my phone, but the same thing keeps happening. Has anyone else noticed this issue? Any help would be amazing. I’m using an iPhone 14 pro, with the latest iOS. 17.3.1, I believe. #Accessibility#Apple#Iphone#VoiceOver#Blind
iOS Shortcuts. I know some people are interested in learning more about iOS Shortcuts. So I wanted to send out a reminder that, last year, Darcy Burnard, from the Maccessibility podcast, did a 10 part series on understanding and using shortcuts. If you are interested in iOS shortcuts, I would highly recommend checking out this series! You can find it on the ACB Community podcast. You can either join the podcast through your favorite podcast app, or go to the website link at the end. Now there is many different things posted to this podcast feed. But just do a search for Understanding Shorcuts, and this will filter them out. The series ran last year from January 23rd to April 10th. Thanks again to Darcy for putting in the time and doing this series! I personally listen to them through my podcast app, but here is the website link if you want it. https://acb-community.pinecast.co. #iOS#Shortcuts#Tip#UnderstandingShortcuts#Blind#Voiceover@DHSDarcy
Apple Watch and the new widgets introduced in OS 10. The watch widgets are not just a way of scrolling through your watch complications. Watch widgets are totally separate. And in fact, I use widgets as additional complications that I might not access as much. Here is how to add, remove, and work with widgets on your Apple Watch.
To access and scroll through your watch widgets, on your clock face, just flick up until you hear widgets and double tap. A list of your current watch widgets will appear.
You can navigate from widget to widget in 2 ways. By turning the crown, and by swiping from one to another.
Editing watch widgets.
To put your widgets in edit mode, just double tap and hold on any of the widgets. It will bring up your list of widgets in edit mode.
To remove a widget, just flick up on the widget and choose remove while in edit mode.
To add a widget, just choose the add button at the beginning of the list while in edit mode. It will bring up a list of all of the different apps to choose from. Double tap the app you want to add a widget from, and it will bring up a list of available widgets from that app. Just double tap the widget you want to add from that app to add it to your widget list.
To rearrange the order of your widgets.
While in edit mode, go to the widget you want to move. flick up and choose pin. This puts it in arrange mode. Then just double tap and hold on the widget and drag it to the position in the list that you want.
Like I said, I personally use widgets as a way of having additional complications that I can access quickly, but maybe not access them as much. For example, on my watch face I have the complication of the current weather conditions. And as one of my widgets, I have the current days forecast.
I also noticed that the heart widget actually shows your current heart rate, where some face complications do not show this.
I am all about being able to access information easily and quickly. So I really like the new watch widgets, and since they can be totally different than your complications, I think they can be very useful. Great job Apple!
I've gotten into trouble in the past because I didn't realize that making an opacity of zero to hide something didn't hide it from VoiceOver, which would still detect it. Jordi saw me mention that and even made it one of the "gotchas" for the Accessibility part of the SwiftUI Series he did.
I just realized that's not the case any more. VoiceOver is ignoring the element when its opacity is zero without me having to do anything else.
I think that I might’ve spotted a voiceover issue with iPadOS.
My app is for iOS, but obviously you can run it on an iPad. I just realized that when you navigate to several views voiceover does not read what is in the bounding box at the new view.
In this example you can see the bounding box surround the text that says “choose any image to use this theme“ but nothing is spoken.
This doesn’t happen on my iPhone. The text is read as expected.
I am extremely clumsy when it comes to testing things with #VoiceOver for #accessibility, but I do try. I have a question:
Is it possible to completely skip over a table on a web page? I know VoiceOver has options to navigate it, but is there a way (or best practice I can implement) to just skip right past it?
Context: Planning handling accessibility for Chart.js. Planned MVP is to add an accessible description. Potential enhancement is to embed the data as a table.
TIL when you combine a button with other elements using accessibilityElement(children: .combine) SwiftUI will NOT read the button label and will instead use it as the title for the accessibility action. This is useful when there's more than one button but frustrating and a bit unexpected when you only include one button as the action title isn't easily available.
When you run a debug build on your device, does VoiceOver take 10+ seconds to initialize after the app has loaded? I thought it was an issue with my app until I ran a test app with almost nothing and it still took forever.
Finally found the cause of my VoiceOver bug. Apparently adding .ignoresSafeArea(.all) to a color layer BEHIND all the content makes my content not accessible to VoiceOver.
The combination of overlay and background layers is a bit more complicated than that but everything looks correct and if I remove .ignoredSafeArea(.all) it works fine.
But looks what happens with 24 entries and VoiceOver grouping entries together. VoiceOver is just saying "symbol" as if the SF Symbol was not there at all.