> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/add-ons/website-accessibility.md).

# Website Accessibility

{% embed url="<https://doctorlogic.wistia.com/medias/9o6in3ly9r>" %}

Website accessibility is of paramount importance as it ensures that digital content and services are available to all individuals, regardless of their abilities or disabilities. A truly accessible website accommodates a diverse range of users, including those with visual, auditory, motor, or cognitive impairments. This inclusivity not only aligns with ethical principles of equality and non-discrimination but also adheres to legal requirements in many jurisdictions. Moreover, an accessible website enhances user experience for everyone, as it considers various devices, browsers, and assistive technologies that people may use to access the internet. By prioritizing website accessibility, businesses and organizations foster a more inclusive online environment, reaching a broader audience and demonstrating a commitment to social responsibility. Ultimately, the significance of website accessibility lies in its ability to break down digital barriers and provide equal opportunities for information and interaction, fostering a more inclusive and equitable online landscape.

Ready to make sure your website is fully accessible for visitors?&#x20;

**Contact your CSM today to ask about adding this important service.**&#x20;

{% content-ref url="/pages/Hkecq1Ax8z1BewLgMH0U" %}
[The Customer Success Manager](/docs/contact-support/the-customer-success-manager.md)
{% endcontent-ref %}


---

# 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://help.doctorlogic.com/docs/add-ons/website-accessibility.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.
