> For the complete documentation index, see [llms.txt](https://rainbowforward.gitbook.io/lgbtqia+-affirming-toolkits/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rainbowforward.gitbook.io/lgbtqia+-affirming-toolkits/access-to-justice-toolkit/section-1/what-does-access-to-remedies-mean.md). # What does Access to Remedies mean? If human rights violations go unaddressed, they could enable further violations leading to an environment of impunity. To avoid this, rights holders must be able to seek remedies from the duty bearers when human rights violations occur. Remedies can take many forms, including a process before an independent authority, compensation, restoration of rights, an apology, or other means of redressing a violation. These measures can be punitive or non-punitive, but most importantly they have to be effective. Access to effective remedies is the barometer to measure how seriously states and other entities take their human rights commitments. Additionally, having an effective system to deliver remedies to violations of human rights can serve as an effective deterrence for further human rights abuses. Furthermore, an effective remedies system will allow oversight bodies and other complaint mechanisms to address structural issues that contribute to discrimination and other human rights violations. It is important to note that non-judicial remedies such as public apologies, public memorials, and guarantees of non-repetition should not be used as substitutes for investigations and prosecutions of perpetrators when human rights violations occur. --- # 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://rainbowforward.gitbook.io/lgbtqia+-affirming-toolkits/access-to-justice-toolkit/section-1/what-does-access-to-remedies-mean.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.