it is keep on crashing

Accessibility Inspector no longer works with Xcode 13.3. I upgraded to Xcode 13.3.1 but the problem persists. Accessibility Inspector fails to capture the elements by moving on the graphical interface of the simulator.

Hello, In Short: add a way to use the text prediction from the Accessibility Keyboard using the regular keyboard. (for example: remap the row number keys.) Explanation: mac's on-screen keyboard has some great features for people with accessibility needs: it is static on the screen, present the typed text in a big font and suggest words. The problem is that the physical keyboard can't use the word suggestion. some of us (accessibility users) can benefit from text prediction using a keyboard, like in any IDE (for programmers) or iPhone keyboard. We are more comfortable using a keyboard than a mouse. By the way: Microsoft Windows's implementation is lacking, as it requires the use of the "up arrow+enter" which is small and far from the center of the keyboard, therefore hard to reach while typing fast, but at least there is something :-) in that case a keyboard macro can help to remap the row number into "up+up...+enter". I have tried to develop it without success. my problem is that I can't find a way to interact with the accessibility keyboard. remapping keys to run a script is the easier part. Thank you for helping make Apple more accessible.

How can we assign the unique accessibility identifiers to the urls in UITextView In the accessibility inspector, I am able to see the urls as separate elements but not able to set the accessibility identifiers for them. The accessibility identifiers are needed for automation testing. In the screenshots added here, i have taken a UITextView which has urls in it.

now i have a device connected with USB in remote, i want to use some api or command to control it when voiceover is on, is there any way we can do it? maybe use usbmuxd or some other way?

I'm using NSAccessibilityAnnouncementRequestedNotification with NSAccessibilityPriorityMedium to announce incoming, unsolicited text in a text game - and sometimes VoiceOver will move onto the next message without fully reading out the first. How can I get VoiceOver to fully read out the current message before moving onto the next? I'm building this accessibility work as part of Mudlet (mudlet.org) an open-source MUD client to give more context.

Is there a good alternative to UILargeContentViewerInteraction - https://developer.apple.com/documentation/uikit/uilargecontentviewerinteraction/ in SwiftUI? I know that TabBar - https://developer.apple.com/documentation/swiftui/tabview has support for the large content viewer, but I'm not sure how to implement it in a custom control. Any ideas? I've tried adding UILargeContentViewerInteraction to a UIKit wrapper, but I must've been doing that wrong because all it did was interrupt long presses. Thanks!

As I currently live in ReactNative Hell, I like to flesh out all my native iOS demos and samples to the max. Including things like accessibility. Recently, I wrote a very simple demo containing a map, and I stumbled upon some issues I was unable to resolve. I think they present very general usecases, and so I would be happy if anyone of you had any idea. The condensed source code for the issues can be found on GitHub Issue 1: The Phantom Overlay To reproduce Run the app on a device, and be sure that VoiceOver is on. Swipe right to get to the Annotations. Expected Result The title of the annotation is read. Actual Result The title of the annotation is read twice. What I know For every annotation on the map view, there is also an overlay, an MKCircle, generated by an MKCircleRenderer. When this overlay is not present, the title is — correctly — only read once. What I have tried In ViewController.swift, lines 54 and 92, I have set both the overlay's and the renderer's isAccessibilityElement property to false. This does not fix the issue (probably because neither of them are the actual views). The overlay should never be an accessible element. Any information should be encoded in the annotation (e.g. "There is a 10m region around this marker") Issue 2: The Unknown Trait While it is correct that the title of the annotation should be read, there is no indication that the annotation can be clicked or interacted with. I have set annotationView.accessibilityTraits = [.button], but this does not change anything. My expectation would be "Cologne Cathedral, Button" or a similar hint that the item is clickable. Issue 3: The Unreachable Callout With VoiceOver active, click on an annotation. I have taken some hints from Stackoverflow, and tried to disable the accessibility on the annotation, and enable it on the callout. This leads to the callout being reachable somehow, but it is absolutely not obvious if you can not see the screen. How can I indicate to the VoiceOver user that now a callout is being shown? A Working Extra: The Annotation Rotor The app also contains a custom rotor, to go through the annotations one by one, without also reading the default Points-Of-Interest on the map. Interestingly (or maybe rather as expected), the title of the annotation is correctly only read once. I whould be extremely happy to get some feedback on these issues, it sounds like most of them could be rather common. Thanks! Alex

Hi All, We are using html input type date in our hybrid application which launches the native datepicker in the app. As we need the app to be accessible we chose the html type date. However at certain instances we want to restrict the date selection till present date only. We have used the max attribute to achieve this, for some reasons the datepicker is not respecting this attribute and allowing the user to select future dates. We are in a tricky position since we do not want to use any library and the production date is nearby. Below is the markup we have used for replicating the behavior: form label for="party"Choose your preferred party date: input type="date" name="party" min="2017-04-01" max="2017-04-30" /label /form Any help would be appreciated. Thanks in advance.

I'm working on a mac app that has similar functionalities to the Rocket macOS app. Whenever the user types : outside of my app I'll show an NSPopover with NSTableView near the cursor. The problem I'm facing here is that The moment I show the NSPopover it becomes the first responder and the user couldn't continue typing. So I tried this, Showed the NSPopover without making a first responder, and used NSEvent.addGlobalMonitorForEvents(matching: .keyDown, handler: ) to listen UpArrow, DownArrow and Enter actions to navigate and select results. The downside of this approach: Let's say I'm composing a new mail, and the cursor responding to the up/down arrow events, eventually moved to other lines. Attaching gifs for reference, The functionality that I'm expecting From my app Note: Notice the cursor position to understand what goes wrong.

Hi. i'm developing an iOS Phone Call app for enterprise release. iPhone has auto-answer option when you have an incoming phone call. i want to progrmatically control auto-answer option in my Objective-c( or Swift ) code. is there any API to set iPhone's auto-answer option excluding jail-breaks? and i wonder if this auto-answer controlling is an invasion of privacy.

I'm working on a mac app that uses Accessibility APIs to get the cursor position from the focused element (Focused element can be from any app) and shows a window near the cursor position. I checked the window positioning in native apps like XCode, Notes, and Messages and tried on web apps as well everything is working fine. I checked the same on the slack desktop app where I'm facing an issue. Which is I'm getting the XOrigin always as 0 and YOrigin as 982 (That is equal to my screen's size: NSScreen.main?.frame.height). Seems it is breaking on electron apps. What am I missing here? Do we need to account for anything else to handle electron apps? Attaching my code for reference. extension AXUIElement {   func getCursorRect() -> CGRect? {     guard let cursorPosition = cursorPosition else {return nil}     var cfRange: CFRange = .init(location: cursorPosition, length: 1)     let axval: AXValue? = AXValueCreate(.cfRange, &cfRange)     var bounds: CFTypeRef?     guard let axval = axval else {return nil}     AXUIElementCopyParameterizedAttributeValue(self, kAXBoundsForRangeParameterizedAttribute as CFString, axval, &bounds)     var cursorRect: CGRect = .zero     guard let bounds = bounds else {return nil}     AXValueGetValue(bounds as! AXValue, .cgRect, &cursorRect)     return cursorRect   } }

Dear I want to development Braille Display Device for IOS. Does the IOS support BLE for Braille Display? Is there any guidance for Braille Display for IOS? Best regards, Joey Kang

Recently I was using tiktok and was messing with my phone. I have the iOS 16 update and I have an IPhone 13. I saw a random bar with a scissor Icon and a arrow as well as other icons which I cannot remember. I have no idea how I triggered this bar to appear and I have no idea what it is. I’ve been searching the internet and found no answer PLEASE HELP ME FIND IT!!

Hi folks, I'm really happy you have made this and would love to chat more on the subject if that's your jam. However, I am struggling to integrate your plugin with my project. I have updated to Unity 2020.3.36f1 (Unity 2020.3.33f1 does not open on my laptop, seem like others had similar issues). The plugin compiles correctly in my Unity project, and I have referenced AccessibilitySettings.PreferredContentSizeMultiplier. Unity builds the XCode project fine, but I cannot build in XCode because of a series of errors like this: Undefined symbols for architecture arm64:   "__UnityAX_registerAccessibilityPreferredContentSizeCategoryDidChangeNotification", referenced from:       _AccessibilitySettings_RegisterCallbacks_m24D66FBB224A583EB09114081A38990B392CC1F4 in Apple.Accessibility.o       _AccessibilitySettings__UnityAX_registerAccessibilityPreferredContentSizeCategoryDidChangeNotification_mAE514A0A5C03E7E91AC797D9FB1E52650D30AB1E in Apple.Accessibility.o      (maybe you meant: _AccessibilitySettings__UnityAX_registerAccessibilityPreferredContentSizeCategoryDidChangeNotification_mAE514A0A5C03E7E91AC797D9FB1E52650D30AB1E)   "__UnityAX_registerAccessibilityIsSwitchControlRunningDidChangeNotification", referenced from:       _AccessibilitySettings_RegisterCallbacks_m24D66FBB224A583EB09114081A38990B392CC1F4 in Apple.Accessibility.o I suspect I am not linking a library I should be, however, adding the Accessibility framework to Embedded Frameworks or to the UnityFramework has not resolved the issue. Could you please point me in the right direction? All the best, Le-Roy