Appearance
Account, Access & Storefront
The screens a product needs before it needs a tenth dashboard.
These eighteen pages were not in the original specification. They were added after reading the market: every SaaS needs plans, invoices, sessions, API keys, members, roles and integrations exactly once, and hand-building them is a fortnight nobody budgets for. A tenth dashboard, by contrast, is a variation on nine you already have.
The catalogue
| Page | Path | What it is for |
|---|---|---|
| Get started | /account/get-started.html | Onboarding checklist, setup progress, usage at a glance |
| Public profile | /account/profile.html | Profile hero, stat strip, activity, teams, about |
| Plans | /account/plans.html | Four tiers, monthly/annual switch, full comparison table |
| Billing | /account/billing.html | Invoice history, payment methods, usage meters, billing address |
| Security | /account/security.html | Two-factor, active sessions, security log, workspace policy |
| API keys | /account/api-keys.html | Masked keys with reveal, copy, rotate and revoke; webhook secret |
| Members | /account/members.html | Team table, pending invitations, seat accounting |
| Roles | /account/roles.html | Permission matrix — five roles across eighteen capabilities |
| Integrations | /account/integrations.html | Connected and available apps, connect/disconnect state |
| Notifications | /account/notifications.html | Channel matrix, quiet hours, digest frequency |
| Appearance | /account/appearance.html | Personal navigation and regional preferences — distinct from the workspace-wide customizer |
| Activity | /account/activity.html | Cross-cutting account feed — sign-ins, billing, team, files; the security log is the security-relevant slice of the same trail |
| Shop home | /store/home.html | Search hero, brand tiles, offers, new arrivals |
| Search results | /store/catalog.html | Faceted filter rail, grid/list toggle, active-filter chips |
| Product page | /store/product.html | Gallery, buy box, variant picker, specification tabs, reviews |
| Wishlist | /store/wishlist.html | Saved items — the [data-av-favourite] heart every card already carries, remove-with-undo, quick-add straight into the basket |
| My orders | /store/orders.html | One card per order with the lines inside, .av-steps fulfilment status, buy-again straight into the basket |
| Receipt | /store/receipt.html | The .av-invoice component the admin's invoice page already ships, with a storefront breadcrumb and no B2B due date |
Every one is registered in PAGES in tests/lib/server.mjs, so all of them are held to the same gates as the rest of the demo: no console errors, one <h1>, no horizontal overflow at any width, no request leaving the origin, and a pixel diff in both colour modes.
The storefront is not a second design system
/store/* is customer-facing and is built from the same components as the admin — .av-card, .av-badge, .av-btn, .av-price, the same tokens, the same presets, the same dark mode.
That is a deliberate constraint, not a shortcut. A template that ships separate "admin" and "shop" stylesheets has two things to maintain, two things to re-theme, and two places for a preset to be half-applied. The only genuinely new pieces are the ones a storefront needs and an admin does not: .av-product-card, .av-facets, .av-buy and .av-qty.
Four decisions worth knowing
A masked secret is masked by swapping the text, never by CSS
-webkit-text-security, a blur filter, and a matching text colour all leave the real value selectable, read aloud, and on the clipboard of anyone who drags across the row. The field looks protected in a screenshot and is protected nowhere else.
[data-av-secret] writes a constant-length mask into the element until the reader asks for the value — which also keeps the mask from leaking the key's length. Revealing announces itself and reverts after twenty seconds. Copy works while the key is hidden, so nobody ever has to reveal one in order to use it.
Be precise about the claim. The value sits in the data-av-secret attribute, because a static demo has to get it from somewhere; what the module guarantees is that it is never in the page's rendered text, never selectable, and never in the accessibility tree until it is asked for. In a real application that attribute becomes a fetch made when the reveal button is pressed, and nothing else in the module changes.
html
<span class="av-secret" data-av-secret="av_live_9f2b7c41d8e63a05b71c">
<code class="av-secret__value" data-av-secret-value></code>
<input type="hidden" data-av-secret-source id="key1src">
<span class="av-secret__actions">
<button class="av-btn av-btn--ghost av-btn--sm" type="button"
data-av-secret-toggle aria-pressed="false">
<span data-av-secret-label>Reveal</span>
</button>
<button class="av-btn av-btn--ghost av-btn--sm" type="button" data-av-clipboard="#key1src">
<span data-av-clipboard-label>Copy</span>
</button>
</span>
</span>A select-all over a column has three states, not two
A checkbox that reads checked when half its column is checked is a lie the reader acts on: they untick it expecting to clear the column and clear nothing, because it was never on.
[data-av-matrix] sets indeterminate — a property, so it cannot be written in markup and has to be set on every change — and aria-checked="mixed" alongside it. Both are needed: a native checkbox with indeterminate set still reports itself as unchecked to the accessibility tree, so without the ARIA the third state is visible and inaudible.
html
<table class="av-matrix" data-av-matrix>
<thead>
<tr>
<th scope="col" class="av-matrix__label">Capability</th>
<th scope="col">
<span class="av-matrix__col">
<span class="av-matrix__col-name">Admin</span>
<label class="av-matrix__all">
<input class="av-check" type="checkbox"
data-av-matrix-all="admin" data-av-matrix-label="Admin">
All
</label>
</span>
</th>
</tr>
</thead>
<tbody>
<tr class="av-matrix__section"><th scope="colgroup" colspan="2">Members</th></tr>
<tr>
<th scope="row" class="av-matrix__label">Invite members</th>
<td data-av-matrix-col="admin">
<label class="av-matrix__cell">
<input class="av-check" type="checkbox" aria-label="Invite members, Admin">
</label>
</td>
</tr>
</tbody>
</table>The matrix is a real <table>, and that is the whole accessibility story. A lone checkbox in a cell means nothing; the same checkbox with a row header and a column header is announced as "Invite members, Admin, checkbox, not checked". Build it out of divs and that sentence disappears.
Three details in that markup are design rather than plumbing:
- The control is
.av-check, the one painted checkbox in the product (src/scss/components/_check.scss). The matrix sets--av-check-sizeon the table and every box below it follows, so the grid gets a 20px control without the size being written ninety times. .av-matrix__cellis a<label>filling the whole cell, so the hit target is the rectangle rather than the box in the middle of it.- The group break is a
<th scope="colgroup">, not a<td>holding a grey slab. It is a heading, so it is marked up as one, and the rows beneath it are grouped by the space around it.
The annual price is in the markup, not divided by twelve in the browser
Both figures are integer minor units, because "monthly ÷ 12, less the discount" is a pricing decision that belongs to whoever set the prices. Computing it client-side produces a number that disagrees with the invoice by a rounding cent, on the one page where that matters most.
html
<div class="av-plans" data-av-plans data-av-state="monthly" data-av-currency="EUR">
<p class="av-pricing-card__price">
<span data-av-plan-price data-av-price-monthly="4900" data-av-price-yearly="4083">€49.00</span>
<span class="av-pricing-card__period" data-av-plan-period>/month</span>
</p>
</div>Each facet group declares how it matches
"Checked" means three different things on one filter panel: a category list is any of, a status is exactly one, a rating is a floor, a price is a ceiling. Inferring that from the input type gets two of the four wrong, so the <fieldset> says which it is.
html
<form class="av-facets" data-av-facets="#storeResults" data-av-currency="EUR"
aria-label="Filter products">
<fieldset class="av-facets__group" data-av-facet-group="brand" data-av-facet-kind="any">
<legend class="av-facets__legend">Brand</legend>
<label class="av-facets__option">
<input type="checkbox" name="brand" value="northwind">
<span class="av-facets__option-text">Northwind</span>
</label>
</fieldset>
<div class="av-facets__foot">
<button class="av-btn av-btn--ghost" type="reset">Reset</button>
<button class="av-btn av-btn--primary" type="submit">Apply</button>
</div>
</form>The panel is a real <form>, so Reset is type="reset" and Enter submits — both come free and both have to be re-implemented if you build it out of buttons. Items are hidden with the hidden attribute rather than removed, so the DOM the reader tabbed into is the DOM that comes back, and the result count is a live region because nothing else on screen reports that anything happened.
Grid and list are the same DOM
[data-av-view-toggle] swaps one modifier on the container. The cards are not rebuilt, so tab order and reading order do not change under a reader who cannot see that the layout did — the same decision the files application already makes.
html
<div class="av-segmented" role="radiogroup" aria-label="View"
data-av-view-toggle="#storeResults" data-av-view-base="av-product-grid">
<label><input type="radio" name="view" data-av-view="grid" checked> Grid</label>
<label><input type="radio" name="view" data-av-view="list"> List</label>
</div>The card is not a link
A card-sized <a> swallows the Add-to-basket and wishlist controls inside it. Nested interactive content is invalid, and in practice the browser resolves it by making those buttons unreachable.
.av-product-card__title a::after stretches the hit area over the card instead, which gives a pointer user the large target without taking the controls away from anyone. The focus ring is drawn on the card via :has(), because the element that actually takes focus is only as wide as its text.
Read next: Utility & Error Pages.