> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/product-finders/accessibility.md). # Accessibility Product Finder follows WCAG standards and is compliant with ADA requirements, ensuring all customers can navigate and complete questionnaires using assistive technologies. ## Key features **Keyboard and screen reader support** * Full keyboard navigation with clear focus indicators * Screen readers announce progress, question context, and option selections * Alternative text for all images and interactive elements **Visual accessibility** * Sufficient color contrast ratios * ARIA labels on interactive thumbnails and controls * Progress information with percentage values for assistive technologies {% hint style="info" %} If you encounter accessibility issues or have specific requirements, please contact your Customer Success Manager. We're committed to making Product Finder experiences inclusive for all users. {% endhint %} --- # 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://docs.crobox.com/how-to-guides/product-finders/accessibility.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.