Enable accessibility programmatically on load#78
Merged
Conversation
Contributor
Author
There was a problem hiding this comment.
Fixed and updated... got overly keen with my camel casing there!
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.
It's a pain to have to enable accessibility in the Settings app before running tests. This code edits the relevant plist file automatically on load. I discovered it needs to be done pretty early, so it's done on class loading - calling on init didn't seem to work (plist content and timestamp did not change).
This seems to correctly enable accessibility, but the method to check whether accessibility was enabled returned true in both cases. However, tests failed without enabling accessibility, and passed with this method being called, so it seems to be working as expected (maybe we need a new way of checking accessibility being enabled?)
It works for the simulator only, and was testing with iOS 5.0 Simulator SDK.