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

# Introduction

Addressing accessibility needs in OpenActive

Accessibility is a central concern for OpenActive: our mission is to use open data to get more people more active. In a world where [more than 80%](https://www.channel4.com/programmes/how-to-beat/on-demand/70184-001) of disabled people feel that gyms are unwelcoming, that means doing everything we can to give them more information about the support that's available to them - including driving improvements to industry best practice in data-gathering and publication.

However, improving the quantity and quality of data related to accessibility presents several challenges, including

* lack of consistency in how data is gathered
* lack of consistency in how data is communicated
* varying and evolving understandings of 'disability' and 'accessibility'&#x20;
* differences in the extent to which individuals identify as 'disabled'
* blurry lines between accessibility and other health-related needs
* the highly-bespoke nature of much accessibility information

The challenge, then, is to create a data model that is sufficiently well-defined to capture adequate accessibility information and encourage good practice, while remaining flexible enough to accommodate the evolving understandings and wide range of needs confronting individuals with enhanced accessibility requirements.


---

# 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://tutorials.openactive.io/accessibility/master.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.
