> For the complete documentation index, see [llms.txt](https://docs.nemus.earth/nemus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nemus.earth/nemus-docs/nemus-litepaper/nemus-technology/the-nemus-web-application/accessibility-and-scalability.md).

# Accessibility & Scalability

To reach the world at large, the Nemus application is designed and developed using the latest WCAG standards while also leveraging AI translation technology to support over 25 different languages across the globe.

The interface is driven by modern Javascript based technologies such as React, Typescript, Ionic, and a WebGL powered mapping solution by MapBox. The API is powered by an array of sophisticated technologies such as Go, Terraform, MongoDB, and PostgreSQL to support real world GeoJSON data. All of which have a deep relational connection with an array of smart contracts to support all blockchain-related interactions.

As Nemus expands, the application will scale to accommodate millions of Guardians and implementation of new features. It will become a web3 hub, interacting across chains and providing a multitude of functions to serve utility for NFTs, the NEA token, and the Nemus DAO.


---

# 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:

```
GET https://docs.nemus.earth/nemus-docs/nemus-litepaper/nemus-technology/the-nemus-web-application/accessibility-and-scalability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.