Used in combination, testing with VoiceOver and debugging with Accessibility Inspector is an effective approach. For example, you might use UIAccessibilityAnnouncementNotification to notify VoiceOver users when some information appears briefly on screen. Notifications are messages that keep VoiceOver up-to-date with what’s happening in your app. As you update your code the changes are reflected in real time, helping you experiment with different solutions. You can examine the accessible label, value, hint (if available), accessibility traits and frame co-ordinates for each control. In the Accessibility Inspector panel you’ll find two types of information: properties and notifications. You need to temporarily disable it (toggle the close control in the upper left of the panel), then scroll the mouse to the desired location before enabling Accessibility Inspector again. Double click Activates the selected control.ĭragging or flicking can’t be simulated with Accessibility Inspector running. With Accessibility Inspector turned on, a different set of gesture replacements is used: Single click Selects a control. A single click simulates a tap, and scrolling simulates flicking or dragging. When you use iOS Simulator you can mimic touch gestures with a mouse. However, you can temporarily turn it on/off using the toggle in the corner of the panel (a circle with an X). This opens the Accessibility Inspector panel.Īccessibility Inspector will remain available until you use the switch to turn it off. To turn on Accessibility Inspector, run your app in iOS Simulator, go to Home > Settings > General > Accessibility and slide the Accessibility Inspector switch to on. Debugging with Accessibility Inspector Use the Accessibility Inspector in XCode and iOS simulator This disables the visual display on the device, letting you explore your app using VoiceOver alone. Triple tap to turn the screen curtain on/off. When you test your app it’s a good idea to simulate the experience of a VoiceOver user as closely as possible. Three finger swipe left/right Moves to the previous/next screen. ![]() Flick left/right Moves to the previous/next control. Double tap Activates the selected control. Single tap Causes VoiceOver to announce the selected control. The following basic gestures will help you test your app: Move finger on screen Causes VoiceOver to announce whatever is under your finger. When VoiceOver is turned on you’ll need a different set of gestures. Hints will help you use VoiceOver, and you’ll also want to test any hints included in your app. At the same time check that Speak Hints is enabled (it’s on by default). You can turn VoiceOver on/off at any time by triple clicking the home button, but the first time it’s a good idea to go to Settings > General > Accessibility > VoiceOver and tap the switch to turn it on. Testing with VoiceOver and debugging with the Accessibility Inspector is a good approach though. Accessibility Inspector doesn’t have speech output, so it’s a debugging tool rather than a testing tool. ![]() Accessibility Inspector lets you simulate VoiceOver interactions, and examine the accessibility information that’s available for the controls in your app. ![]() When your app (or prototype) is in a fit state to be deployed on a device, testing it with VoiceOver, or better still asking VoiceOver users to test it, will give you realistic feedback.Īccessibility Inspector (available in the iOS Simulator) can then be used to debug any problems you discover. When it comes to testing, there is no substitute for using your app on an iOS device with VoiceOver turned on. Native UI controls have accessibility built-in as standard, and custom controls can be accessibility-enabled without difficulty. When you build an iOS app it’s easy to make it VoiceOver accessible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |