Statement

Accessibility

This site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, for everyone who wants to hear the music or read the story.

What the site does

  • Every page works with a keyboard, with a visible focus ring and a “Skip to content” link first.
  • All content is in the page itself: it reads the same with JavaScript turned off, and the menu works without it.
  • The site is dark by default. A “Light mode” button in the footer switches every page to a light theme and remembers the choice; without JavaScript the site stays dark. Text and controls meet the AA contrast ratios in both the dark and light themes, on every page’s own colors.
  • Pages reflow to 320 CSS pixels wide without scrolling sideways, and text can be enlarged to 200%.
  • Motion is gentle and follows your device: it stops when your device’s settings ask for reduced motion, with or without JavaScript. Nothing flashes.
  • Images have text alternatives; decorative ones are hidden from screen readers. Wherever a color marks one of the three projects, it comes with a shape (circle, square or diamond) and the project’s name.
  • Forms have visible labels, say which fields are required in words, keep what you typed when something needs fixing, and list the problems at the top.
  • Nothing on this site plays sound on its own.

Known gaps

  • Videos are links to YouTube. Their captions have not all been checked by a person yet.
  • The Luxury Liners’ 2001–2004 journal is linked as archived pages on the Wayback Machine, which this site doesn’t control, until it is restored here as text.
  • Some archived press quotes come from reprints; their original articles may not be accessible.

How it is tested

Each build is checked with automated tests (axe-core, WCAG 2.2 AA rules) in dark and light themes at phone and desktop widths, for sideways scrolling at 320 pixels on every page, and with JavaScript off. Keyboard use is checked by hand. Screen-reader checks by hand (NVDA with Firefox, VoiceOver with Safari on a Mac and VoiceOver on an iPhone) have not been done yet; when they are, the date and the tools used will be listed here.

Report a problem

If something on the site doesn’t work for you, please report it through the contact form (topic “Accessibility problem”), saying which page and what happened, and it will be fixed as soon as possible.

Last reviewed .