Using the Accessibility Inspector to Drive the UI in Simulator This isn’t to say that you should always test with Accessibility Inspector as a part of your toolchain, but instead use VoiceOver at the end of that process and use the Accessibility Inspector throughout that process. This is going to help you explore all of that information in one place while being a more valuable tool for developers than VoiceOver. Moreover, in the Accessibility Inspector, you can see all of the properties at once, whereas VoiceOver only can view about a subset of those properties. You can also explore switch control, braille boards, and alternative input devices. The Accessibility Inspector is not only to helpful for making an app more accessible VoiceOver applications, but it helps you explore all of the accessibility properties that are available for other assistive technologies. Instead of using VoiceOver in the simulator, you can explore the accessibility of an app using the Accessibility Inspector.
However, when you’re testing in the simulator you do not have access to VoiceOver or the other assistive technologies on the device. It’s very frustrating.įor this reason, testing in the simulator is very useful. Then you’ll have to wait for and an unknown amount of time until you can test on a device again. On top of that, you never know when the toolchain’s going to break, and if it does your team agent has to go in and accept some new, updated agreement. Primarily, it is difficult to keep devices set up, manage your profiles, and your development stuff. One of the things that is frustrating about the iOS environment is how difficult it is to test on a device.
Testing Accessibility in iOS Simulator with the iOS Accessibility Inspector
0 kommentar(er)
