fix: expose iOS sheet accessibility content#699
Merged
Conversation
|
@erickreutz is attempting to deploy a commit to the lodev09 Team on Vercel. A member of the Team first needs to authorize it. |
lodev09
approved these changes
May 29, 2026
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix iOS sheet accessibility traversal so the presented sheet wrapper exposes the mounted content view, and footer controls nested inside the footer host view remain reachable by XCTest and assistive technologies.
Type of Change
Bug fix.
Test Plan
Ran
PATH="$(dirname $(xcrun --find clang-format)):$PATH" scripts/objclint.sh.Ran
corepack yarn typecheck.Ran
corepack yarn test --maxWorkers=2.Screenshots / Videos
N/A
Checklist
Tested on iOS through Lugg app Maestro/XCTest coverage.
Android and Web are unaffected; this only changes iOS native accessibility traversal.
Added changelog entry.