added performAccessibilityActivateWithExpectedResult#1304
Merged
Conversation
RoyalPineapple
commented
Sep 17, 2024
RoyalPineapple
force-pushed
the
alex/AccessibilityActivate
branch
2 times, most recently
from
61f9c9d to
c2e68f6
Compare
RoyalPineapple
changed the title
justinseanmartin
approved these changes
Sep 17, 2024
RoyalPineapple
force-pushed
the
alex/AccessibilityActivate
branch
from
f0ef0aa to
eaa3168
Compare
kyleve
approved these changes
Sep 23, 2024
RoyalPineapple
force-pushed
the
alex/AccessibilityActivate
branch
from
eaa3168 to
c2341aa
Compare
RoyalPineapple
force-pushed
the
alex/AccessibilityActivate
branch
from
c2341aa to
4dac875
Compare
amorde
pushed a commit
to amorde/KIF
that referenced
this pull request
Jun 26, 2025
amorde
pushed a commit
to amorde/KIF
that referenced
this pull request
Feb 24, 2026
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
3 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.
Some of my recent accessibility work in our design system results in accessibility elements that abstract away the interactivity of some underlying controls. These elements subsume the interactivity of their children and re-expose the functionality via
accessibilityActivate().Unfortunately this breaks KIF matching resulting in the need for an escape hatch to allow activation of elements with greater complexity.
performAccessibilityActivateWithExpectedResult calls accessibilityElement() on the found element and compares its result to the expectation.