ContactPortaal
Accessibility statement

Accessible to everyone

ContactPortaal is designed to be usable by people with a wide range of abilities and meets WCAG 2.2 level AA. We test the interface continuously and improve where needed.

Our commitment

We follow EU Directive 2016/2102 on the accessibility of public-sector websites and mobile applications, plus the Dutch implementation (Tijdelijk besluit digitale toegankelijkheid overheid). For private customers we apply the same standard.

Standards we follow

  • WCAG 2.2 level AA, across desktop, tablet and mobile.
  • EN 301 549 v3.2.1, the European standard for digital accessibility.
  • Valid HTML5 with proper semantic elements (landmarks, headings, lists, form fields).
  • WAI-ARIA where it adds value, with a preference for native HTML elements that achieve the same outcome.

What that means in practice

  • Full keyboard operation

    Every function is reachable without a mouse. Focus indicators are always visible; tab order follows the visual logic.

  • Contrast and colour use

    Body text contrasts at least 4.5:1 against the background (AA), headings and larger text at least 3:1. Colour is never the only way information is conveyed.

  • Screen readers

    Tested with NVDA, VoiceOver and TalkBack on the main flows. Icons have alt text, controls have linked labels, and dynamic updates are announced via aria-live.

  • Motion

    Animations are subtle and respect prefers-reduced-motion. There are no flashing or auto-playing elements.

  • Language

    The interface is available in Dutch and English. The html lang attribute is set correctly per page so screen readers use the right pronunciation.

  • Forms

    Every input has a label, errors are signalled both textually and visually, and autocomplete hints are set where they help.

Known limitations

We're open about what can still improve. Areas we're actively working on:

  • The ArcGIS map component offers a table alternative for users who can't use the map, but the map itself isn't yet fully keyboard-operable for every interaction.
  • The rich-text editor in newsletters uses third-party widgets with limited screen-reader support. A markdown editor alternative is planned.
  • Some overview tables use virtualised scrolling at large data sizes, which limits how the total length is announced to screen readers.
Report an issue

If you encounter an accessibility issue, please let us know at toegankelijkheid@contactportaal.nl.

We respond within five business days and keep you informed of the resolution.

Last updated: May 2026.

Ready to take a look?

Book a 30-minute demo, we'll walk through your own scenario, not a generic tour.

Book a demoGet in touch