Accessibility statement
Dayporto aims to be usable by everyone: in the office, in the van and in the customer portal, with mouse, keyboard, touch or screen reader. This statement describes honestly where we stand.
WCAG 2.2 AA
Status
Dayporto is designed and built to the Web Content Accessibility Guidelines (WCAG) 2.2 level AA, the standard referenced by EN 301 549 and European accessibility legislation. The status is based on self-assessment with automated and manual checks; an independent WCAG-EM evaluation has not yet been carried out.
How we test
- Automated checks with axe-core (WCAG 2.2 AA rules) on the public site, the office app, the technician app and the customer portal — part of the test suite, so on every release.
- Lighthouse in the CI pipeline blocks a release when the accessibility score drops below 90.
- Contrast of every brand colour computed with WCAG 2.x and APCA (see table); the values below come live from the design tokens.
- Manual checks of keyboard operation, focus order, heading structure and screen-reader labels on the core screens.
What we built in
- Skip link to the main content, landmarks (banner, navigation, main, footer) and one h1 per page.
- All form fields with associated labels; error messages linked to the field (aria-invalid, aria-describedby).
- Icons without text have an accessible name; decorative icons are hidden from screen readers.
- Click targets of at least 24×24 pixels (WCAG 2.2, 2.5.8) and visible focus.
- Respect for reduced motion (prefers-reduced-motion) and a dark mode.
- Four languages (Dutch, English, German, French) with the correct language tag per page.
- Text stays readable at 200 % zoom and on phone width without horizontal scrolling.
Contrast measurement of the brand palette
WCAG 2.x requires 4.5:1 for normal text and 3:1 for large text and controls. APCA is the candidate method for WCAG 3 (not yet a standard); guide values: Lc 75 for body text, 60 for larger text, 45 for large bold headings. We report both and require WCAG 2.2 AA.
| Text on background | WCAG ratio | AA | APCA Lc |
|---|---|---|---|
| #0A2239 / #ffffff | 16,14:1 | yes | 103 |
| #102A43 / #ffffff | 14,64:1 | yes | 101 |
| #374151 / #ffffff | 10,31:1 | yes | 94 |
| #69707d / #ffffff | 4,98:1 | yes | 74 |
| #69707d / #F3F5F7 | 4,56:1 | yes | 68 |
| #C4390B / #ffffff | 5,33:1 | yes | 75 |
| #0D6B51 / #E4F9F2 | 5,91:1 | yes | 75 |
| #0A2239 / #FF5A1F | 5,18:1 | yes | 44 |
| #0A2239 / #FF7A45 | 6,24:1 | yes | 51 |
| #ffffff / #0A2239 | 16,14:1 | yes | 106 |
| #475569 / #F3F5F7 | 6,93:1 | yes | 80 |
Known limitations
- Brand colours an organisation sets itself (logo, primary colour) may yield lower contrast outside our control; text colours are darkened automatically to 4.5:1, background colours are not.
- Generated PDF documents (quotes, invoices, payslips, drawings) are not yet tagged for screen readers (PDF/UA).
- The drawing module (floor plans) is mouse/touch oriented; drawing with the keyboard alone is limited. All information in a drawing is also available as a list and PDF.
- Maps (planning, routes) have a textual list view as alternative, but the map itself is not fully keyboard operable.
Report a problem
Run into something? Email us — we respond within five working days and include it in the next release. Mention the page and, if possible, your assistive technology.
This statement was drawn up on 20-09-2026 and is re-checked with every release.