Skip to content
Tactigo
Log in

Accessibility

Tactigo is built to target WCAG 2.1 AA. A page that only says so is worth nothing, so this one sets out what a machine checks on every change, what a person checks by eye, and what has not been verified at all.

What is checked, and by what

The table covers all three surfaces: the player app, the analyst app, and this public site. The "not verified" rows would make a shorter and more confident page if they were deleted, and a useless one.

  • Colour contrast of text and background

    Standing
    Automated test
    How it is checked
    All 33 token pairs are measured on every CI run, in both light and dark appearance (WCAG 1.4.3 / 1.4.11). A colour below the threshold cannot be merged.

  • Text size inside form fields

    Standing
    Automated test
    How it is checked
    Every field is at least 16px. Below that, Safari on iPhone zooms the page on focus and you lose your place in the form. A smaller value fails a test.

  • Where the keyboard is, while you use it

    Standing
    Automated test
    How it is checked
    A focus outline is drawn on every screen from one shared rule, and that outline is one of the pairs the contrast check measures.

  • Japanese, English and German

    Standing
    Automated test
    How it is checked
    A string missing any of the three languages fails the build, so a screen cannot quietly fall back to a language you did not choose.

  • Tap targets of at least 44×44px

    Standing
    Built in, not tested
    How it is checked
    44×44px is a value in the design system and is checked by eye, screen by screen. Nothing measures it automatically.

  • Respecting "reduce motion"

    Standing
    Built in, not tested
    How it is checked
    If your device asks for reduced motion, animation stops across both apps from one shared rule. It is built in, not tested.

  • Completing a flow with the keyboard alone

    Standing
    Not verified
    How it is checked
    The screens are built from standard HTML elements, so most of them work, but no flow has been walked end to end with the keyboard only.

  • Using the service with a screen reader

    Standing
    Not verified
    How it is checked
    Labels are written per component, but nothing has been audited end to end with VoiceOver or TalkBack. This is the weakest point on this page.

  • Captions on video clips

    Standing
    Not verified
    How it is checked
    The short clips an analyst attaches to a report have no captions. The analysis itself is written text; the clips illustrate it.

Where this stands legally

The European Accessibility Act (Directive (EU) 2019/882) requires online services to meet accessibility requirements and to publish an assessment of how they do. Article 4(5) then exempts microenterprises providing services — fewer than 10 people and turnover or balance-sheet total of €2m or less — from those requirements and from every obligation attached to them. Ensologic, which operates Tactigo, is one, so there is no legal duty to publish this page today.It is published anyway because the exemption is a cliff rather than a slope: it disappears the moment the company crosses the threshold, with no transitional period. A statement written now, with four public pages and two apps, is one that gets maintained. One written against a deadline is one that gets bought.The reading of the law above is research as of 28 July 2026 and is not legal advice.

If something here shuts you out

Plainly: there is no contact address yet. The operating company is not registered, so there is no mailbox anyone reads. It will be added here and on the privacy page at the same time as the registration.An address that bounces is not going on the page about not shutting people out.

For how data is handled, see How we handle privacy.

Last updated: 28 July 2026