# UpScalp Help Center Accessibility Statement **Last reviewed:** 2026-05-22. UpScalp help pages should be readable, scannable, and usable for Lite, Premium, and approved Private Beta users. ## Current accessibility approach The Help Center aims to use: 1. Plain language. 2. Clear headings. 3. Short paragraphs. 4. Descriptive links. 5. Consistent terms across pages. 6. Task-focused lists. ## Current limitations The Help Center is published through GitBook, so some layout, navigation, theme, export, and formatting behavior may depend on GitBook platform settings. If a page is hard to read or use, report the page URL, device, browser, and specific issue so it can be reviewed. ## Report an accessibility issue Send: 1. Page title and URL. 2. Device and browser. 3. What was hard to read or use. 4. Screenshot if useful. 5. Whether the issue affected setup, support, or trading-risk understanding. Use [Contact Support](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-contact-support) for the support route. ## Related 1. [Contact Support](https://upscalp.gitbook.io/upscalp-docs/troubleshooting/upscalp-contact-support) 2. [Official Links and Channels](https://upscalp.gitbook.io/upscalp-docs/reference/upscalp-official-links) --- # Agent Instructions: 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://upscalp.gitbook.io/upscalp-docs/trust-and-safety/upscalp-accessibility-statement.md?ask= ``` 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.