Add policy management for on-screen keyboard.

components/policy/resources/policy_templates.json

 {
 # policy_templates.json - Metafile for policy templates
 #
 # The content of this file is evaluated as a Python expression.
 #
 # This file is used as input to generate the following policy templates:
 # ADM, ADMX+ADML, MCX/plist and html documentation.
 #
 # Policy templates are user interface definitions or documents about the
 # policies that can be used to configure Chrome. Each policy is a name-value
@@ skipping 100 matching lines @@
 #   templates and documentation. The policy definition list that Chrome sees
 #   will include policies marked with 'future'. If a WIP policy isn't meant to
 #   be seen by the policy providers either, the 'supported_on' key should be set
 #   to an empty list.
 #
 # IDs:
 #   Since a Protocol Buffer definition is generated from this file, unique and
 #   persistent IDs for all fields (but not for groups!) are needed. These are
 #   specified by the 'id' keys of each policy. NEVER CHANGE EXISTING IDs,
 #   because doing so would break the deployed wire format!
-#   For your editing convenience: highest ID currently used: 254
+#   For your editing convenience: highest ID currently used: 256
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
 #     $1 -> Google Chrome / Chromium
 #     $2 -> Google Chrome OS / Chromium OS
 #     $3 -> Google Chrome Frame / Chromium Frame
 #     $6 is reserved for doc_writer
 #
 # Device Policy:
 #   An additional flag device_only (optional, defaults to False) indicates
@@ skipping 5305 matching lines @@
 
           If this policy is set to true, high contrast mode will always be enabled.
 
           If this policy is set to false, high contrast mode will always be disabled.
 
           If you set this policy, users cannot change or override it.
 
           If this policy is left unset, high contrast mode is disabled initially but can be enabled by the user anytime.'''
         },
         {
+          'name': 'VirtualKeyboardEnabled',
+          'type': 'main',
+          'schema': { 'type': 'boolean' },
+          'supported_on': ['chrome_os:34-'],
+          'features': {
+            'can_be_recommended': True,
+            'dynamic_refresh': True,
+            'per_profile': True,
+          },
+          'example_value': True,
+          'id': 255,
+          'caption': '''Enable on-screen keyboard''',
+          'desc': '''Enable the on-screen keyboard accessibility feature.
+
+          If this policy is set to true, the on-screen keyboard will always be enabled.
+
+          If this policy is set to false, the on-screen keyboard will always be disabled.
+
+          If you set this policy, users cannot change or override it.
+
+          If this policy is left unset, the on-screen keyboard is disabled initially but can be enabled by the user anytime.'''
+        },
+        {
           'name': 'ScreenMagnifierType',
           'type': 'int-enum',
           'schema': {
             'type': 'integer',
             'enum': [ 0, 1 ],
           },
           'items': [
             {
               'name': 'None',
               'value': 0,
@@ skipping 82 matching lines @@
 
           If this policy is set to true, high contrast mode will be enabled when the login screen is shown.
 
           If this policy is set to false, high contrast mode will be disabled when the login screen is shown.
 
           If you set this policy, users can temporarily override it by enabling or disabling high contrast mode. However, the user's choice is not persistent and the default is restored whenever the login screen is shown anew or the user remains idle on the login screen for a minute.
 
           If this policy is left unset, high contrast mode is disabled when the login screen is first shown. Users can enable or disable high contrast mode anytime and its status on the login screen is persisted between users.''',
         },
         {
+          'name': 'DeviceLoginScreenDefaultVirtualKeyboardEnabled',
+          'type': 'main',
+          'schema': { 'type': 'boolean' },
+          'supported_on': ['chrome_os:34-'],
+          'device_only': True,
+          'features': {
+            'dynamic_refresh': True,
+          },
+          'example_value': True,
+          'id': 256,
+          'caption': '''Set default state of the on-screen keyboard on the login screen''',
+          'desc': '''Set the default state of the on-screen keyboard accessibility feature on the login screen.
+
+          If this policy is set to true, the on-screen keyboard will be enabled when the login screen is shown.
+
+          If this policy is set to false, the on-sreen keyboard will be disabled when the login screen is shown.
+
+          If you set this policy, users can temporarily override it by enabling or disabling the on-screen keyboard. However, the user's choice is not persistent and the default is restored whenever the login screen is shown anew or the user remains idle on the login screen for a minute.
+
+          If this policy is left unset, the on-screen keyboard is disabled when the login screen is first shown. Users can enable or disable the on-screen keyboard anytime and its status on the login screen is persisted between users.''',
+        },
+        {
           'name': 'DeviceLoginScreenDefaultScreenMagnifierType',
           'type': 'int-enum',
           'schema': {
             'type': 'integer',
             'enum': [ 0, 1 ],
           },
           'items': [
             {
               'name': 'None',
               'value': 0,
@@ skipping 563 matching lines @@
       'desc': '''Text appended in parentheses to the policy name to indicate that it has been deprecated''',
       'text': 'deprecated',
     },
     'doc_recommended': {
       'desc': '''Text appended in parentheses next to the policies top-level container to indicate that those policies are of the Recommended level''',
       'text': 'Default Settings (users can override)',
     },
   },
   'placeholders': [],
 }