Monizze

Accessibility at Monizze

Last updated: 30 June 2026

Digital accessibility, in two sentences

Digital accessibility means making sure a website, an application or a document can be used by everyone, including people with a disability: visual, auditory, motor or cognitive, whether that disability is permanent, temporary or situational.

In concrete terms, this means a person should be able to:

  • read content even with low vision, thanks to sufficient contrast;
  • navigate without a mouse, using the keyboard alone;
  • understand a page read aloud by a screen reader;
  • complete a form without getting stuck.

Our commitment

We see accessibility not as a regulatory constraint, but as a condition of our work. We are committed to making our digital services perceivable, operable, understandable and robust for as many people as possible, and to improving continuously.

This commitment translates into concrete actions:

  • building accessibility in from the design of our pages and products;
  • checking our services regularly and correcting the gaps we identify;
  • raising awareness and training our teams;
  • offering an accessible alternative to anyone who requests one.

Conformance status

The public website monizze.be is, at this time, partially conformant with level AA of the Web Content Accessibility Guidelines (WCAG 2.2).

Several criteria are met, but an initial assessment has identified points to correct, listed below. As long as these gaps remain and as long as the full manual evaluation has not been carried out, we do not claim full conformance.

Reference framework used:

  • the WCAG 2.2 guidelines, level AA, the international reference for digital accessibility;
  • the European harmonised standard EN 301 549;
  • the European Accessibility Act (European Directive 2019/882), transposed into Belgian law by the Belgian Act of 5 November 2023.

Scope covered

This statement covers the public website monizze.be, in its French, Dutch and English versions.

Our logged-in environments are not yet covered by this statement:

  • the beneficiary space MyMonizze;
  • the employer space (Client Area);
  • the benefits platform Dealzz;
  • the flexible compensation platform RewardFlex;
  • the merchant network map;
  • our mobile application.

These services are the subject of a separate assessment. We will extend the statement as their audit progresses, rather than claiming coverage we would not have verified.

What is already in place

Several accessibility foundations are present on the website:

  • the language of each page is correctly declared, which allows screen readers to render it properly;
  • each page has a descriptive title;
  • the pages rely on a semantic structure (header, navigation, content, footer) rather than on a stack of neutral blocks;
  • the contact form fields display a visible label.

These points form a healthy basis, but do not amount to conformance: they have not yet been confirmed by a full manual evaluation.

Content not yet accessible

The following limitations have been identified on the website and are being addressed. For each one, we indicate what it changes for you and the technical criterion involved.

Insufficient colour contrast

  • What this changes: in some places, text lacks contrast and is hard to read, particularly for people with low vision. This is the case with our brand orange when it is used as a text colour (section titles, highlighted figures, certain links). On mobile, the indicator of the site's active language also appears light on a light background, which makes it nearly invisible.
  • WCAG criteria: 1.4.3 Contrast (Minimum) (AA); 1.4.11 Non-text Contrast (AA).
  • Our fix: reserve light orange for decorative areas and use a dark, legible variant for text; correct the background of the language selector on mobile.

Contact form

  • What this changes: on the contact form, the field labels are not correctly linked to the input areas for screen readers, and the required nature of certain fields is not conveyed in a way assistive technologies can use. Autofill for personal fields is not offered either.
  • WCAG criteria: 3.3.2 Labels or Instructions (A); 1.3.1 Info and Relationships (A); 4.1.2 Name, Role, Value (A); 1.3.5 Identify Input Purpose (AA).
  • Our fix: link each label to its field, signal required fields with a technical attribute, and enable autofill assistance.

Structure and navigation landmarks

  • What this changes: the internal structure of certain pages contains duplicate navigation landmarks, which can disorient people who navigate by region with a screen reader. Several sets of links (language selector, link lists, app badges, footer) are also not marked up as lists, which deprives the screen reader of their number and their grouping. Finally, the organisation of the headings shows, on some pages, inconsistencies in level.
  • WCAG criteria: 1.3.1 Info and Relationships (A).
  • Our fix: keep only one main content region and one footer per page, mark up the sets of links as lists, and restore a continuous heading hierarchy.

Cookie banner

  • What this changes: the cookie banner, supplied by a third party, has a structural anomaly and can display in English on our French-language pages, which harms comprehension and speech output.
  • WCAG criteria: 1.3.1 Info and Relationships (A); 4.1.2 Name, Role, Value (A); 3.1.2 Language of Parts (AA).
  • Our fix: we have reported these anomalies to our provider for correction.

PDF documents

  • What this changes: some documents made available in PDF format (general terms and conditions, data processing agreement) have not yet undergone an accessibility check; their conformance is not guaranteed at this time.
  • Our fix: these documents will be audited and brought into conformance, or offered in an accessible alternative form on request.

Preparation of this statement

Method and tools used:

  • automated checking, cross-referenced with several independent tools: axe-core, pa11y (WCAG2AA standard), Lighthouse, and the accessibility checking tool of the Belgian federal administration (BOSA), run on the main pages (home, product page, contact, privacy);
  • analysis of the pre-rendered HTML code of the pages (structure, navigation landmarks, headings, language attribute, contact form);
  • verification of the colour contrast ratios on the measured values, according to the WCAG thresholds (4.5:1 for normal text, 3:1 for large text and interface components).

The most significant defects (brand orange, contact form, language selector, duplicated structure) are confirmed by several of these tools, including the official Belgian tool.

Our improvement plan

We have started a prioritised correction process:

  • Short term: correct the colour contrasts, restore the display of the language selector on mobile, link the contact form labels and signal required fields, remove the duplicate navigation landmarks. Most of these defects come from the shared template: a fix at the template and design system level corrects several pages at once.
  • Medium term: carry out the full manual evaluation (keyboard and screen reader), reduce the layout shifts when certain pages load, revise the heading hierarchy, have the cookie banner corrected by our provider.
  • To be planned: accessibility audit of the PDF documents, then extension of the process to the logged-in environments and the mobile application.

Reporting a problem

If you run into a difficulty accessing content or using a feature of our services, let us know. We will look for a solution with you and, if necessary, provide the content concerned in an accessible form.

Means of redress

If our response does not satisfy you, or in the absence of a response from us, you can refer the matter to the competent authority. In Belgium, this is the Economic Inspectorate of the FPS Economy. You can submit a report through its Contact Point, available on economie.fgov.be.