Accessibility statement
WebOké wants everyone; including visitors with a visual or motor impairment; to be able to use the website and client portal fully. We continuously work on accessibility following the WCAG 2.1 AA guidelines.
The standard we follow
We follow the European accessibility standard EN 301 549, based on the WCAG guidelines (level AA). This aligns with the European Accessibility Act, which applies to webshops and online services since June 2025.
To the best of our knowledge the website and client portal comply with this standard. Accessibility is part of our development process: every new feature is built with keyboard operation, screen reader support and sufficient contrast.
What we do
- All buttons and links can be operated with the keyboard (Tab, Enter and space), including the dialogs and selection actions in the portal.
- Forms have labels, decorative icons are hidden from screen readers and status messages are announced.
- Text and controls have sufficient colour contrast, in both the light and dark theme.
- Form errors are textual, linked to the field and readable by screen readers.
- The site is available in Dutch and English; the language choice applies to all pages and messages.
- Pages have a logical heading structure, recognisable landmarks and a "skip to main content" link.
- We use no flashing or auto-playing content; animations are subtle and never required to understand the site.
Frequently asked questions about accessibility
Can I use WebOké with a screen reader?
Yes. The website and client portal are fully usable with screen readers such as NVDA, JAWS and VoiceOver: forms have labels, status messages are announced and decorative elements are skipped.
Can I operate everything with just the keyboard?
Yes. All features, from ordering to DNS management in the client portal, can be operated with Tab, Enter and space, with a visible focus indicator.
What if something turns out not to be accessible after all?
Report it via a support ticket or email. Accessibility reports are handled with priority and fixed structurally.
Running into something?
If you find a page or feature that is not properly accessible, please let us know and we will fix it. Report it via a support ticket
This statement was last updated on 15 August 2026.
