SAAS BRAND-TO-UI HANDOFF — BRANDFOLIA
Updated: 2026-11-04

FILLED IDENTITY RECORD — DAYMARK (fictional)
Brief: planning-software identity for small teams.
Input: a written service idea, no product photo or working app.
Voice: helpful and concrete; no invented features, integrations or savings.
Palette: violet #3E3A72 / pale base #F0EFFA / lilac #B6A5E2 / white #FFFFFF.
Source: https://brandfolia.com/work/daymark/
Files: identity JSON, actual SVG artwork, palette CSS, brandbook and board.
Boundary: no semantic-token library, interactive components or application code.

YOUR PRODUCT
Brand / product owner / design owner / developer / version / date:
Audience and verified task:
Available features and evidence:
Planned features (do not imply available):

ROLE MAPPING — PROPOSED UNTIL IMPLEMENTED AND TESTED
Role | value/font | surface/state | text/background contrast | test evidence | decision
Main text:
Supporting text:
Primary action:
Link / hover / focus:
Surfaces:
Status and error treatment:
Heading / body / label / data typography:
Brand colors are not automatic semantic tokens or accessibility approval.

COPY STATES — ONLY FOR BEHAVIOR YOUR PRODUCT SUPPORTS
Trigger | actual system state | message | recovery/next action | verified behavior
Empty:
Loading:
Success:
Failure:
No permission:

SCREENSHOT REGISTER
Asset | product version | real screen or concept | data permission/privacy check | caption | owner

IMPLEMENTATION REVIEW
[ ] Real and long text at narrow and wide widths.
[ ] Text/background contrast; hover and focus states.
[ ] Keyboard access and visible focus.
[ ] Error and recovery wording matches implemented behavior.
[ ] Product screenshots describe available features accurately.
[ ] Identity, component code and review record have clear versions.
WCAG contrast reference: https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html
A color-pair check alone does not verify full accessibility conformance.