From 4045e6b9ab296436cb5344f3af7184c2ce2a8ff0 Mon Sep 17 00:00:00 2001 From: Scott Main Date: Thu, 24 Mar 2011 13:25:48 -0700 Subject: docs: a11y doc typo Change-Id: Ib4c41c129c8ecbd738dfe6866bd429efdf17c23f --- docs/html/guide/practices/design/accessibility.jd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/html/guide/practices/design/accessibility.jd b/docs/html/guide/practices/design/accessibility.jd index 4590682..a2b314e 100644 --- a/docs/html/guide/practices/design/accessibility.jd +++ b/docs/html/guide/practices/design/accessibility.jd @@ -18,7 +18,7 @@ accessibility events during user interaction
  • Allow Navigation with a Directional Controller
    1. Controlling focus order
    2. -
    3. Clicking with the a directional controller
    4. +
    5. Clicking with a directional controller
  • Label Your Input Widgets
  • @@ -157,7 +157,7 @@ setNextFocusDownId()} and {@link android.view.View#setNextFocusRightId setNextFocusRightId()}.

    -

    Clicking with the a directional controller

    +

    Clicking with a directional controller

    On most devices, clicking a view using a directional controller sends a {@link android.view.KeyEvent} with {@link android.view.KeyEvent#KEYCODE_DPAD_CENTER} to the view currently -- cgit v1.1