> 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/getting-involved.md).

# Getting Involved

Contributing to the OpenActive Accessibility standard

OpenActive welcomes contributions from the community - particularly with regard to accessibility. There are a variety of channels available for feeding back on our specification, depending on the nature of the feedback and the level of commitment this entails.

Individuals wishing to comment upon or contribute to the accessibility specification may do so by:

* technical comments and proposals related to the accessibility standard in general can be raised as issues on the GitHub [accessibility-draft repository](https://github.com/openactive/accessibility-draft/issues)
* if your contribution specifically concerns the Participant Condition Supported Vocabulary, issues and proposals can be raised in the dedicated [participant-condition-supported repository](https://github.com/openactive/participant-condition-supported/issues)
* if you want to take an active role in defining and setting the direction of the standard, you can join the [W3C OpenActive Community Group](https://www.w3.org/community/openactive/)
* or you can just email us with any other comments or concerns you might have, at **<hello@openactive.io>**

OpenActive particularly welcomes feedback from individuals with disabilities and organisations dedicated to advocacy in this area.

f you find any of these channels to be inaccessible in any way and have suggestions on how we can improve this, please let us know via <hello@openactive.io>.  We try to be as inclusive as possible, and are always open to improvement.


---

# 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/getting-involved.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.
