> For the complete documentation index, see [llms.txt](https://sign-language-center.gitbook.io/tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sign-language-center.gitbook.io/tech/problem-to-solve.md). # Problem to Solve According to the World Health Organization (WHO), over **1.5 billion** people globally experience some degree of hearing loss, with approximately **430 million** requiring rehabilitation for disabling hearing loss. In addition, the World Federation of the Deaf estimates that around **70 million** deaf people use sign language as their primary means of communication. This is not a small number. Despite it, everyday communication between signers and non-signers remains difficult. ## The challenges ### Communication barriers Most people do not know sign language. Simple interactions such as ordering food, asking for directions or talking to a colleague can become frustrating or impossible without help. ### Limited access to interpreters Professional interpreters are valuable but scarce, often expensive, and usually need to be booked in advance. They are rarely available for spontaneous, day-to-day conversations. ### Few accessible learning tools People who want to learn sign language, including family members, friends and teachers of deaf people, often lack affordable, interactive resources that give feedback on their signing. ### Exclusion from public life When communication is hard, participation in education, work, public events and online spaces suffers. ## Our approach Sign Language Center applies AI to these problems with a tool that is **free**, **compact** and **convenient**: real-time translation of signs, an AI agent that teaches sign language with instant feedback, and AI voice generation so that signers can speak through the system. --- # 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://sign-language-center.gitbook.io/tech/problem-to-solve.md?ask=&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.