1. Our commitment

Thorbis is committed to making its platform usable by as many people as possible, including people who use assistive technologies such as screen readers, screen magnifiers, voice-control software, and keyboard-only navigation.

We treat accessibility as part of building a quality product, not a one-time project. As we add and change features, we aim to keep them usable for everyone who relies on our platform.

2. The standard we work toward

We aim to align with the Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2 at Level AA as a target that guides our work.

A target, not a certification

Accessibility is an ongoing effort, and we continue to improve. We do not claim full conformance with WCAG, and some areas may not yet fully meet Level AA. We describe known limitations below and work to address issues as we find them.

3. Measures we take

We build on a shared design system and work toward accessibility through measures such as:

semantic markup so the structure of pages and content is conveyed to assistive technologies;
keyboard navigability for interactive elements, so the platform can be operated without a mouse;
color contrast that we aim to keep sufficient using the colors and tokens in our design system;
visible focus states so it is clear which element is currently active;
labels and accessible names for buttons, links, form fields, and other interactive elements.

These measures describe how we approach accessibility; they are not a guarantee that every screen or feature meets them in every case.

4. Known limitations and third-party content

Some areas may not yet be fully accessible

Some content, integrations, or third-party components may not yet be fully accessible. This includes features we are still improving and components provided by Third-Party Services that we do not fully control. We work to address accessibility issues as we find them and as they are reported to us.

5. Feedback and accommodations

If you encounter an accessibility barrier on the platform, or if you need information in an alternative format, contact us at support@thorbis.com. Tell us what you were trying to do and the page or feature involved, and we will work with you to provide the information or service you need.

We treat accessibility feedback as a priority and use it to identify and fix issues.

6. Ongoing improvement and contact

We review the feedback we receive and update our platform and this statement over time as our practices and the underlying guidelines evolve.

For accessibility help and accommodations, contact support@thorbis.com. For legal questions about this statement, contact legal@thorbis.com.

Operating map

Translate the policy into an operational review

Legal pages should help buyers and administrators understand which workflow, approval, and retained record the document supports.

Workflow touched

Identify the product behavior this document governs before reviewing individual clauses.

Decision owner

Name who approves the workflow, exception, vendor review, or customer-facing disclosure.

Record to keep

Store the accepted version, review date, question trail, and any follow-up action in one place.

Review workflow

Use the document as an operating reference, not just a legal archive

Read the scope

Start with the document purpose, effective date, and category before reviewing the clauses.

Check the operating impact

Map the terms to the workflow they affect: data, payments, AI, messaging, content, or platform use.

Route questions

Send contract, privacy, security, abuse, DMCA, or support questions to the right inbox.

Request routing

Send the right question to the right Thorbis inbox

Legal noticeslegal@thorbis.com Privacy requestsprivacy@thorbis.com Security reviewsecurity@thorbis.com Platform abuseabuse@thorbis.com

Same category

Accessibility Statement