In this interactive session we will:

• Go through requirements we had for Breadcrumbs in our web apps at Ahold Delhaize.
• Build a generic breadcrumbs component in the layout.tsx mechanism of Next.js so they are automatically added to all your pages.
• Decide what to put in server components, what to put in client components and demonstrate the problems you get when making wrong choices.
• Build a mechanism that lets a page override the generic breadcrumbs.
• Test your knowledge on React during the session with mentimeter questions.

Learn how we took our server-driven UI platform to the next level by utilizing cutting-edge developments in the React and React Native ecosystem.

The JavaScript ecosystem is longing for a standardized tooling. No more plumbing work, no more choice fatigue and no more analysis paralysis. But how would such a tool look like? Together, we have a look at the newly released Vite+ Alpha and see if the new open source CLI can hold up to its promises, covering developer's tooling needs and let them focus on shipping, especially in an agentic age.

Modern JavaScript applications often pass automated accessibility checks with flying colors. Tools like Lighthouse, Axe, and CI pipelines give us green reports, and we feel confident shipping.

But what happens when real users interact with the application?
In this talk, we’ll explore why automated accessibility testing only catches a fraction of real issues. Through a live demo of a seemingly “accessible” JavaScript form (we will see on the Lighthouse and Axe DevTool no accessibility issues), we’ll uncover hidden problems that automated tools completely miss, such as broken keyboard navigation, silent dynamic UI updates, and modal dialogs that behave correctly visually but fail real users.

You’ll learn why accessibility is not just about passing automated checks, but about understanding how people actually interact with your JavaScript applications.

This session will include a live demo, practical examples, and concrete takeaways developers can apply immediately.

Cognitive stress has always been a challenge when dealing with new languages, features and APIs. Oftentimes, we find ourselves experimenting with new features, rather than only reading their documentation. Either with a debugger, a REPL environment, or a thousand console.logs, we explore what these tools do. But what if there was something that will further cut the time between writing code and seeing the result? JS Eval is a tool that achieves exactly this by displaying the evaluation results of your program directly where they come from. Join me as we dive into its plethora of features and how they can help you understand the new tools you encounter!