Explore best practices for creating inclusive apps that cater to users with diverse abilities

Learn More

Post

Replies

Boosts

Views

Activity

White screen in iOS18
Our app: https://apps.apple.com/it/app/bookapp-business/id1511129368 BookApp Business, does not work in iOS 18 when it starts it opens a white screen it is developed in Xamarin Forms and we cannot update it are there any solutions? tanks for support Alex
5
0
279
1w
IOS Applink Not Working
Hello There, I setup the applinks in ios app. The associated domain url returning the correct response and in my app the same is been confiqured. But when the link is called the app is not recognising. I tried all the possible method but its not working.
0
0
169
1w
IPad OS18
since having updated my iPad with subject title update, I can no longer type French accents with my magic keyboard. The toggle between English and French is there, the actual key type is no longer available.
0
0
174
1w
Disable Inappropriate Content Warnings in Writing Tools
I’ve noticed that the writing tools frequently display content warnings for certain topics, often more than seems necessary, and I would love to see a way to disable them in my app. Specifically, I have encountered many situations where mentioning LGBTQ topics triggers a content warning and temporarily blocks the user, while similar mentions of heterosexual topics do not. For example: Triggers Content Warning: “I’ve been listening to this song on repeat yesterday and today haha. It’s really nice that it’s about being homosexual ~u~” “I’ve been listening to this song on repeat yesterday and today haha. It’s really nice that it’s about being *** ~u~” Does Not Trigger Content Warning: “I’ve been listening to this song on repeat yesterday and today haha. It’s really nice that it’s about being heterosexual ~u~” “I’ve been listening to this song on repeat yesterday and today haha. It’s really nice that it’s about being straight ~u~” This inconsistency not only introduces unnecessary friction when discussing diverse topics but may also inadvertently suggest that LGBTQ topics are inappropriate or immoral. Such an implication could be harmful to many users, especially young adults, by reinforcing negative perceptions of LGBTQ issues. I believe it’s important for the AI writing tools to handle all topics equitably to promote inclusivity and diversity. And would love to be able to disable these warnings in my app. here’s a video showcasing the example prompts above: https://share.icloud.com/photos/0bdGPxy2xmGZT2ildAU4ThERQ
0
0
240
2w
2.0 System Controls In Immersive Space
How do I enable the system hand controls within an immersive space? I have an ImmersiveScene and would like to enable the new 2.0 system controls like the home button and volume slider. ImmersiveSpace(id: appModel.immersiveSpaceID) { ImmersiveView() } .immersionStyle(selection: .constant(.full), in: .full) .upperLimbVisibility(.visible) While I can see my hands and arms in this view, I cannot get the "New Hand Gestures" to show up when on visionOS 2.0. When I leave the immersive space, they appear.
1
0
252
2w
Expose ContextMenu as annoucable
I have a list of items that have swipe actions that I'd like to hide from accessibility and make actions available via the AccessibilityActions modifier. Additionally, I would like to make the contextMenu annoucable as an action. This behavior exists in the Apple Podcasts app but can't find out to do it in SwiftUI. If the users knows to use the triple-tap, they can activate the context menu but have it as an action of the element is even better.
0
0
345
3w
Not able to capture individual elements on the home screen of iOS17 device with xCode 15.4 and appium2
Hello Team, I am not able to capture any elements on physical iPad device in Landscape mode. Elements appear to be offset. I suspect it considers the screen in Portrait mode even though it’s in landscape mode. I am using below devices: iPAD(10th generation) - iOS 17.6.1 Xcode - 15.4 Appium - 2.11.3 Xcuitest to 7.26.0 Note - I am able to capture the elements in the portrait mode on ipad Could you please help me or provide any inputs on this ?
0
0
296
3w
Unreliable Accessibility API behavior when interacting with Microsoft Teams app
I'm developing a macOS app that interacts with Microsoft Teams using the Accessibility API. I've noticed inconsistent behavior when querying UI elements, particularly for the mute button. My queries often fail, while system tools like VoiceOver can consistently access these elements (which are visible on the screen). In some cases, it works well, but in others, the UI elements are not visible from my code. When I try Accessibility Inspector, it also initially fails to inspect. However, the Inspector seems to have some "magical" power that, when I run it or via AX audit, appears to refresh the AX tree, and then my code occasionally works as well. Given that VoiceOver can consistently read the screen, I assume the issue is not with the Microsoft Teams app itself (assuming it's based on Electron/React). I am mentioning this, because when I interact with Zoom app, reading the mute status from the app's menu bar, its 100% working anytime. What would you recommend I try or explore to improve reliability? Can I refresh the apps' AX tree from my end from swift? Is that a bug in AX API or even in Microsoft Teams? (have ready example and demo video, but it does not let me upload here)
1
0
320
3w