Digital Barriers Make Visitors of Dutch Websites Stumble

Visitors to Dutch websites regularly run into digital barriers, according to research published by Eindhoven University of Technology (TU/e) under the title "Digital barriers make visitors of Dutch websites stumble."

The finding matters for anyone who designs or procures web interfaces in the Netherlands. A barrier, in this context, is any element of a page that prevents a user from completing a task: a form label a screen reader cannot associate with its input, a color contrast ratio that falls below perceivable thresholds, a keyboard trap inside a modal dialog, or a navigation structure that assumes a mouse pointer the visitor does not use.

The framing of the study is notable. It does not describe accessibility as a niche concern of a small disabled user group. It describes stumbling — an experience that can affect any visitor, at any time, on any device. A user filling in a form on a phone in bright sunlight faces essentially the same low-contrast text as a user with low vision. A user with a temporary wrist injury who cannot operate a mouse faces the same focus-order and keyboard-navigation failures as a full-time screen reader user.

This framing aligns with how international standards treat the problem. The Web Content Accessibility Guidelines (WCAG), currently at version 2.2, define success criteria across four principles — content must be perceivable, operable, understandable, and robust. Version 2.2, published as a W3C Recommendation in October 2023, added criteria such as 2.4.11 Focus Not Obscured and 2.5.7 Dragging Movements, both of which address exactly the kind of interaction failures that make visitors stumble: interfaces where the focused control disappears behind a sticky header, or where a task can only be completed with a drag gesture and offers no single-pointer alternative.

For Dutch organizations, the legal context is concrete. The European Accessibility Act took effect on 28 June 2025, obliging providers of consumer-facing digital services — e-commerce, banking, transport, e-books — to meet accessibility requirements. Public-sector bodies in the EU have been held to the equivalent obligations of EN 301 549, which incorporates WCAG, since 2018 through the Web Accessibility Directive. Research documenting that Dutch sites still place barriers in visitors' paths suggests a gap between the legal baseline and the interfaces actually shipped.

The design implications are practical rather than aspirational. Fixing barriers usually means applying well-documented patterns: programmatically associated labels and error messages, focus indicators that remain visible, dialogs that trap and release focus correctly, text alternatives that convey function rather than file name, and layouts that reflow at 320 CSS pixels without loss of content. None of these techniques are novel. All of them are testable, either with automated tools that catch a fraction of failures or with the manual assistive-technology testing that catches the rest.

The measurable outcome of removing such barriers is straightforward: more visitors complete the task they came for. Forms get abandoned less. Support contacts drop. Checkout conversion rises. Accessibility work tends to pay for itself precisely because the barriers it removes are ones that slow down or block real interactions for the entire audience, not a hypothetical edge case.

The TU/e publication contributes Dutch evidence to a pattern already visible across Europe: despite mature standards, a clear legal mandate, and decades of documented technique, websites continue to ship with preventable obstacles. As enforcement of the European Accessibility Act begins and awareness grows, the question for Dutch teams shifts from whether to remove these barriers to how quickly they can audit, fix, and verify the interfaces their visitors depend on every day.