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

# Accessibility

<figure><img src="/files/BnbUfw1NAdpd26QAaFoO" alt=""><figcaption></figcaption></figure>

Our design system is founded on inclusive design principles, ensuring our products are usable by everyone, reflecting the full range of human diversity. We commit to:

1. **Human-Centered Design**: Our success is gauged by our ability to meet diverse user needs and preferences.
2. **Collaborative Co-Design**: We engage with users of all abilities as co-designers to ensure our products are accessible and intuitive.
3. **Adaptive Innovation**: Our design process is flexible, responsive to user feedback, and recognizes the complexity of integrating accessibility into a dynamic technological landscape.

**Key Commitments**:

* **Edge User Expertise**: We integrate the insights of 'edge users' directly into our design process, valuing their unique contributions to creating functional and accessible products.
* **Accessible Tools**: Our design practices and tools are accessible, promoting contribution from all team members.
* **Openness**: We champion open standards to foster compatibility and extension by a broad community.
* **Iterative Design**: Our approach is iterative, rapidly adapting to include new requirements and scenarios to better serve user needs.

Resources:\
\- [Floe Project](https://handbook.floeproject.org/perspectives/the-three-dimensions-of-inclusive-design-part-one/)


---

# 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://docs.agora.foundation/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.