Svelte has been described as an “accessibility-first-framework”, yet its compiler warnings cover only a fragment of the issues at hand. In this talk, I’d like to explore how accessible Svelte really is and more importantly, have a look at what you can do to bridge the gap. Ideas include checking both automatically and manually for issues the compiler might overlook, like color contrast, keyboard accessibility and semantics.
A weekly Svelte update from February 2024 covering changelog highlights, community showcase featuring Paraglide JS for internationalization, and discussions about Svelte 5 progress.
Changelog and Q&A with Rich Harris. The episode covers various updates and improvements in Svelte, including support for TypeScript type assertions, fixes for scoping classes, optimizations in the compiler, and enhancements in SSR (Server-Side Rendering) and CSS pruning.
Svelte includes built-in animations that makes it easy to slide, scale, and fly elements in and out of the DOM. However, you need to be careful to not trigger motion sickness in your users. I will go over which Svelte transitions could cause accessibility issues and how to respect user motion preferences when using them.
The front end development landscape has been transformed since we started building Svelte and Sapper. What would a reimagined, truly modern workflow look like?
Domenik Reitzner had a dialog with his brave audience about the dialog element and how to integrate it with Svelte. He showed us the benefits of using the platform and what a11y(accessibility) benefits come out of the box, by using this HTML element.
Some new routing changes have made its way to SvelteKit. Controversial? A bit. We sit down with Rich Harris to talk about the why and the how of it all.