Lines Matching full:accessibility
462 <h2 id="43-accessibility">Accessibility and UI Automation</h2>
464 <p>Starting in Android 4.3, accessibility services can <strong>observe and
470 <p>Accessibility services can declare <strong>new capability attributes</strong>
473 content, enable explore-by-touch, or enable web accessibility features. In some
479 <p>Building on the accessibility framework in Android 4.3, a new <strong>UI
957 <h2 id="42-accessibility">Accessibility</h2>
959 <p>The system now helps accessibility services <strong>distinguish between touch
960 exploration and accessibility gestures</strong> while in touch-exploration mode.
963 and determines whether it is a touch exploration (slow) or accessibility gesture
967 <p>The system provides a new global accessibility option that lets an
968 accessibility service open the Quick Settings menu based on an action by the
969 user. Also added in Android 4.2 is a new accessibility feedback type for
972 <p>To give accessibility services insight into the meaning of Views for
973 accessibility purposes, the framework provides new APIs for associating a View
975 accessibility services through AccessibilityNodeInfo.</p>
1274 <img src="{@docRoot}images/jb-accessibility-focus-250.png" width="240px" height="469">
1278 <h2 id="accessibility">Enhanced Accessibility</h2>
1280 <p>New APIs for accessibility services let you handle gestures and manage <strong>accessibility focus</strong> as the user moves through the on-screen elements and navigation buttons using accessibility gestures, accessories, and other input. The Talkback system and explore-by-touch are redesigned to use accessibility focus for easier use and offer a complete set of APIs for developers.</p>
1282 <p>Accessibility services can link their own <strong>tutorials</strong> into the Accessibility settings, to help users configure and use their services.</p>
1284 <p>Apps that use standard View components <strong>inherit support</strong> for the new accessibility features automatically, without any changes in their code. Apps that use custom Views can use new accessibility node APIs to indicate the parts of the View that are of interest to accessibility services. </p>
