Data display

Evidence relationship

<forma-evidence-relationship>

Makes claim-to-evidence relationship type and scope explicit rather than relying on proximity alone.

Authoring tag
<forma-evidence-relationship>
Category
Data display
Behavior owner
Application content
Canonical source
patterns/evidence-relationship.html

Purpose

An evidence relationship states, in one article, a claim, the type of relationship the evidence has to it (supports, contradicts, partially supports), the evidence itself, its source and the scope it covers, plus its current standing. Placing evidence next to a claim does not say how they relate; this component makes the relationship type a visible label. Forma lays out the header, body and footer; the relationship type, scope and status are application facts and Forma never infers them.

Use when

  • A claim (ready to deploy, control is effective, requirement met) is backed or challenged by specific evidence.
  • The evidence covers a particular scope (commit, environment, period) that may differ from the claim's scope.
  • Reviewers must see whether evidence is current, stale or superseded.

Avoid when

Behavior to know

  • Article grid with 0.75rem gaps: header (relationship type and claim), body, footer.
  • The relationship type is text in the header, typically a .forma-component-kicker.
  • The body is a grid of short labelled statements (Evidence, Source, Scope).
  • Trailing margins inside the header and body are removed so the card stays compact.

Basic example

The smallest correct markup: the canonical pattern from patterns/evidence-relationship.html inside its public tag. Copy this first, then adapt labels, names and state.

Canonical

Minimal evidence relationship

Rendered from the canonical pattern file.

Supports

Claim: deployment is ready

Evidence: Required checks passed.

Source: CI run 1042

Scope: commit abc123

Current
HTML · Minimal evidence relationship Raw HTML for HTML · Minimal evidence relationship
<forma-evidence-relationship class="forma-component-tag">
<article class="forma-evidence-relationship" aria-labelledby="relationship-claim"><header><p class="forma-component-kicker">Supports</p><h2 id="relationship-claim">Claim: deployment is ready</h2></header><div class="forma-evidence-relationship__body"><p><strong>Evidence:</strong> Required checks passed.</p><p><strong>Source:</strong> CI run 1042</p><p><strong>Scope:</strong> commit abc123</p></div><footer><span class="forma-status-lozenge">Current</span></footer></article>
</forma-evidence-relationship>

Click or tap the code once to select all of it, then copy.

Examples

Scenario

Contradicting evidence

A load test contradicts the claim that the service meets its latency target. The relationship type Contradicts is the first thing read, and the footer states the evidence is current.

Contradicts

Claim: checkout meets the 400 ms p95 latency target

Evidence: Load test measured 612 ms p95 at 2,000 requests per second.

Source: Performance run PR-5520

Scope: EU West, release candidate rel-2026.10-rc2

Current
HTML · Contradicting evidence Raw HTML for HTML · Contradicting evidence
<forma-evidence-relationship class="forma-component-tag">
  <article class="forma-evidence-relationship" aria-labelledby="evidence-relationship-contradicting-evidence-claim">
    <header>
      <p class="forma-component-kicker">Contradicts</p>
      <h2 id="evidence-relationship-contradicting-evidence-claim">Claim: checkout meets the 400 ms p95 latency target</h2>
    </header>
    <div class="forma-evidence-relationship__body">
      <p><strong>Evidence:</strong> Load test measured 612 ms p95 at 2,000 requests per second.</p>
      <p><strong>Source:</strong> Performance run PR-5520</p>
      <p><strong>Scope:</strong> EU West, release candidate rel-2026.10-rc2</p>
    </div>
    <footer><span class="forma-status-lozenge">Current</span></footer>
  </article>
</forma-evidence-relationship>

Click or tap the code once to select all of it, then copy.

Scenario

Evidence covering part of the scope

Tests passed, but only for one of the two platforms the claim covers. The relationship is Partially supports, the scope line names what is covered, and the footer says the evidence is stale because a newer commit exists.

Partially supports

Claim: the mobile app is ready for release

Evidence: UI regression suite passed, 412 of 412 tests.

Source: CI run 1187

Scope: Android only, commit a41c9e0. iOS has no run for this commit.

Stale: 3 newer commits
HTML · Evidence covering part of the scope Raw HTML for HTML · Evidence covering part of the scope
<forma-evidence-relationship class="forma-component-tag">
  <article class="forma-evidence-relationship" aria-labelledby="evidence-relationship-partial-scope-claim">
    <header>
      <p class="forma-component-kicker">Partially supports</p>
      <h2 id="evidence-relationship-partial-scope-claim">Claim: the mobile app is ready for release</h2>
    </header>
    <div class="forma-evidence-relationship__body">
      <p><strong>Evidence:</strong> UI regression suite passed, 412 of 412 tests.</p>
      <p><strong>Source:</strong> CI run 1187</p>
      <p><strong>Scope:</strong> Android only, commit <span class="forma-identifier">a41c9e0</span>. iOS has no run for this commit.</p>
    </div>
    <footer><span class="forma-status-lozenge" data-state="unknown">Stale: 3 newer commits</span></footer>
  </article>
</forma-evidence-relationship>

Click or tap the code once to select all of it, then copy.

Mobile

Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.

Mobile example

Mobile evidence relationship

A supporting relationship at phone width. The single-column layout is unchanged; long claims and scope lines wrap.

Static specimen. Its links point to placeholder destinations that do not exist on this site. Its controls are shown for their markup and appearance and cannot be operated here.

Viewport width

Frames narrower than the selected width show the component at the width available.

What changes at narrow widths

  • The component is a single-column grid at every width, so there are no breakpoints.
  • Long claims and scope statements wrap; identifiers should use Identifier & critical value so hashes break safely at 320px.
  • The footer status keeps its text and glyph; a Status lozenge does not wrap internally, so keep its text short.
  • Links inside the body keep their own touch targets; the article itself is not interactive.
HTML · Mobile evidence relationship Raw HTML for HTML · Mobile evidence relationship
<forma-evidence-relationship class="forma-component-tag">
  <article class="forma-evidence-relationship" aria-labelledby="evidence-relationship-mobile-evidence-claim">
    <header>
      <p class="forma-component-kicker">Supports</p>
      <h2 id="evidence-relationship-mobile-evidence-claim">Claim: backups are restorable</h2>
    </header>
    <div class="forma-evidence-relationship__body">
      <p><strong>Evidence:</strong> Monthly restore drill completed in 38 minutes.</p>
      <p><strong>Source:</strong> <a href="#evidence-relationship-mobile-evidence-drill">Restore drill record DR-0926</a></p>
      <p><strong>Scope:</strong> Production database, snapshot of 26 Sep 2026</p>
    </div>
    <footer><span class="forma-status-lozenge" data-state="ok">Current</span></footer>
  </article>
</forma-evidence-relationship>

Click or tap the code once to select all of it, then copy.

Baseline

Mobile · 320px

The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.

Viewport width

Frames narrower than the selected width show the component at the width available.

API and configuration

Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.

Native and ARIA attributes
AttributeOnValuesDefaultDescription
aria-labelledbyarticle.forma-evidence-relationshipid of the claim heading—Names the article by its claim.
CSS hooks (derived from dist/all.css)
HookKindValues or defaultDescription
.forma-evidence-relationshipBlock class—Root article; a grid of header, body and footer with 0.75rem gaps. Removes the trailing margin of the header's last child.
.forma-evidence-relationship__bodyElement class—Grid of labelled evidence statements with 0.5rem gaps; its last child has no bottom margin.
Keyboard interaction
KeysResult
NoneStatic content; links inside the body are reached with Tab.

Form behavior

Not a form control.

States

Evidence relationship states
StateHow it is expressedPresentation
Relationship typetext in the header (Supports, Contradicts, Partially supports)Supplied by the application; Forma applies no type-specific styling.
Evidence standingStatus lozenge text in the footerCurrent, Stale, Superseded and so on, stated in words.

Accessibility

Forma provides

  • Uses an article with a header, body and footer so the structure is exposed.
  • Presents relationship type and standing as text, never as color or position alone.

Your application supplies

  • Put the relationship type before the claim heading so it is read first.
  • Label each body statement (Evidence, Source, Scope) in visible text.
  • State when scope differs from the claim, and when evidence is stale or superseded.
  • Choose the heading level to fit the page outline.

Responsive behavior

  • Single column at every width; no breakpoints.
  • Text wraps; the article fits its container.

Motion

  • No animation: the component is static.

Usage guidance

Do

  • Use a fixed, application-defined vocabulary of relationship types.
  • Show scope for every piece of evidence.

Avoid

  • Implying support by placing evidence next to a claim without a relationship label.
  • Treating stale evidence as proof of current state.

Verification specimens

Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.