Reference

Design system

Every ratio was computed with tools/a11y/contrast.py against all three grounds. This page is noindex: it documents the template for whoever builds with it.

Never performed is blue, not red

The catalogue's whole argument is that a small number of pieces travel and most do not, and that this is the shape of the field rather than a verdict. So the second state token is a cool blue marking the pieces that were played again, and an unperformed work simply takes the muted text colour. There is no red on this page, because there is nothing on it that is a failure. The count is a number first, the state is a word second, and colour is third.

The markup asserts less than the page

Three works have never been performed. They are on the page, with the reason, because a catalogue that hides its failures is not a catalogue — but they are not emitted as MusicComposition, because publishing a piece as a structured work with no performance behind it asserts a public existence it does not yet have. Day 113 made the same call about sold-out shows and day 114 about departed members: the page is for humans and the markup is for machines, and they are allowed to say different true things.

Person, not MusicGroup

Days 113 and 114 were both MusicGroup, which is right for a performing act and wrong for somebody whose output is scores other people play. This is a Person with an Occupation and a workExample list — the seventh schema shape in seven days, each chosen from what the page is.

No photographs

A score is not a photograph and a stock picture of a piano would be decoration on a page whose entire argument is specificity. The composer is also fictional, which rules out a portrait for the reason day 110 gave.

Type

Tokens

The border token clears 3:1 against all three grounds, which is what WCAG 1.4.11 asks of a non-text boundary. It is never used for text.