Skip to content
Anslation

Accessibility

Accessibility statement

Anslation wants its public website to work for everyone, including people who use a keyboard, a screen reader, zoom, or reduced motion. This statement says what the site does today, where it still falls short, and how to tell us about a barrier.

Last reviewed 25 October 2026. This is our own assessment: the site has not had an independent accessibility audit yet.
  • Our target

    We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across the public website.

  • What works today

    A skip link, visible keyboard focus, clear page landmarks, text alternatives for photos, and respect for reduced motion.

  • Tell us about a barrier

    If a page is hard or impossible to use, email support with the page, what you tried to do, and what you use to browse.

Statement

Where the site stands today.

Our target, what the public pages already do, what we know still falls short, and how to reach us.

Our target

We design and check the public website against WCAG 2.2 level AA. It is the standard we work toward, not a claim that every page meets it today.

  • This statement covers the public company website: the home page and the company, help, policy, and resource pages.
  • Signed-in product workspaces, such as Anslation One, Ansi, the Store, and Creators, have their own interfaces and are not assessed in this statement yet.
  • Where a page falls short of the target, we treat it as a fault to fix, not as an exception.

What the site does today

These are features of the public pages as they are built now.

  • A "Skip to content" link is the first thing the keyboard reaches on a page, and it moves focus to the main content.
  • Each page has one header, one main region, and one footer, and declares its language, so screen readers can move between the parts of a page.
  • Links and buttons show a visible focus style when you reach them with the keyboard.
  • Photos carry text alternatives, and purely decorative graphics are hidden from screen readers.
  • Animations and moving effects stop when your device is set to reduce motion.

Known limitations

Some parts of the site still fall short. We would rather tell you than have you find out the hard way.

  • The public pages use one light colour scheme. There is no dark theme or high-contrast option on these pages yet.
  • Some diagrams and sample product windows are illustrations. The text around them explains their point, but they are not always described in full.
  • Services from other companies that we link to or use, such as sign-in providers or payment pages, may not meet the same standard.
  • Because the site has not had an independent audit, there may be barriers we have not found yet.

How to report a barrier

If something on the site is hard or impossible to use, please tell us, and say if you need the content in another way.

  • Email support@anslation.com, or use the request form on the Support page.
  • Include the page address, what you were trying to do, and the device, browser, and any assistive technology you use.
  • You do not need an account to send a report by email.

Review of this statement

This statement was last reviewed on 25 October 2026.

  • We review it when the site changes in a way that affects accessibility, and when a known limitation is fixed.
  • A fixed limitation is removed from the list above; a newly found one is added.

Accessibility FAQ

Common questions about accessibility.

Short answers about the standard we work toward and how to report a problem.

Does the Anslation website meet WCAG 2.2 level AA?

It is our target, and we design and check the public pages against it. The site has not had an independent audit, so we do not claim full conformance; the statement lists the limitations we know about.

How do I report an accessibility problem?

Email support@anslation.com, or use the request form on the Support page. Include the page address, what you were trying to do, and the device, browser, and assistive technology you use.