Alexander Lucas | df6c827 | 2012-03-06 18:13:07 -0800 | [diff] [blame] | 1 | page.title=Implementing Accessibility |
Scott Main | 1c2dea0 | 2013-04-10 18:59:29 -0700 | [diff] [blame] | 2 | page.tags="navigation","input" |
Alexander Lucas | df6c827 | 2012-03-06 18:13:07 -0800 | [diff] [blame] | 3 | |
| 4 | trainingnavtop=true |
| 5 | startpage=true |
Alexander Lucas | df6c827 | 2012-03-06 18:13:07 -0800 | [diff] [blame] | 6 | |
| 7 | @jd:body |
| 8 | |
| 9 | <div id="tb-wrapper"> |
| 10 | <div id="tb"> |
| 11 | |
| 12 | <h2>Dependencies and prerequisites</h2> |
| 13 | <ul> |
| 14 | <li>Android 2.0 (API Level 5) or higher</li> |
Alexander Lucas | df6c827 | 2012-03-06 18:13:07 -0800 | [diff] [blame] | 15 | </ul> |
| 16 | |
| 17 | <h2>You should also read</h2> |
| 18 | <ul> |
| 19 | <li><a href="{@docRoot}guide/topics/ui/accessibility/index.html">Accessibility</a></li> |
| 20 | </ul> |
| 21 | |
| 22 | </div> |
| 23 | </div> |
| 24 | |
| 25 | <p>When it comes to reaching as wide a userbase as possible, it's important to |
| 26 | pay attention to accessibility in your Android application. Cues in your user |
| 27 | interface that may work for a majority of users, such as a visible change in |
| 28 | state when a button is pressed, can be less optimal if the user is visually |
| 29 | impaired.</p> |
| 30 | |
| 31 | <p>This class shows you how to make the most of the accessibility features |
| 32 | built into the Android framework. It covers how to optimize your app for |
| 33 | accessibility, leveraging platform features like focus navigation and content |
| 34 | descriptions. It also covers how to build accessibility services, that can |
| 35 | facilitate user interaction with <strong>any</strong> Android application, not |
| 36 | just your own.</p> |
| 37 | |
| 38 | <h2>Lessons</h2> |
| 39 | |
| 40 | <dl> |
| 41 | <dt><b><a href="accessible-app.html">Developing Accessible Applications</a></b></dt> |
| 42 | <dd>Learn to make your Android application accessible. Allow for easy |
| 43 | navigation with a keyboard or directional pad, set labels and fire events |
| 44 | that can be interpreted by an accessibility service to facilitate a smooth |
| 45 | user experience.</dd> |
| 46 | |
| 47 | <dt><b><a href="service.html">Developing Accessibility Services</a></b></dt> |
| 48 | <dd>Develop an accessibility service that listens for accessibility events, |
| 49 | mines those events for information like event type and content descriptions, |
| 50 | and uses that information to communicate with the user. The example will |
| 51 | use a text-to-speech engine to speak to the user.</dd> |
| 52 | |
| 53 | </dl> |
| 54 | |