Accessible for everyone

We believe everyone deserves access to events. That's why WCAG AA accessibility is not an afterthought but a core value of MijnEvent.

Standards

What we do

Every screen, every button and every form meets the WCAG 2.1 AA guidelines.

Keyboard navigation

The entire checkout process is operable with just a keyboard. Logical tab order, visible focus indicators and skip links on every page.

Color contrast

All text meets a minimum 4.5:1 contrast ratio. UI elements and focus indicators meet at least 3:1. Tested with multiple tools.

Screen reader support

Semantic HTML, ARIA labels, live regions for error messages and status updates. Tested with NVDA, VoiceOver and JAWS.

Form labels

Every input field has a visible label, descriptive error messages and hint text. Never just a placeholder as a label.

Touch targets

All clickable elements are at least 44x44 pixels. Extra large in the check-in app for field use.

Error handling

Errors appear inline next to the field with clear explanations. Focus automatically moves to the first error field on submission.

Comparison

MijnEvent vs. the rest

Criterion MijnEvent Average platform
WCAG AA compliant
Keyboard navigation Partial
Screen reader tested
Visible focus indicators
Form labels Partial
Contrast ratio 4.5:1 Partial
Skip links
ARIA live regions
"Accessibility is not a feature you can toggle on or off. It's a right."

— The MijnEvent team

Our checklist

Our WCAG AA checklist

  • Semantic HTML structure (h1-h6)
  • Alt text on all images
  • Visible focus ring on interactive elements
  • Logical tab order without tabindex > 0
  • Labels linked to every form field
  • Error messages at the field, not just at the top
  • role="alert" on dynamic error messages
  • aria-live="polite" on status updates
  • Buttons for actions, links for navigation
  • Skip link to main content
  • Minimum 44x44px touch targets
  • Focus trap in modals and dialogs
Formal statement

Our accessibility statement

This page shows how we put accessibility into practice. If you want to read the formal, legal statement — covering the WCAG 2.1 AA standard we apply, our compliance status, known limitations and how to file a complaint — see our full accessibility statement.

Read the accessibility statement