Progressive enhancement in Svelte - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is progressive enhancement in web development?

Progressive enhancement means building a basic, working website first, then adding extra features that improve the experience for browsers or devices that support them.

intermediate

How does Svelte support progressive enhancement?

Svelte compiles components to simple JavaScript that runs in the browser, allowing the page to work without JavaScript first, then enhancing with interactivity when JS loads.

beginner

Why is progressive enhancement important for accessibility?

It ensures all users, including those with older browsers or assistive technologies, can access the core content and functionality without barriers.

beginner

In Svelte, what is a simple way to add progressive enhancement to a button?

Start with a normal HTML button that works without JS, then add Svelte event handlers to enhance it with extra behavior when JS is available.

intermediate

What is the difference between progressive enhancement and graceful degradation?

Progressive enhancement builds from a simple base up, adding features for better browsers. Graceful degradation starts with a complex site and tries to keep it usable on older browsers.

What is the first step in progressive enhancement?

A Ignore older browsers

B Build a basic, functional website

C Use only JavaScript for all features

D Add complex animations

Progressive enhancement starts by building a simple, working site that everyone can use.

How does Svelte help with progressive enhancement?

A By compiling components to efficient JavaScript that enhances basic HTML

B By requiring heavy JavaScript frameworks

C By disabling HTML fallback

D By only supporting modern browsers

Svelte compiles to simple JS that enhances the basic HTML, supporting progressive enhancement.

Which is NOT a benefit of progressive enhancement?

A Better accessibility

B Works on all browsers

C Requires users to have JavaScript enabled

D Improves user experience gradually

Progressive enhancement does NOT require JavaScript; it works without it first.

What should you do to enhance a button in Svelte progressively?

A Use a plain HTML button first, then add Svelte event handlers

B Use only JavaScript to create the button

C Hide the button if JavaScript is disabled

D Use inline styles only

Start with a normal button, then add interactivity with Svelte handlers.

What is the main difference between progressive enhancement and graceful degradation?

A Progressive enhancement requires no JavaScript

B They are the same

C Graceful degradation ignores older browsers

D Progressive enhancement builds up from simple; graceful degradation starts complex and simplifies

Progressive enhancement builds from simple to complex; graceful degradation starts complex and tries to keep it usable.

Explain how you would apply progressive enhancement in a Svelte app for a form component.

Think about how the form works with and without JavaScript.

Describe why progressive enhancement improves accessibility and user experience.

Consider users with different devices and abilities.

Practice

1. What is the main goal of progressive enhancement in Svelte applications?

easy

A. To load all data at once for faster performance

B. To use only JavaScript for all app functionality

C. To avoid using semantic HTML elements

D. To make sure the app works with basic features before adding advanced ones

Solution

1. Step 1: Understand the concept of progressive enhancement

   Progressive enhancement means starting with a simple, working version of the app that everyone can use.

2. Step 2: Identify the goal in Svelte apps

   In Svelte, this means building basic content first, then adding interactive features on top.

3. Final Answer:

   To make sure the app works with basic features before adding advanced ones -> Option D

4. Quick Check:

   Progressive enhancement = basic first, then advanced [OK]

Hint: Think: start simple, then add features [OK]

Common Mistakes:

• Assuming JavaScript must be used for everything
• Ignoring basic content for advanced features
• Skipping semantic HTML importance

2. Which of the following is the correct way to provide fallback content for users without JavaScript in a Svelte app?

easy

A. Enable JavaScript to see this app.

B.

C. No JS support

D. Enable JS

Solution

1. Step 1: Identify the HTML element for no-JavaScript fallback

   The tag is designed to show content only when JavaScript is disabled.

2. Step 2: Check the options for correct usage

   Enable JavaScript to see this app.

   uses correctly with fallback text. Others misuse tags or won't show fallback properly.

3. Final Answer:

   <noscript><p>Enable JavaScript to see this app.</p></noscript> -> Option A

4. Quick Check:

   Fallback for no JS = <noscript> [OK]

Hint: Use <noscript> for no-JS fallback content [OK]

Common Mistakes:

• Using <script> to detect JS absence
• Hiding fallback with CSS only
• Using <template> which doesn't render

3. Given this Svelte snippet for progressive enhancement:

<button aria-label="Toggle menu" on:click={toggleMenu}>Menu</button>
<nav class:open={menuOpen}>...</nav>

What happens if JavaScript is disabled in the browser?

medium

A. The menu is always visible because class binding works without JS

B. The button does nothing and the menu stays hidden

C. The button triggers toggleMenu even without JS

D. The menu is removed from the DOM

Solution

1. Step 1: Understand Svelte event handling and class binding

   The on:click event and class:open binding require JavaScript to work.

2. Step 2: Consider no JavaScript scenario

   Without JS, the button click does nothing and the class:open is not applied, so the menu stays hidden if initially hidden.

3. Final Answer:

   The button does nothing and the menu stays hidden -> Option B

4. Quick Check:

   JS off means no event or class binding [OK]

Hint: JS needed for event and class bindings [OK]

Common Mistakes:

• Thinking class binding works without JS
• Assuming button triggers function without JS
• Believing menu auto-shows without JS

4. You wrote this Svelte code for progressive enhancement:

<button on:click={toggle} aria-expanded={expanded}>Toggle</button>
<div hidden={!expanded}>Content</div>

But the content never shows when clicking the button. What is the likely problem?

medium

A. The hidden attribute does not toggle correctly with boolean binding

B. The aria-expanded attribute must be a string, not boolean

C. The toggle function is missing or not updating expanded

D. The on:click event is not supported in Svelte

Solution

1. Step 1: Check event and state connection

   The button's on:click calls toggle, which should update expanded state.

2. Step 2: Identify missing or broken toggle function

   If toggle is missing or doesn't update expanded, the hidden attribute never changes, so content stays hidden.

3. Final Answer:

   The toggle function is missing or not updating expanded -> Option C

4. Quick Check:

   Missing toggle function = no state change [OK]

Hint: Ensure toggle updates state variable [OK]

Common Mistakes:

• Thinking hidden attribute toggles automatically
• Confusing aria-expanded type requirements
• Believing on:click is unsupported in Svelte

5. You want to build a Svelte app that shows a list of items with a button to filter them. For progressive enhancement, which approach is best?

hard

A. Render the full list in HTML first, then use Svelte to filter items interactively

B. Render an empty list and fetch items only after JavaScript loads

C. Hide the list and show it only after the filter button is clicked

D. Use only JavaScript to create and display the list dynamically

Solution

1. Step 1: Understand progressive enhancement for lists

   Start with a fully rendered list in HTML so users without JS see all items.

2. Step 2: Add interactive filtering with Svelte

   Use Svelte to add filtering on top, enhancing the experience for JS users.

3. Final Answer:

   Render the full list in HTML first, then use Svelte to filter items interactively -> Option A

4. Quick Check:

   Basic content first, then interactive features [OK]

Hint: Show full content first, then add JS filters [OK]

Common Mistakes:

• Loading list only after JS runs
• Hiding content initially
• Relying solely on JS for content display