SASSU

Accessibility Statement

Last updated: 29 October 2026

Sassu aims to be usable by anyone who wants to train, including if you have low vision, do not use a mouse, work with a screen reader, or have trouble with moving images. Below is where we stand — including the things that do not work well yet, because a statement without that list says nothing. The Dutch version is the leading text; this is a translation.

1. What does this statement cover?

The website sassu.fit and the app app.sassu.fit, including the coach side. Both belong to Jayyletsgetfit, the Netherlands, trading as Sassu.

2. The standard we follow

We follow the Web Content Accessibility Guidelines (WCAG) 2.1, level AA. That is the standard used as the baseline in the Netherlands and across the EU.

3. Where we stand now

Status: partially compliant.

We say this plainly for one reason: no independent audit has been carried out. Nobody outside our team has tested Sassu against WCAG 2.1 AA, and we have not walked every tab of the app with a real screen reader. What follows is what we checked in our own code ourselves on 29 October 2026. There may therefore be problems that are not on this list.

4. What does not work well yet

These are the limitations we established ourselves. Each one is named with its reason, not lumped into a catch-all.

• Charts and progress lines have no text alternative. Your weight trend, your mood chart and the strength lines are drawn shapes. A screen reader reads nothing from them, and there is no table or summary alongside. The underlying numbers are in the app and in your data export.
• The Gym section sits in an embedded frame. For technical reasons the workout player is its own page inside the app. Stepping into and out of that frame with a keyboard or screen reader is messier than elsewhere in the app.
• Photos you upload yourself get a generic description. A progress photo or a meal photo carries the text “progress photo”, not a description of what it shows. There is no field yet where you can type your own description.
• There is no ‘skip to content’ link. If you work with a keyboard, you pass through the navigation before you reach the content of a tab.
• Not every tab has been walked with a screen reader. The app is large and grows fast. We do not know for every screen whether all buttons and fields carry a good name.

5. What does work

This was checked too, not assumed:

• Reduced motion. If your phone or computer is set to show less movement, Sassu leaves out its animations and transitions. That applies to the app, the workout player and the website.
• A dark and a light theme. You choose Day or Night in Settings; the app forces neither.
• Reordering works without dragging. Moving exercises and programme items can be done with ‘Move up’ and ‘Move down’ buttons, not only by drag-and-drop.
• Pages declare their language. Dutch pages are marked as Dutch and English pages as English, so a screen reader pronounces them correctly.
• Your data comes with you. Settings has an Export my data button. If a screen does not work for you, you can always take your data out yourself.

6. Reporting a problem

If you run into something — a button you cannot reach, text you cannot read, a screen that does not work with your assistive technology — email info@sassu.fit. Tell us which screen it is and which tool or setting you use, so we do not have to ask back.

We respond within five working days. That is an answer from a person: what we see, whether we can fix it, and when. If we cannot fix it quickly we will say so, and look with you for a route that does work.

If you are not satisfied with our response, you can turn to the Netherlands Institute for Human Rights.

7. How this statement came about

Drawn up on 29 October 2026 on the basis of our own review of our code, carried out by the team that builds Sassu. No external party, no user testing sample. We update this page whenever we have resolved an item from section 4 or come across a new one.