{"id":13917,"date":"2025-05-23T13:16:14","date_gmt":"2025-05-23T13:16:14","guid":{"rendered":"https:\/\/www.anamata.nl\/?p=13917"},"modified":"2025-05-27T06:50:28","modified_gmt":"2025-05-27T06:50:28","slug":"accessibility-is-no-longer-optional","status":"publish","type":"post","link":"https:\/\/www.anamata.eu\/nl\/13917\/","title":{"rendered":"Accessibility is no longer optional"},"content":{"rendered":"
<\/div>
\n
\n

How WCAG 2025 impacts your Mendix app<\/h4><\/div><\/div><\/div>\n<\/div><\/div>\n\n\n\n
<\/div><\/div>\n<\/div><\/div><\/div>\n\n\n\n
Intro<\/strong><\/h5><\/div><\/div>

Imagine this: you\u2019ve built a beautiful Mendix app. Super fast, sleek design, everything works… but then the truth comes out. Not everyone can use it. Oops!

Starting in 2025, the new WCAG 2.2 guidelines and the European Accessibility Act (EAA) will come into effect. So what does that mean for your Mendix apps? And what does it mean for you as a Mendix developer? More importantly, how do you make sure your app is not just compliant, but truly accessible to everyone?

At Anamata, we believe in Quality from the Heart. Accessibility is a core part of that. You can see this reflected in our QA scans, where we actively check whether applications meet the latest accessibility standards.<\/p><\/div><\/div>\n\n\n\n

<\/div><\/div><\/div>\n\n\n\n
What is WCAG and why is it important?<\/strong><\/strong><\/span><\/h5><\/div><\/div>

WCAG stands for Web Content Accessibility Guidelines, an international standard for digital accessibility. These guidelines ensure that websites, apps, and other digital products are usable by everyone, including people with visual, auditory, motor, or cognitive disabilities.
WCAG is based on four key principles:

Perceivable<\/strong>: information and components must be presented in ways users can perceive (like text alternatives for images).
Operable<\/strong>: users must be able to navigate and use the interface without barriers, even with just a keyboard or voice control.
Understandable<\/strong>: content and operation should be clear and easy to comprehend.
Robust<\/strong>: content should work reliably across various technologies, including screen readers.<\/p><\/div><\/div>\n\n\n\n

What\u2019s new in WCAG 2.2?<\/strong><\/strong><\/strong><\/h5><\/div><\/div>

The WCAG 2.2 guidelines introduce new success criteria on top of WCAG 2.1, with a focus on users with cognitive and motor impairments. Expect things like improved focus indicators, easier-to-use buttons, and clearer navigation.

And then there\u2019s the European Accessibility Act (EAA), legislation requiring digital products and services in the EU to be accessible. In short: if your app isn\u2019t accessible, you could face serious legal consequences. But honestly, why would you want to exclude a large portion of your potential users in the first place?
<\/p><\/div><\/div>\n\n\n\n

A learning moment from practice<\/strong><\/strong><\/h5><\/div><\/div>

When I first started as a Mendix developer, I\u2019ll admit: accessibility wasn\u2019t on my radar. I focused on speed, functionality, and design. For two years, I built applications without giving much thought to users with disabilities.

That all changed when I started a project in the public sector. Government institutions must comply with strict accessibility requirements, and suddenly I had to dive into WCAG, aria labels, and keyboard navigation. Thankfully, as a developer, you can learn fast, but I quickly realized it would have been far more efficient to build accessibility into my workflow from day one.

With WCAG 2.2, it\u2019s not just the public sector anymore. More and more industries will need to comply. Accessible development won\u2019t be the exception. It\u2019ll be the norm.
<\/p><\/div><\/div>\n\n\n\n

\n
<\/div>\n<\/div>\n\n\n\n
<\/i><\/span>
Government institutions must comply with strict accessibility requirements, and suddenly I had to dive into WCAG, aria labels, and keyboard navigation. Thankfully, as a developer, you can learn fast, but I quickly realized it would have been far more efficient to build accessibility into my workflow from day one<\/span><\/div><\/blockquote><\/div><\/div>\n\n\n\n
Why this matters for your business<\/strong><\/strong><\/strong><\/h5><\/div><\/div>

<\/p><\/div><\/div>\n\n\n\n