Home | History | Annotate | Download | only in keyboard-input

Lines Matching full:your

12 <ol>
  <li><a href="#Test">Test Your App</a></li>
  <li><a href="#Tab">Handle Tab Navigation</a></li>
  <li><a href="#Direction">Handle Directional Navigation</a></li>
</ol>
28 interact with your app. Although most hand-held devices such as phones use touch as the
34 you optimize your app to support interaction through a keyboard. This lesson describes
38 Supporting of directional navigation in your application is also important in ensuring that
39 your application is <a href="{@docRoot}guide/topics/ui/accessibility/apps.html">accessible</a>
40 to users who do not navigate using visual cues. Fully supporting directional navigation in your
47 <h2 id="Test">Test Your App</h2>
49 <p>It's possible that users can already navigate your app using a keyboard, because the
57 <p>To test your app:</p>
59 <li>Install your app on a device that offers a hardware keyboard.
70 <li>To test your app, use only the Tab key to navigate through your UI, ensuring that
74 <li>Start from the beginning of your app and instead use the direction controls
75 (arrow keys on the keyboard) to navigate your app.
76 <p>From each focusable element in your UI, press Up, Down, Left, and Right.</p>
82 does not do what you expect, specify where the focus should go in your layout, as discussed
89 <p>When a user navigates your app using the keyboard Tab key,
132 <p>Users can also navigate your app using the arrow keys on a