> For the complete documentation index, see [llms.txt](https://ressources.technoculture.club/riso/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ressources.technoculture.club/riso/a-propos-de-cette-ressource/accessibilite.md). # Accessibility **Prerequisites:** * Knowledge of print media (lithography, mimeography, screenprinting, etc.) * Knowledge of bookmaking * Knowledge of graphic design **Accessibility Barriers:** * Mobility: Studio space with a Risograph should accomodate for wheelchair accessibility. Height of the Risograph may be difficult for certain users to use * Vision: The screen on the Risograph can not be changed in size and can be inaccessible for certain people * Equipement/Technical: Access to a graphic design software, a computer, and paper material should be provided **Activities:** * Activities with a Risograph are accessible for people capable of hands-on activities but can also be accessible for those comfortable using the computer for designing. It is also possible to make hand copies of designs. * Time sensitivity: Print is a medium that requires a lot of time * Access to a large indoor space that has a studio space set up --- # 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://ressources.technoculture.club/riso/a-propos-de-cette-ressource/accessibilite.md?ask=&goal= ``` `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.