Designing for everyone: accessibility improvements in airline ticketing
How a travel-tech team rebuilt its booking flow for accessibility, phase by phase, and how the team changed along the way.
Front-end developer at Rabobank
I write about the seam between design and front-end: accessibility, design systems and the habits that keep interfaces right.
I’m a front-end developer at Rabobank in the Netherlands. I spend my days where design decisions turn into code, which is where most interface mistakes are made, and I champion accessibility across my department. This site is where I think in public: what works at that seam, what doesn’t, and what I would tell a team starting tomorrow.
01
Accessibility is not a final audit, it is where every component starts. I champion it across my department, and I write about making it a habit a whole team keeps, not the heroic effort of one specialist.
On the blog: “Designing for everyone: accessibility improvements in airline ticketing”
02
Interfaces drift when nobody looks after the system. I write about tokens, components and the agreements that keep a design file and a codebase saying the same thing.
On the blog: “Islands architecture in Next.js”
03
Speed is a feature people feel before they see it. I write about raising it in design and code review, while it is still cheap to fix, instead of optimising in a panic afterwards.
On the blog: “Advanced front-end performance tips”
04
Design intent should survive the handoff. Most of my work happens in that gap, and most of what I write comes from it: the mistakes that are cheapest to catch before a line of code exists.
On the blog: “Cognitive load and UI design”
Blog
Essays on accessibility, design systems and working between design and front-end. Practical, opinionated and drawn from real projects, with a new one roughly once a month.
How a travel-tech team rebuilt its booking flow for accessibility, phase by phase, and how the team changed along the way.
How Hick’s Law, Fitts’s Law and the serial position effect can guide smarter interface decisions.
Serve static content fast, hydrate only the interactive parts, and let teams share one product.
Techniques beyond the basics that make speed feel like a design feature, not just a metric.