directly in your custom view class. For another example of this approach, see the Android
<a href="{@docRoot}tools/support-library/index.html">Support Library</a> (revision 5 or higher)
sample {@code AccessibilityDelegateSupportActivity} in
-({@code <sdk>/extras/android/support/v4/samples/Support4Demos/}).</p>
+({@code <sdk>/extras/android/support/v4/samples/Support4Demos/}).</p>
- <p class="note"><strong>Note:</strong> You may find information on implementing accessibility for
- custom views written prior to Android 4.0 that describes the use of the
- {@link android.view.View#dispatchPopulateAccessibilityEvent dispatchPopulateAccessibilityEvent()}
- method for populating AccessibilityEvents. As of the Android 4.0 release, however, the recommended
- approach is to use the
- {@link android.view.View#onPopulateAccessibilityEvent onPopulateAccessibilityEvent()} and
- {@link android.view.View#onInitializeAccessibilityEvent onInitializeAccessibilityEvent()}
- methods.</p>
-
<h3 id="virtual-hierarchy">Providing a customized accessibility context</h3>
</PreferenceScreen>
</pre>
-<p>Because support for {@code <preference-headers>} was added in Android 3.0, the system calls
+<p>Because support for {@code <preference-headers>} was added in Android 3.0, the system calls
{@link android.preference.PreferenceActivity#onBuildHeaders onBuildHeaders()} in your {@link
- android.preference.PreferenceActivity} only when running on Androd 3.0 or higher. In order to load
+ android.preference.PreferenceActivity} only when running on Android 3.0 or higher. In order to load
the "legacy" headers file ({@code preference_headers_legacy.xml}), you must check the Android
version and, if the version is older than Android 3.0 ({@link
android.os.Build.VERSION_CODES#HONEYCOMB}), call {@link