Home | History | Annotate | Download | only in versions

Lines Matching full:accessibility

48   <li><a href="#A11y">Accessibility</a>
50 <li><a href="#A11yService">Accessibility service APIs</a></li>
552 <h2 id="A11y">Accessibility</h2>
554 <h3 id="A11yService">Accessibility service APIs</h3>
556 <p>The reach of accessibility service APIs has been significantly increased in Android 4.1. It now
559 input events through additions to the {@link android.view.accessibility.AccessibilityEvent}, {@link
560 android.view.accessibility.AccessibilityNodeInfo} and {@link
561 android.view.accessibility.AccessibilityRecord} classes.</p>
563 <p>Accessibility services can also perform actions on behalf of the user, including clicking,
565 android.view.accessibility.AccessibilityNodeInfo#performAction performAction} and {@link
566 android.view.accessibility.AccessibilityNodeInfo#setMovementGranularities
577 android.view.accessibility.AccessibilityNodeInfo#findFocus findFocus()} and {@link
578 android.view.accessibility.AccessibilityNodeInfo#focusSearch focusSearch()}, and set focus
579 using {@link android.view.accessibility.AccessibilityNodeInfo#setAccessibilityFocused
585 <p>The new {@code android.view.accessibility.AccessibilityNodeProvider} class allows you to
586 surface complex custom views to accessibility services so they can present the information in a
587 more accessible way. The {@code android.view.accessibility.AccessibilityNodeProvider} allows a user
589 accessibility services that is completely separate from the widget?s layout structure. This semantic
590 structure allows accessibility services to present a more useful interaction model for users who are