Spark & Anvil Privacy

Real cases

Two of the ideas you practise, meeting in one real situation. Choose, see what actually happens, then reflect.

A case · you decide

Name It and Quiet It read the header

Name It & Quiet It — a 16-year-old fixing the school app's header in a coding club

The idea in play: every control needs an accessible name, and pure decoration needs an empty alt so it is skipped.

The header has a magnifying-glass search button with no text, and a decorative swirl image. A screen reader reads it as "magnifying glass tilted left, button, image, swirl-final-v2.png."

Name It: an icon-only button needs a name the screen reader can say aloud.

Quiet It: a decoration that carries no information gets alt="" so the reader skips it.

What should Aiden change?

Audit a screen →

A case · you decide

Contrast It and Structure It fix the article page

Contrast It & Structure It — a 17-year-old auditing a news page for a class project

The idea in play: body text needs 4.5:1 contrast, and headings must not skip levels.

The page uses light grey #999 text on white, and its headings go from h1 straight to h3 because the designer liked the h3 size.

Contrast It: #999 on white is about 2.8:1. Normal-size text needs at least 4.5:1.

Structure It: screen-reader users jump between headings, so the level after h1 should be h2. Size is a style choice, not a level.

What is the right fix?

Audit a screen →