> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/device-applications/accessibility-enabler.md).

# Accessibility Enabler

The BlueFletch Accessibility Enabler automates the process of granting application-level accessibility permissions in Android Settings. An administrator can include this in a deployment without needing to distribute credentials for administrative settings to every store manager.

The application enables Android Settings, launches Accessibility settings, and then triggers automated button-taps to grant accessibility permissions to another application. The automated taps and delays between taps are based on parameters passed in by an Android intent. Once the prescribed taps have occurred, the app then closes Accessibility settings and returns Android Settings to a disabled state.

## Intent to Launch

The intent to initiate the Accessibility Enabler must include coordinates for the steps in Accessibility settings to grant permissions, and can optionally include a delay before starting touch events and/or a delay between touch events.

Intent as an ADB command:

```
adb shell "am start -a android.intent.action.MAIN -n com.bluefletch.ems.accessibilityenabler/.MainActivity -e 'coordinates' '[[x1, y1], [x2, y2], [x3, y3]]' --el 'startdelay' '<delay-before-in-milliseconds>' --el 'inputdelay' '<delay-between-in-milliseconds>'"
```

Intent as a Stage Now XML:

```xml
<wap-provisioningdoc>
  <characteristic version="10.5" type="Intent">
    <parm name="Action" value="StartActivity" />
    <parm name="ActionName" value="android.intent.action.MAIN" />
    <parm name="Package" value="com.bluefletch.ems.accessibilityenabler" />
    <parm name="Class" value="com.bluefletch.ems.accessibilityenabler.MainActivity" />
    <characteristic type="Extra">
      <parm name="ExtraType" value="string" />
      <parm name="ExtraName" value="coordinates" />
      <parm name="ExtraValue" value="[[x1, y1], [x2, y2], [x3, y3]]" />
    </characteristic>
    <characteristic type="Extra1">
      <parm name="Extra1Type" value="long" />
      <parm name="Extra1Name" value="startdelay" />
      <parm name="Extra1Value" value="<delay-before-in-milliseconds>" />
    </characteristic>
    <characteristic type="Extra2">
      <parm name="Extra2Type" value="long" />
      <parm name="Extra2Name" value="inputdelay" />
      <parm name="Extra2Value" value="<delay-between-in-milliseconds>" />
    </characteristic>
  </characteristic>
</wap-provisioningdoc>
```

Where `[xn, yn]` are placeholders *x, y* coordinates for button clicks, `<delay-before-in-milliseconds>` is a placeholder for the delay in milliseconds before touch events will start, and `<delay-between-in-milliseconds>` is a placeholder for the delay in milliseconds between each touch event.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/device-applications/accessibility-enabler.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.