AffectlyBack to home

Accessibility Statement

Last updated: August 17, 2026

Where we stand

Affectly is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most of the standard is met but some parts are not. We would rather tell you exactly what we have and have not checked than claim a clean bill of health we cannot evidence.

1. Our Commitment

Affectly exists to make learning work for people whose brains work differently. An inaccessible learning tool would contradict the whole point of the product, so accessibility is something we treat as part of the feature, not a box to tick afterwards.

We aim to meet WCAG 2.1 Level AA, the standard referenced by the Australian Disability Discrimination Act guidance, the EU Web Accessibility Directive and European Accessibility Act, the UK Equality Act, and the US ADA.

2. Accessibility Features We Have Built

  • "How I learn" presentation modes: you can have Ari's answers rearranged into chunks of one idea each or numbered steps, without changing what Ari says.
  • Reduced motion: we respect your operating system's "reduce motion" setting, and offer a calm mode that removes animation independently of it.
  • Read along audio: Ari's replies can be spoken aloud, with the message highlighted while it is being read.
  • Focus mode: strips decorative colour and movement from the lesson surface for easier concentration.
  • Larger text and spacing: an increased reading comfort mode for longer passages.
  • Keyboard navigation and visible focus indicators throughout the public pages.
  • Semantic headings and landmarks so screen readers can navigate structure.

3. How We Measure This, and What It Does Not Cover

We maintain an automated axe-core accessibility test. It checks WCAG 2.1 A and AA rules at both a mobile and a desktop viewport width, and it fails rather than merely warns when it finds a violation. It currently covers our public, signed out pages (home, pricing, about, login, signup and the legal pages) and also a live guest lesson, which exercises the tutor chat itself. At the last run, all of those passed at both widths.

To be precise about the limits of that: the test is run by hand rather than automatically on every change, so it catches problems when we run it, not the moment they are introduced. Wiring it into our automated checks is on our list.

Please read this part honestly with us

  • Automated testing finds roughly a third of real accessibility problems. A passing scan is a floor, not proof the product is usable.
  • It says nothing about whether someone using a screen reader can actually complete a task end to end. That needs a person, and we have not yet commissioned a formal audit with assistive technology users.
  • Parts of our signed in experience (the dashboard, flashcards, courses and settings) are not yet covered by the automated scan. The tutor chat is covered, because a guest lesson is in scope.
  • We have not been independently audited or certified by a third party.

4. Known Limitations

We are aware of the following and are working on them:

  • Charts and analytics. Our emotion trend and progress charts are visual and do not yet have a complete text or table alternative.
  • Generated certificates. Course completion certificates are produced for printing and are not tagged for screen readers.
  • Read along highlighting is per message, not per word. Our speech provider does not report word boundaries, so we highlight the whole message being spoken rather than tracking individual words.
  • Third party screens. Payment pages are hosted by Stripe and the App Store; their accessibility is theirs to control, not ours.

5. Tell Us About a Problem

If any part of Affectly is difficult or impossible for you to use, please tell us. We treat it as a bug, not a feature request.

Email origae.dev@gmail.com. Please describe what you were trying to do, what got in the way, and the assistive technology and browser you were using if that applies.

  • We aim to acknowledge within 5 business days and to tell you what we plan to do within 20 business days.
  • If we cannot fix something quickly, we will offer you the information or function another way in the meantime, including by email or in a plain text format if that is easier for you.

6. Escalating

If you are not satisfied with our response, you can raise it with the accessibility or antidiscrimination body where you live. In Australia, the Australian Human Rights Commission at humanrights.gov.au. We would much rather hear from you first and fix it.

7. For Procurement: Conformance Report

If you are assessing Affectly for an institution, we publish a full Accessibility Conformance Report (VPAT® 2.5, WCAG Edition). It works through all 50 WCAG 2.1 Level A and AA success criteria individually, states our evaluation methods, and marks criteria we have not tested as "Not Evaluated" rather than assuming a pass.

We can supply it as a PDF, or complete your own accessibility questionnaire, on request.

8. Related Policies

See also our Privacy Policy and Terms of Service.