Accessibility statement.

Our commitment

We're committed to making TextSight accessible to people of all abilities, including those who use assistive technologies. Accessibility is an ongoing effort — we keep improving the product as we go.

Standard we aim for

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. WCAG is built around four principles — content should be perceivable, operable, understandable, and robust. We use these as our target, and we test against them as we build.

What we support

• Keyboard navigation — core flows can be operated without a mouse.
• Screen-reader support — semantic HTML, labels on form controls, and meaningful link text.
• Colour contrast — we aim for AA-level contrast for text and important UI.
• Responsive layouts — pages reflow for zoom and small screens.
• Reduced motion — we respect the operating-system "reduce motion" preference.

Known limitations

We're a small team and some areas may not yet fully meet our target — for example, complex interactive results views and some third-party embedded widgets (such as live chat or payment fields) are partly controlled by their providers. If you hit a barrier, please tell us and we'll prioritise a fix or provide an alternative way to get what you need.

Give us feedback

If you experience any difficulty accessing part of TextSight, email hello@textsight.ai with the page and the problem, and we'll respond and work with you on an alternative. Your feedback directly helps us improve.