Accessibility statement

On this page, you will find information about how we handle accessibility at Monthio. We continuously update these statements in line with the development of accessibility.
Updated July 9, 2026

Information

This accessibility statement applies to all pages on flow.monthio.com or any subsequent customized URLs (hereinafter “the Services”). The Services must comply with Directive (EU) 2019/882 (the “European Accessibility Act”), which aims to ensure equal access to digital products and services throughout the EU.

This accessibility statement also applies to the monthio.com website (hereinafter “the Website”), which must also comply with the aforementioned directive.

At Monthio, we are committed to ensuring that our service is accessible to all users, regardless of disabilities, limitations, technology, or special needs. We believe that everyone should be able to access and use our services. While there are still gaps in the accessibility of our services, we are continuously working to improve the accessibility of our products and services. 

Website compliance status 

The Website is designed to comply with the Web Content Accessibility Guidelines (WCAG) 2.2 Levels A and AA.

The Website is fully compliant, including:

  • Support for screen readers and assistive technologies;
  • Semantic HTML5 structures;
  • WCAG-compliant CSS styles for color contrast, focus indicators, and visual clarity;
  • Compatibility across modern browsers and devices;

Services compliance status

We are actively working to improve the accessibility of the Services. At present, the Services are partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 Levels A and AA. This means that while some accessibility requirements are met, there are still challenges we are working to resolve.

Our internationally used, consumer-facing product, Income Verification, has been updated to fully meet WCAG 2.2 Levels A and AA criteria. This includes features such as, but not limited to:
  • Optimized keyboard navigation and focus handling;
  • WCAG-compliant CSS styles for high-contrast colors, focus indicators, and visual clarity;
  • Robust error messages and suggestions, that guide users to correct input mistakes;
  • React components built with accessibility in mind, including ARIA roles, labels, and state handling;
  • Compatibility with screen readers and other assistive technologies.
Other product offers are under active development and being aligned with the same accessibility standards. See Non-Accessible Content for more details.

Ongoing improvements

To strengthen accessibility across the Services, we have initiated a comprehensive accessibility program, which includes:
  • New accessible design system and component library
    Developed based on react-aria, with built-in accessibility features and WCAG-compliant CSS. It will be deployed in a prioritized sequence to ensure consistent accessibility and compliance.
  • Accessibility by design
    New features moving forward will be designed and developed with accessibility as a top priority from the very beginning.
  • Employee training
    Increasing awareness and competencies in accessibility and inclusive design across teams.
Interim Measures
While the new design system is being developed and implemented, we continue to monitor and improve accessibility within the Services. Critical accessibility issues are addressed immediately wherever possible within the current technical framework and infrastructure.

Feedback

We welcome feedback on accessibility in the Services or the Website. Your feedback helps us improve the experience for all users.

Email: info@monthio.com‍

Non-Accessible Content

As part of our ongoing assessments, we have identified areas where accessibility can be improved. These challenges may affect users who rely on assistive technologies or alternative methods of interacting with digital content. We are aware of and tracking the following current accessibility gaps, aligned with specific WCAG 2.2 Success Criteria:

2.1.1 Keyboard, 2.1.2 No Keyboard Trap
Almost all, but not yet all, functionalities are keyboard accessible. We also have a few instances of keyboard traps, which we are in the process of fixing.

2.4.5 Multiple Ways
Not all content on the Service is accessible through more than one method. We are exploring how we can technically provide users with multiple ways to find and access the content.

3.3.3 Error Suggestion
We are adding clear error suggestions in the messaging to help users resolve the problem.

3.3.2 Labels or Instructions
A few form elements lack proper labels and instructions.