# You build the screens. The SDK reports each step.

> You build the checkbox, the button, and the page. A browser SDK that renders nothing records the ceremony you built, and a checker tests it at three screen sizes.

Source: https://esigncomply.com/product/ceremony-sdk

`@esigncomply/browser`

`@esigncomply/browser` renders nothing. It observes your elements, reports each step to Esign Comply, and tells your code when the ceremony can proceed.

[Get started](https://esigncomply.com/signup) · [Read the quickstart](https://esigncomply.com/docs/quickstart)

## Attach, present, observe, complete

Present each document and satisfy the session's required steps before completing.

1. **Attach**

   Create the session on your server and send only the short-lived client token to the browser.

2. **Present**

   Present each document through the link you built. The SDK reports whether the link serves the registered text.

3. **Observe**

   Pass the assent region, the checkbox, and the submit button. The SDK observes those elements and reports each step.

4. **Complete**

   Complete from your real submit handler. `ceremony.remainingSteps()` tells your UI when to enable the button.

`@esigncomply/react` adds `useCeremony` and `useDocument` hooks with no visual components.

Browser

```
import { EsignComply } from "@esigncomply/browser";

const sessionResponse = await fetch("/api/ceremony", { method: "POST" });
if (sessionResponse.ok === false) throw new Error("Unable to create ceremony");
const { clientToken, documents } = await sessionResponse.json();
// clientToken is a short-lived esc_ct_... token, not a secret API key.

const ceremony = await EsignComply.attach({ clientToken });

await ceremony.presentDocument({
  versionId: documents[0].version_id,
  mode: "hyperlink",
  link: document.querySelector("#tos-link"),
});

await ceremony.presentDocument({
  versionId: documents[1].version_id,
  mode: "hyperlink",
  link: document.querySelector("#privacy-link"),
});

ceremony.observeAssent({
  region: document.querySelector("#assent"),       // notice text, links, checkbox, button
  checkbox: document.querySelector("#agree"),
  submit: document.querySelector("#create-account"),
});

// The page links to the resolved versions above.
// Call this from the real submit handler, after the SDK records trusted intent.
async function finishSignup() {
  const result = await ceremony.complete(); // { recordId, receipt, verifyUrl }
  await confirmSignupOnYourServer(result.recordId); // Your authenticated server route
}
```

## What the SDK does on your page

### What it measures

Checks cover the document served, link styling and placement, visible text against the registered version, and the assent region's markup, styles, layout, and initial control state.

Live EU capture defaults to submitted inputs and necessary transaction or session data; use synthetic checks for richer diagnostics unless the live capture is separately cleared or consented to where required.

### What blocks live completion

- A checkbox checked at load.
- A programmatic click instead of a trusted user event.
- A prefilled typed-name field.
- A link that does not serve the registered text.

Test mode reports findings without blocking.

### What it never collects

- Content outside the elements you pass it
- Other form fields
- Keystrokes
- Screenshots
- Cookies
- Cross-site identifiers

## Conformance rules drawn from case law

Keep the notice and button in the same viewport and make links recognizable. A button label alone does not satisfy the notice rule.

### Checked as events arrive

The conformance engine evaluates relevant events as they arrive, checking controls, notice placement, link visibility and contrast, action wording, and registered versions as applicable.

### Findings you can act on

Run the conformance checker over your test records. Each finding names the rule, what was measured, and the fix.

### Errors an AI can fix

SDK errors include a rule ID and a suggested fix you can pass to your coding tool.

### Measured facts are sealed

We seal the measured facts. Adopted blocking conditions prevent live completion; warnings and new advisories do not.

Sources

### Decisions the rules draw on

The rules draw on these decisions. On top of them, Esign Comply sets its own policy for when a flow needs a checkbox or a typed name. The evidence report prints the measurements, and conformance findings are stored beside the record.

- [Meyer v. Uber](https://opencasebook.org/casebooks/19251-contracts-2026/resources/11.1.4-meyer-v-uber-technologies-inc/)
- [Berman v. Freedom Financial](https://openjurist.org/30/f4th/849/daniel-berman-v-freedom-financial-network-llc)
- [Cullinane v. Uber](https://www.faegredrinker.com/-/media/files/insights_db/publications/2018/08/cullinane-v-uber.pdf?la=en&hash=D30D0AFB9465944EF83BCE65BEEB36F44153BF77)
- [Chabolla v. ClassPass](https://cdn.ca9.uscourts.gov/datastore/opinions/2025/02/27/23-15999.pdf)
- [Godun v. JustAnswer](https://law.justia.com/cases/federal/appellate-courts/ca9/24-2095/24-2095-2025-04-15.html)
- [Good v. Uber](https://law.justia.com/cases/massachusetts/supreme-court/2024/sjc-13490-0.html)

`@esigncomply/browser`

## Design targets

### Size

**under 15 KB**

Compressed.

### Dependencies

**0**

No third-party dependencies.

### Main thread

**50 ms**

No main-thread blocking above this.

## Your UI. Our rules. Independent evidence.

[Get started](https://esigncomply.com/signup) · [Documentation](https://esigncomply.com/docs)

Free plan: 10 live signatures a month and a full test mode. No card required.

---

Every page on esigncomply.com has a Markdown version at the same URL plus `.md` (the home page is `https://esigncomply.com/index.md`). https://esigncomply.com/llms.txt lists them.
