For modifying feature state, the extension needs accessibilityFeatures.modify permission. In order to get feature states the extension must request accessibilityFeatures.read permission. This API relies on the ChromeSetting prototype of the type API for getting and setting individual accessibility features. Use the chrome.accessibilityFeatures API to manage Chrome's accessibility features. Release information is not available for APIs before Chrome 42, which was released in early 2015. For more information, see Asynchronous methods. If you need to know the result of calling such methods, use the returned promise or pass a callback function into the method.

Unless stated otherwise, methods in the chrome.* APIs are asynchronous: they return immediately, without waiting for the operation to finish. For example, chrome.alarms requires only the alarms permission, while chrome.action requires an action object in the manifest.json file.

These fields are frequently permissions, but not always. Many APIs consist of a namespace and its related manifest fields. Chrome provides extensions with many special-purpose APIs such as chrome.alarms and chrome.action.

Google chrome remote desktop install