> For the complete documentation index, see [llms.txt](https://neural.akshayajagekar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://neural.akshayajagekar.com/introduction/accessibility.md).

# Accessibility

{% hint style="info" %}
**Good to know:** Accessible design lets people of all abilities interact with, understand, and navigate our products.
{% endhint %}

{% tabs %}
{% tab title="Introduction" %}
Accessibility means that people can do what they need to do in a similar amount of time and effort as someone fully abled. It means that people are empowered, can be independent, and will not be frustrated by something that is poorly designed or implemented.
{% endtab %}

{% tab title="Our Approach to Accessibility" %}
Here at our product we comply to all levels of accessibility sagittis lacus vel augue laoreet rutrum faucibus dolor auctor. Cras mattis consectetur purus sit amet fermentum. Fusce dapibus, tellus ac cursus commodo, tortor mauris condimentum nibh, ut fermentum massa justo sit amet risus. Donec id elit non mi porta gravida at eget metus.
{% endtab %}
{% endtabs %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://neural.akshayajagekar.com/introduction/accessibility.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.