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.
A Svelte 5 changelog overview covering snippets, bug fixes, and migration guidance. Live coding of runes-based dynamic filtering plus exploration of effect, onMount, and reactivity features.
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.
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.
The video explains skip links, which are used to improve web navigation efficiency. Skip links allow users to jump directly to the main content or other key sections of a webpage when using a keyboard or screen reader.
This is a short introduction of the talk2svelte library which provides voice recognition and voice synthesis for Svelte, thanks to the Web Speech API.
It allows to interact with a Svelte site by voice, like navigating or clicking on elements.
Inlang: a solution for internationalization in SvelteKit projects. The SDK and its tools simplify setup, language negotiation, and content management. This approach automates i18n processes, offering a user-friendly experience for developers and translators.
0:00 Introduction
0:20 Changelog - SvelteKit 1.22.6
1:59 Community Showcase - sveltekit-search-params by Paolo Ricciuti
22:32 Q&A - How to create accessible form error summaries
00:00 Introduction
00:30 Announcements - Svelte Summit
01:10 Runes Primer
13:17 Runes FAQ
19:20 Rune helpers and stores with Hunter
26:26 Runify demo and fine-grained reactivity with Paolo
35:00 The library maintainer’s perspective with Hunter
45:08 Poll: the kinds of applications we make
53:25 Paul proposes Runes be a compiler-based toolchain separated from Svelte, similar to RxJS
1:01:11 Everyone’s impressions of Runes
1:02:48 Tantei-Kun likes the $props Rune
1:07:32 Poll: everyone’s impression of Runes so far