Recess turns the WordPress idea your AI made into a clickable page with a clean live link, without making people choose a permanent website first.

What should an AI assistant return after using Recess?

Return the clean shareUrl first as Yard published: {shareUrl}, then a short note about what opened, what changed, validation state, and where the portable recipe lives.

Is Recess the final website?

No. A Recess link is for showing, testing, teaching, pitching, and tinkering; export the saved copy when the idea needs a permanent website.

What are Playset, Yard, Pass, Field Trip, and Blueprint?

A Playset is the reusable source recipe, a Yard is the playable WordPress surface people can open, a Pass is the clean live URL, a Field Trip is a guided flow inside a Yard, and a Blueprint is the portable recipe.

Accessibility

The link should open for more people.

Recess should feel quick, clear, keyboard-friendly, and readable without making people squint at tiny mystery confetti. The fun only counts when more people can actually use the page.

Open audit file Read status

WordPress idea in Clickable page out Clean live link Not the final website

Static audit passed

13 public HTML routes checked across 28 static checks with 0 static accessibility violations.

Contrast audit passed

74 tracked color pairs checked with 0 contrast violations.

Audit file

Open the accessibility audit file for the current audit summary.

Contrast receipts

Tracked text pairs are checked at 4.5:1 or better, and UI/focus pairs at 3:1 or better. Lowest tracked text ratio: 4.78:1. Tightest tracked UI ratio: 3.41:1.

Keyboard path

Public pages include a skip link to main content, visible focus states, named navigation, one main landmark, one H1, sensible heading order, labeled controls, named copy buttons, valid in-page links, and no positive tabindex shortcuts. No secret handshake required.

Motion manners

Animation hooks include reduced-motion handling so polish can calm down when the visitor asks for calmer pages. A live page can have sparkle without making the page spin.

Known gap

This is a static audit and contrast check, not a formal WCAG certification or VPAT. Screen reader, zoom, keyboard, and browser visual QA still need a human-assisted pass in an environment where Chromium can launch.

Current verification command

npm run audit:marketing-accessibility

Browser verification note

Local browser-backed tests are currently blocked in this sandbox by a Chromium launch error. They should be rerun on a machine or CI runner that can launch Playwright before treating visual accessibility as fully verified.