1. Scope and current status
This statement covers the public Sytance website and the hosted Sytance application operated by Sytance Technologies Limited.
We are working toward a more accessible experience but do not currently claim that every page, workflow, generated document, or third-party integration fully conforms to WCAG 2.2 Level AA. Accessibility is treated as an ongoing product and content responsibility rather than a one-time declaration.
2. Our approach
Our accessibility work is guided by the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We use these criteria when designing new public pages and materially changing core product workflows.
Priorities include semantic structure, labelled controls, keyboard operation, visible focus, text alternatives, colour contrast, browser zoom, text sizing, status communication, and error identification.
3. Testing and compatibility
We combine component and code review with keyboard checks, browser zoom and text-size checks, automated accessibility testing where appropriate, and manual review of important workflows.
The experience may vary by operating system, browser, assistive technology, language, and the complexity of Customer Content. For the best available experience, use a current version of a major browser and keep assistive technology up to date where practicable.
4. Known limitations
Complex data-flow diagrams, architecture editors, large interactive tables, rich-text editing, and generated documents may not yet provide an equivalent experience with every assistive technology. The accessibility of Customer Content also depends on source material supplied by the customer.
Some third-party pages or embedded services are controlled by their providers. We consider accessibility when selecting and integrating services, but we cannot directly remediate every third-party interface.
5. Tell us about a barrier
Email support@sytance.com with the affected page or feature, the barrier you encountered, and any adjustment or alternative format that would help. Do not include passwords, authentication tokens, or unnecessary sensitive information.
We aim to acknowledge an accessibility report within five business days and then provide a practical response, workaround, alternative format, or remediation update where reasonably possible. Complex product changes may take longer, and we will explain the next step when we can.
6. Review of this statement
We review this statement as the website, application, testing approach, and known limitations change. The date above identifies the current published version.