Cotality Design whitepaper

Cotality Placement QA

Design system for catching social-placement drift before export.

Built from a Cotality social-placement audit, this whitepaper captures how the Figma mirror, AE geometry, and live HTML QA tool became one review system.

01 Summary

What this system proves

I noticed concrete placement drift, turned the rules into a visible QA system, and built a practical handoff tool before my first interview.

The problem

Similar social assets showed inconsistent card width, vertical anchor, headline alignment, and optional mark placement.

The fix

The QA tool detects the visible card, compares it with format geometry, and renders a corrected version using the current spec.

The handoff

Figma documents the visual system, AE provides motion geometry, and HTML validates the exported frame.

3Social formats
31Figma variables
4Component sets
0Missing WEB syntax

02 Source model

Tool first, Figma mirrored

The live HTML tool is the operational placement spec for this case study. Figma records and explains the system so the design language remains inspectable.

LayerRole
HTML QA toolCurrent validation surface and operational spec.
Figma Design fileVisual mirror, token map, reusable guide components, and example documentation.
AE rigOriginal motion geometry and template defaults for placement.
Historical BibleReference context for where the placement rules began.

03 Scope

Three social formats

The system intentionally covers IG and FB social placements only. Static carousel and YouTube landscape video need separate process rules.

Reel

9:16
1080 by 1920 vertical social video.

Feed video

3:4
1080 by 1440 feed social video.

Square post

1:1
1080 by 1080 square social post.

04 Figma inventory

Captured design system

The Figma package reached phase 4 with pages, frames, component sets, variables, styles, accessibility notes, and production token sync.

31Variables
5Text styles
4Component sets
0Missing WEB syntax

Pages

Cover, Foundations, Social Formats, Guide Overlays, Placement Examples, and QA Tool Mapping.

Component sets

Guide Label, Format Frame, QA Status Chip, and Guide Overlay.

05 Captures

Figma evidence

These are exported from the editable Figma Design file and stored with the page so the design rationale is visible outside Figma.

Figma Foundations page for Cotality Placement QA
Foundations captures tokens, type, component language, and accessibility basis. Open full capture
Figma Placement Examples page showing drift and corrected examples
Placement Examples documents the drift versus corrected story. Open full capture
Figma note about live HTML refinement
Live HTML Refinement records production adjustments after the browser polish pass. Open full capture

06 Tokens

Color and overlay language

The palette uses Cotality's public brand feel plus QA-specific overlay states. Every overlay survives without color alone.

Ink#1e1405
Cream#f7efe2
Violet#a805fb
Coral#ff8e65
Safe zoneDashed green outline
Detected cardYellow measured box
Mark zoneBlue dashed box
BaselineMagenta dotted line

07 Checklist

Read-only QA logic

The checklist is computed from the loaded frame. It does not ask the reviewer to manually decide pass or fail.

Review areaWhat the tool checks
FormatImage loaded, ratio detected, ratio matches an approved preset.
PlacementCard found, inside safe zone, within maximum width, and anchored to the preset.
Visual rulesCard carries white text, headline alignment follows the preset, optional mark sits in the approved zone.
Corrected viewPlacement rows pass by construction because the tool renders the current standard.

08 Accessibility

508 is part of the system

The tool treats accessibility as production behavior, not a late review pass.

Interaction

  • Visible focus rings on controls.
  • Guide swatches are keyboard reachable.
  • Disclosure state and toggle state remain clear.
  • Motion respects reduced-motion preferences.

Perception

  • Status chips include visible text.
  • Overlays use hue, line style, label, and halo.
  • Contrast is measured against white text.
  • Layout avoids horizontal overflow at 360px.

The small detail that matters

The white divider and triangle on the violet placement card stay true to the AE rig. If a browser preview makes the divider read pink because of subpixel blending, the answer is a magnified detail crop, not thickening the production stroke.

09 Media pipeline

AE and AME proof outputs

The QA page audits still frames captured from public Cotality social video outputs. These motion examples show how the same placement system carries through AE correction and AME compression.

What the QA page proves

The browser tool validates a loaded frame against the current placement spec: format ratio, detected card, safe zone, anchor, card width, text color, headline alignment, and optional mark zone.

What the motion pass proves

The AEP uses the same visual rules to render corrected outputs. AME then compresses the final videos so the card edge, divider stroke, headline, and avatar detail stay clean on web playback.

Compression note

The social resize outputs are an approximate stress pass, not an exact Instagram or Facebook transcode. They resize each layout to a 720-wide H.264 version so the page can show how a disciplined AME master survives platform-style recompression.

Historical rule context remains available in the Placement Bible. The current operational check is the live QA tool.

10 Implementation map

Design to live tool

The whitepaper stays grounded because every design concept maps to the live HTML implementation.

Figma conceptHTML implementation
Format framesPRESETS and PRESET_ORDER
Guide overlaysOverlay toggles, swatches, and canvas drawing helpers.
Corrected exampletargetBox, renderCorrected, and drawCotalityCard
Checklist rowsCHECKS, STATE_LABEL, and scoring functions.
Accessibility behaviorARIA labels, focus styles, reduced-motion branch, and no color-only states.

11 Next

Where this goes

This artifact can now support the live QA tool in an interview, a portfolio case study, or a production handoff conversation.

Review

Use the live tool to run the three built-in social samples, one real upload, and still frames from the corrected motion exports.

Extend

If YouTube or webinar layouts matter, write a separate landscape video bible instead of folding it into this system.

Maintain

When HTML, AE, or AME settings change, update Figma and this whitepaper so the system remains aligned.