Initial draft of ChromeVox Next tutorial.

chrome/browser/resources/chromeos/chromevox/chromevox/background/keymaps/next_keymap.json

Index: chrome/browser/resources/chromeos/chromevox/chromevox/background/keymaps/next_keymap.json
diff --git a/chrome/browser/resources/chromeos/chromevox/chromevox/background/keymaps/next_keymap.json b/chrome/browser/resources/chromeos/chromevox/chromevox/background/keymaps/next_keymap.json
index 8349b199a5ff61aaf0e99ec3bb12f4fdc0fdceed..23ac466e0294733dedb641c75c9e5dc3804c9428 100644
--- a/chrome/browser/resources/chromeos/chromevox/chromevox/background/keymaps/next_keymap.json
+++ b/chrome/browser/resources/chromeos/chromevox/chromevox/background/keymaps/next_keymap.json
@@ -570,6 +570,15 @@
           "keyCode": [65, 66]
         }
       }
+    },
+    {
+      "command": "help",

[David Tseng, 2016/06/29 20:59:43]

I already added a showUpdatePage command.

The user flow I was going for was the following:
User always starts off in Classic. As soon as a user turns on ChromeVox, he/she
gets alerted via a message center notification of changes in ChromeVox. Hitting
Search+o, n will get the user to the page (this can be the tutorial).

In this cl, a user would only get tot the tutorial if they clicked on the
message and not via the key.

[dmazzoni, 2016/06/29 22:51:35]

Got it. Switched it so that showNextUpdatePage opens the tutorial.

+      "sequence": {
+        "cvoxModifier": true,
+        "keys": {
+          "keyCode": [79, 84]
+        }
+      }
     }
   ]
 }