Skip to content
Choose a language: EN
Menu

Accessibility statement

Version 1. This statement was drawn up on 6 October 2026. It applies to Algia, at algia.be and app.algia.be, and to the summaries and exports made with it.

In short

  • We aim for WCAG 2.2 level AA throughout Algia.
  • Every page is tested automatically, in Dutch, English and French, and the main flows by keyboard.
  • We know of a few limitations. They are listed below, with what replaces them.
  • Something not working for you: write to support@algia.be.

1. Our commitment

Huskii VOF wants everyone to be able to use Algia, including on a bad day, one-handed, with a tremor, with a screen reader or with large text. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, which is also the level the European standard EN 301 549 refers to.

2. How we test

  • The public pages and the application screens for registering, signing in, security and the diary are checked with axe-core in a real browser, in all three languages, against the WCAG A and AA rules. A violation fails the build.
  • Keyboard use is part of the browser tests, and recording an entry is walked through with the keyboard alone.
  • We check that pages work at a width of 320 pixels and at 200% zoom without losing content or function.
  • We check that touch targets are at least 44 by 44 pixels.
  • Animation stops when your device asks for reduced motion.
  • Contrast is set in the colour system itself, for the light and the dark theme, so a single screen cannot break it.

3. What we built for it

  • Every form field has a visible label, and an error is described in text next to the field it concerns.
  • Each page declares its language, so a screen reader pronounces Dutch as Dutch and French as French.
  • Colour never carries meaning on its own: the body map and charts always show a number or a word too.
  • The summary for a consultation is a tagged PDF (PDF/UA), which a screen reader can read in order.

4. Known limitations

  • The drawn body map is decorative for assistive technology. The list of body regions next to it is the accessible equivalent, with real checkboxes, and is the form itself: what you tick there is what is saved.
  • Charts are drawings. Each chart has a data table with the same numbers, which is the accessible equivalent.
  • The summary for a consultation shows regions as a table, not as a drawing of the body.
  • A test with a screen reader by a person has not been done yet for every flow. The automatic tests do not catch everything, so this statement may still miss a problem.
  • A signed-in session ends after 30 minutes without activity, to protect your diary on a shared device, with a warning five minutes before. Something not yet saved may then have to be entered again.
  • Paying and managing a subscription happen on Stripe's own pages, which we do not control.
  • Reminders on an iPhone only work once Algia is added to the home screen. This is a limit of the iPhone, not of accessibility, but it adds steps.

5. Reporting a problem

Write to support@algia.be. Tell us which page or screen, what you wanted to do, and, if you like, which browser or assistive technology you use. We answer every report, and if something cannot be fixed quickly we help you get what you needed another way.

6. Enforcement

If our answer does not satisfy you, you can turn to the FPS Economy (FOD Economie / SPF Economie), which supervises the European Accessibility Act in Belgium: economie.fgov.be.

7. About this statement

This statement was drawn up on 6 October 2026, based on our own testing. We review it every quarter and whenever Algia changes in a way that affects it.