accessibility

  1. The interface does not end at the board

    Physical-key feedback, host sleep, and an iOS zoom gesture expose three boundaries the game still needs to design around.

  2. Let the game explain itself

    Game-log chips gain explanation-on-demand tooltips, while the recording script learns to demonstrate the game it claims to show.

  3. The narrow screen gets to decide

    Foundation tokens make a mobile-first redesign tractable, then a second design review turns layout stability and colour contrast into regression tests.

  4. The week the game started watching itself

    A three-PR refactor trio makes the word-submission pipeline immutable and side-effect-free, then the newly-launched game gets its first stats page, a same-week AI tuning pass informed by it, docs finally caught up to the Postgres stack, and a WCAG 2.2 audit closes the week.

  5. The screen that would not respond

    A WCAG reflow fix that became a permanent layout rule, assisted mode deleted nine days after it shipped, and an end-game screen that froze the browser until profiling found why.

  6. The first pull requests

    Two days of committing straight to main end in one day: a CI workflow, a licensing swap, a WCAG audit, and the design question the game keeps coming back to.