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

# Accessibility or Consistency

Wherls is built with the vision of making Web3 technology accessible to everyone — regardless of technical background, location, or device. The platform’s design prioritizes user inclusivity, visual clarity, and consistent performance across environments.

&#x20;

🌍 **Global Accessibility**

* **Device-Agnostic Design:**

Wherls works seamlessly across desktops, tablets, and smartphones, ensuring users can access their assets and features anytime, anywhere.

* **Multilingual Support (Planned):**

To cater to a diverse user base, future versions of Wherls will include support for major languages beyond English.

* **Wallet Compatibility:**

Users can access Wherls with MetaMask, Trust Wallet, WalletConnect, and more — making onboarding easier for both crypto newcomers and pros.

&#x20;

🧩 **Consistent User Experience**

* **Unified Interface:**

Whether buying an NFT, staking tokens, or claiming rewards, the interface remains consistent in layout and behavior to minimize learning curves.

* **Design Standards:**

All UI elements follow responsive design principles, ADA-compliant color contrast, and universal iconography to ensure usability for all.

* **Performance Optimization:**

Page loads, NFT rendering, and wallet connections are optimized for speed, even under high traffic.

&#x20;

By placing users at the center of its product design, Wherls bridges the gap between decentralized infrastructure and mainstream user expectations — ensuring that blockchain technology is not only powerful but also practical.


---

# 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://wherls.gitbook.io/wherls/accessibility-or-consistency.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.
