# Accessibility Statement Accessibility in Virusis is not only a design preference. It matters especially for documentation readability and result-screen usability. ## Target areas * meaningful heading structure * keyboard navigation * screen-reader-friendly labeling * sufficient contrast * understandable content and action order ## Current signals The product already reflects: * route-based public pages * accessible form labeling * SSR and hydration support * content-oriented public SEO pages as decisions that support accessibility. ## What is still missing This still does not equal a formal WCAG compliance report. Manual accessibility testing should happen before publication. No verified accessibility feedback channel is currently published in this help center. That channel should be defined before the site is published. --- # 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://docs.virusis.com/legal/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.