IOS 26 is going to make it possible to add ringtones using the share sheet. Tech sites are not hyping this up enough because you still have to create the ringtone, but I know lots of us know how to do that already and just need the easy way to add it to our phone without going through iTunes. And now, approximately 14 years after Apple supposedly untethered the iPhone from the computer, we have it. So now if you go to one of those ringtone sites, or someone texts you an audio file, or you’re handy with Hokusai or some other audio editor for the iPhone, you can make your own ringtones without a billion steps. Like everything else Apple has done in recently years, it’s taken so long for such a basic feature to arrive that it’s hard for me to even be excited about it, but I sure won’t miss blundering my way through iMazing.
@talon Why do you regret a post like that? It is completely correct.
@acidiclight If you do, I'd be happy to help in drafting a protocol.
@acidiclight Talkback just makes a sound. I like this approach though because it doesn't have to be in something that identifies itself properly as a text field. I could be typing in a dialog that doesn't properly identify a text box, or an inaccessible part of an app and still catch my typos.
@BTyson @lexipic @Kaliah I'm not sure. I don't have it installed. I do remember it being the case you could have the mouse drop into a different window and then continue the lesson without you being aware, however now I think about it that might have been down to something my TVI did rather than the program. I'd have to install it again and double-check.
@acidiclight I also have a spell checker which plays a sound if I typo a word, and that applies across applications. It's essentially a key loger.
@acidiclight I tend to just navigate the field with arrows, or use the read current line command. Like for this post, I pressed the up arrow key to review the first line, then down to review the next, and so on.
@acidiclight <rant> I hate Wayland for this kind of crap. It was designed with absolutely no thought put into the structure of accessibility, and like everything else, accessibility feels like a bolt-on. I will not use a Wayland desktop in production at any point. I simply cannot do so, the tools I need to have an efficient workflow cannot exist under Wayland. </rant>
@acidiclight Oh, I see your problem. Yeah, usually people that have any form of typing echo on have the speech fast, or just pause after each word to hear what was said. Sentence echo rather than word echo might be better. You would still have to pause, but not after each word. I have all typing echo off.
@acidiclight You can't, because Wayland.
a new thing we're about to launch: a self-service support center where you can get step-by-step interactive troubleshooting guides to solve common problems, or enter the required data for common support issues in a structured way. the engine for this was custom developed by @ailurux. some illustrations by @holo_memory
@acidiclight Hm. that really shouldn't happen. Yes, it will interrupt, but if you're not sending speech start and speech stop events really fast then I can't see how it breaks. What speech synthesizer are you using?
@puppygirlhornypost2 It made a lot of sense for phones and tablets.
@acidiclight Usually the screen reader just draws the focus pointer over the element that has keyboard focus. I'm not sure if it works the same or differently under xorg. I've never asked someone to look. Yeah, the settings UI could really use an update, but it's fully accessible and things are placed in sensible places.
@Kaliah Just tried. discord launches fine. Maybe try uninstalling and reinstalling?
@acidiclight Understandable. It's probably best to navigate the way I outlined for accessibility testing. I'm surprised Orca doesn't have a visual indication of where the browse mode cursor is though, I think all other screen readers do this.