Skip to content

Conformance rules

The 28 automated checks Esign Comply runs on a ceremony, what each one measures, its effect in live mode and how to fix a finding.

The conformance engine evaluates each ceremony event against the rules on this page. Every rule tests something Esign Comply can measure on its own record: the state of a control, the text of a notice, a contrast ratio, the order of events. The measurements are sealed into the record as facts. The pass or fail judgment is stored beside the record and is not printed on evidence reports or certificates.

Findings describe measurable design facts. They are not a statement that a flow is lawful or enforceable.

Findings are advisory. They exist so that you, or your AI coding tool, can read a rule ID and repair the interface before going live.

Two modes

Passive. Every test and live ceremony is evaluated as its events arrive. Each response from POST /v1/sessions/{id}/events carries a conformance object, the browser SDK emits a finding event, and in test mode the SDK logs each finding to the browser console with the rule ID and a link to this page.

Active. The CLI opens your page in a headless browser and runs the ceremony with a test signer at three viewport sizes: 390 by 844, 768 by 1024 and 1440 by 900.

npx esigncomply@latest check --url http://localhost:3000/signup

The active check also attempts violations and expects each one to be refused: submitting with the checkbox untouched, triggering a programmatic click, altering the document text in the page, calling the completion step from a different origin, and skipping the verification step. It posts a forged success to your application's callback and expects access to stay blocked, because your server must confirm the record itself (see Server confirmation). The command returns an exit code, so a regression such as a restyled link or a pre-checked box fails a CI build.

Each finding lists the rule, the status, the measurement, a plain-language fix and the prompt instruction it relates to. The dashboard offers a "Copy for AI" control that produces the findings as Markdown to paste back into your coding tool.

Levels and states

A finding has a status and a state.

Field Values Meaning
status pass, warn, block The result of the check. block and warn are the two levels a failed check can have.
state enforce, advise Whether the check can refuse a live record. advise means evaluated and stored, never a reason to refuse.

How the level and state of a check are decided for one session:

  1. The session's jurisdiction packs fire rules, for example US-08 or CA-01. A rule's record conditions name the checks that implement them and give each a level, Block or Warn.
  2. If a fired rule names the check, its level applies. Where several rules name it, the stricter level wins.
  3. A check is in the enforce state only when the rule that names it is part of the profile's adopted baseline and its pack has been reviewed by counsel. A rule that arrived later, from a newer pack version or a newly enabled pack, runs in advise until you adopt it. See Compatibility.
  4. If no fired rule names the check, it is still measured. It gets the default level shown on this page and, in live mode, the advise state.

What then happens:

Mode Effect
Test Nothing blocks. Every check is evaluated against the latest release as if adopted, and every finding is returned, including passes, so you can see what a live ceremony would require.
Live A finding with status: "block" and state: "enforce" stops sealing. POST /v1/sessions/{id}/complete returns 422 conformance_failed with the rule and the findings. A text mismatch under CR-08 is refused earlier, on the event, with render_mismatch. Warnings and advisories never stop a record.

If the page is repaired during the session, a later passing result for the same rule replaces the earlier failure.

"Live-mode effect" in the sections below is the effect when the check is enforced.

The finding object

{
  "rule": "CR-05",
  "status": "warn",
  "state": "enforce",
  "message": "Document link contrast against surrounding text is 1.5 to 1; at least 3 to 1 is expected, in addition to any underline.",
  "fix": "Give document links a colour that differs from the surrounding text by a contrast ratio of at least 3 to 1, and keep them underlined.",
  "measurement": { "contrast_ratio": 1.5, "underlined": true, "font_px": 14, "link_visible": true },
  "maps_to": ["US-11"],
  "event_type": "document.presented",
  "version_id": "dv_3kT9"
}
Field Description
rule The rule ID on this page. The same ID appears in SDK errors, API errors and the generated prompt.
message What was found.
fix A repair for the page. Present when the check did not pass.
measurement The numbers and values behind the result.
maps_to The pack rules that fired for this session and are implemented by this check.
event_type, version_id The event, and the document version where relevant, that produced the finding.

Where findings appear:

  • conformance.findings[] on each event response. Live mode returns only findings that did not pass.
  • findings[] on a conformance_failed or render_mismatch error.
  • conformance.results[] on the record, marked advisory, outside the sealed hash. Checks that ran in advise and were not met are listed in advisories[].
  • The dashboard, per record and per conformance run.

The rule set is versioned. This page describes rule set 2026.11.2, and each record pins the version it was evaluated under.

Rule index

Rule Check Default level Evaluated
CR-01 Affirmative assent control Block On the intent and consent events
CR-02 Notice text names every document Block On notice.captured
CR-03 Notice names the action control Warn On notice.captured
CR-04 Notice and control in the same viewport Block On notice.captured
CR-05 Document link contrast Warn On document.presented
CR-06 Notice font size and contrast Warn On notice.captured
CR-07 Single primary action control Warn On notice.captured
CR-08 Document links resolve to the registered version Block On document.presented
CR-09 Method matches context Block At completion
CR-10 Renewal terms beside a separate consent control Block On renewal_terms.presented
CR-11 Payment disclosures and acknowledgment label Block On notice.captured
CR-12 Electronic-signing statement in notice Warn On notice.captured
CR-13 Review before the final act Block At completion
CR-14 Storable, reproducible terms before assent Block On document.presented
CR-15 Offered languages and stored language Warn On document.presented
CR-16 Consumer e-consent steps complete Block At completion
CR-17 Verification complete for L2 and L3 Block At completion
CR-18 Jurisdiction, signer and document category confirmed Block At session creation
CR-19 Pack resolution finished before the ceremony Block At session creation
CR-20 Required strings present Block On notice.captured
CR-21 Renewal-terms prominence Warn On renewal_terms.presented
CR-22 Order of events Warn On consent and billing events, and at completion
CR-23 Separate controls Warn On the separate consent events
CR-24 Required facts present Block At session creation and at completion
CR-25 Disclosure language Warn No per-event finding in this rule set
CR-26 Tagged terms have captured headings Warn No per-event finding in this rule set
CR-27 Signer completeness Warn No per-event finding in this rule set
CR-28 Timing facts Block At completion

Pack rule IDs such as US-08 or CA-01 are listed with each pack in the pack catalogue.

CR-01 Affirmative assent control

Check. The assent control was unchecked or empty at load and was changed by a trusted user event.

Maps to. US-08, EU-01.

Measured. control (checkbox, typed, drawn or button), initial_state (unchecked, checked, empty, prefilled), trusted (whether the change came from a real user event). Evaluated on intent.captured and on every consent event: econsent.given, renewal.consent_given, electronic_agreement.given, sensitive_capture.consent_given.

Live-mode effect. Block.

Server-only sessions. In a session created with capture_mode: "server_only" your server reports the control, and it cannot observe a trusted user event. When the event reports a clear initial state and says nothing about trusted, the finding is Warn, never Block, with the message "The assent control was reported by the customer's server and was not observed by Esign Comply." It is still Block when your server itself reports initial_state: "checked" or "prefilled", or trusted: false.

How to fix. Render every checkbox unchecked and every typed-name field empty. Never prefill or pre-check an assent control. Let the user's own click or keystroke change the control, and remove any code that calls .click() or sets .checked on the user's behalf.

CR-02 Notice text names every document

Check. Notice text exists inside the assent region and contains the title of every document in the session.

Maps to. US-09.

Measured. notice_chars (length of the captured notice text) and missing_titles (document titles not found in it). The text of buttons and form controls is not counted as notice text.

Live-mode effect. Block.

How to fix. Put the notice text inside the container you pass to observeAssent as region, and name every document by its registered title, each linked to its document page.

CR-03 Notice names the action control

Check. The notice text names the action control by its label, for example "By clicking Create account", or the assent control is a checkbox whose own label states agreement to the named documents. A button label alone never satisfies this rule. Vague phrases such as "by clicking below" or "by continuing" are flagged.

Maps to. US-09.

Measured. names_action_control, checkbox_states_agreement, vague_phrase, submit_label.

Live-mode effect. Warn.

How to fix. Write the notice as: "By checking the box and clicking {button label}, you agree to the {document titles}." Use the exact label of the button. Do not use "by clicking below" or "by continuing".

CR-04 Notice and control in the same viewport

Check. The notice and the action control are in the same viewport at the signing act, and the notice is above or beside the control.

Maps to. US-10.

Measured. same_viewport, notice_above_action, notice_to_action_px, viewport (width and height). Not measured in minimal capture.

Live-mode effect. Block if the notice and the control cannot be seen together. Warn if they share the viewport and the notice sits below the control.

How to fix. Show the notice text directly above the action button, in the same container, visible without scrolling at 390 by 844.

CR-05 Document link contrast

Check. Document links differ from body text by color, with a contrast ratio of at least 3 to 1 against the surrounding text, in addition to any underline.

Maps to. US-11.

Measured. contrast_ratio (link color against the surrounding text), underlined, font_px, link_visible. Evaluated for hyperlink presentations. Not measured in minimal capture.

Live-mode effect. Warn.

How to fix. Give document links a color that differs from the surrounding text by a contrast ratio of at least 3 to 1, and keep them underlined.

CR-06 Notice font size and contrast

Check. The notice font size is at least body size and at least 12 px, and its contrast against the background is at least 4.5 to 1.

Maps to. US-12.

Measured. font_px (smallest size in the notice text), body_font_px, contrast_ratio (lowest contrast of the notice text against its background). Not measured in minimal capture.

Live-mode effect. Warn.

How to fix. Make the notice at least as large as body text and at least 12 px, with a contrast ratio of at least 4.5 to 1 against its background.

CR-07 Single primary action control

Check. No more than one primary action control is inside the assent region. Competing controls in the viewport are counted.

Maps to. US-13.

Measured. primary_buttons (submit buttons and elements marked data-esc-primary inside the region), competing_controls_in_viewport (visible primary controls outside it).

Live-mode effect. Warn.

How to fix. Keep one primary button inside the assent container. Put social sign-in buttons in a separate container with their own notice and their own session.

CR-08 Document links resolve to the registered version

Check. Each document link resolves to the registered version, and inline content matches render_hash.

Maps to. US-02, US-14.

Measured. For inline and scrollbox: mode, render_hash_reported, render_hash_registered. For hyperlink: mode, link_href, link_target_render_hash, render_hash_registered, target_checked. A link fails when it points outside the domain, or when the text of the page behind it was fetched and does not match. In minimal capture the presentation is recorded against the registered artifact.

Live-mode effect. Block. The API refuses the event with 422 render_mismatch and keeps it as evidence of what the page presented.

How to fix. Serve each document at a stable page on your domain that renders the registered version by its version ID, unmodified, inside <article data-esc-document>. For inline presentation, render the content fetched from Esign Comply inside the container you pass to presentDocument. Do not copy document text into the repository. If the text changed, publish it as a new version.

CR-09 Method matches context

Check. The method matches the context: a checkbox for purchase, trial, renewal and consumer profiles, and a typed name or stronger for signature profiles. This is Esign Comply policy, not a legal requirement.

Maps to. US-17.

Measured. method, profile_kind (signature or acceptance), purpose, signer_class.

Live-mode effect. Block.

How to fix. For signature profiles, such as an NDA or a contract, use a typed-name field and a signing button. For consumer, purchase, trial and renewal ceremonies, use an unchecked checkbox with an explicit statement, then a button.

CR-10 Renewal terms beside a separate consent control

Check. The renewal terms are shown clearly and conspicuously in visual proximity to an unchecked consent control. By Esign Comply policy that control is separate from the terms checkbox.

Maps to. US-20.

Measured. wording_present and missing_fragments (the renewal consent sentence from required_strings), empty_elements (of renewal_term, price, cancellation_policy, cancel_path), proximity_px (distance from the terms to the consent control), same_container.

Live-mode effect. Block.

How to fix. Show the renewal consent sentence from required_strings with the renewal term, price, cancellation policy and cancel path filled in, directly beside its own unchecked checkbox. Report the block with ceremony.renewalTerms({ region, elements }) and the checkbox with ceremony.renewalConsent({ checkbox }).

CR-11 Payment disclosures and acknowledgment label

Check. For a covered payment obligation, including a conditional one, the required disclosures appear directly before ordering and the final button carries the sole approved, legible acknowledgment label.

Maps to. EU-10.

Measured. submit_label and approved_labels. Evaluated for consumer purchase, trial and renewal purposes when the EU or UK pack applies. The approved labels come from the paid_order_button entry in required_strings, by language.

Live-mode effect. Block.

How to fix. Label the final button only with the approved wording for the language, for example "Order with obligation to pay", and show the required order information directly above it.

CR-12 Electronic-signing statement in notice

Check. On signature profiles the notice contains the electronic-signing statement.

Maps to. US-04.

Measured. statement_found.

Live-mode effect. Warn.

How to fix. Use the notice: "By typing your name and clicking {button label}, you agree to sign this agreement electronically and to be bound by it."

CR-13 Review before the final act

Check. A review is presented before the final act for signature and purchase contexts. In covered EU orders the consumer can identify and correct inputs before ordering.

Maps to. US-05, EU-09.

Measured. review_presented, correctable.

Live-mode effect. Block for covered EU orders without a correctable review. Otherwise Warn.

How to fix. Show a summary before the final act and call ceremony.reviewPresented({ container }). For EU consumer orders include a "Review or correct your details" control.

CR-14 Storable, reproducible terms before assent

Check. Covered EU flows offer the exact pinned terms in a storable and reproducible form before assent. A later receipt is not a substitute.

Maps to. US-29, EU-09.

Measured. downloadable, printable. Evaluated when the EU, UK or CH pack applies.

Live-mode effect. Block for covered EU flows with consumer signers. Otherwise Warn.

How to fix. Offer "Download or print the exact terms" for the session-pinned version before the assent control. Mark the controls with data-esc-download and data-esc-print, or pass them to presentDocument as downloadControl and printControl.

CR-15 Offered languages and stored language

Check. The offered languages are disclosed, and the stored language is checked against the consumer's choice and mandatory local requirements, not against the locale alone.

Maps to. EU-13.

Measured. presented_language, offered_languages, locale. Evaluated when the EU, UK or CH pack applies.

Live-mode effect. Warn. Block for an unmet mandatory local requirement. Rule set 2026.11.2 reports this check at Warn.

How to fix. Declare the offered languages in context.facts["offered_languages"] when you create the session, and record the signer's choice with ceremony.languageSelected(code).

CR-16 Consumer e-consent steps complete

Check. The consumer electronic-records consent steps (disclosure, access demonstration, consent) are complete where the profile requires them.

Maps to. US-21, US-22, US-23, US-24.

Measured. missing_steps among disclosure.presented, access.demonstrated and econsent.given.

Live-mode effect. Block. The API also refuses completion with steps_incomplete while a required step is missing.

How to fix. Run presentDisclosure, demonstrateAccess and giveEConsent before the assent control. See Consumer e-consent.

CR-17 Verification complete for L2 and L3

Check. Verification is complete for L2 and L3 sessions.

Maps to. US-36.

Measured. assurance_level, verified.

Live-mode effect. Block. The API also refuses completion with steps_incomplete while identity.verified is missing.

How to fix. Call ceremony.verify.start({ method }) and ceremony.verify.confirm({ code }) before the signing act. See L2 verification.

CR-18 Jurisdiction, signer and document category confirmed

Check. The applicable jurisdictions, the signer class and country, and the document category are confirmed.

Maps to. EU-08.

Measured. This rule is applied when the session is created, from the inputs you send: signer.class, signer.country, signer.region and context.facts["document_category"]. It produces no per-event finding in rule set 2026.11.2. Missing inputs appear in the session's warnings[] (for example signer_country_missing, signer_class_missing, document_type_requires_review:<id>), and the applied packs with their reasons are recorded on the session and the record.

Live-mode effect. Block for unresolved EU cases pending review. A document category on an applied pack's exclusion screen is refused with 422 document_type_excluded.

How to fix. Send the signer's class and country, and the state for U.S. signers, from your own form or account data. Send the document category where a pack asks for it. Do not guess location from an IP address. See Jurisdictions.

CR-19 Pack resolution finished before the ceremony

Check. Pack resolution finished before the ceremony starts: signer.region is present, or the profile's unknown-state rule has been applied and recorded.

Maps to. JR-4, JR-5.

Measured. Applied when the session is created. The session and the record carry the applied packs with their reasons. When a U.S. signer has no region and the profile enables state packs, the session carries the warning signer_region_missing.

Live-mode effect. Block only when the profile sets on_unknown_region to reject. The session is then refused with 422 signer_region_required.

How to fix. Collect the signer's state in your form and pass it as signer.region, for example US-CA. Or choose strictest or base_only for on_unknown_region on the profile.

CR-20 Required strings present

Check. Every entry in required_strings[] is present in the captured assent region or in the named slot. Quoted statutory text must match exactly. Each element of an element list must have a captured value.

Maps to. SP-1 and the fixed-string tables of each state pack.

Measured. For verbatim strings: slot, rule, missing_fragments. For element lists: slot, rule, empty_elements. Only entries with check: true are looked for. The renewal consent sentence is covered by CR-10 and the paid-order button label by CR-11.

Live-mode effect. Block where the pack rule that carries the string is a Block rule. Otherwise Warn.

How to fix. Render the string for each slot from required_strings verbatim, inside the assent region or in an element marked data-esc-slot="<slot>". Statutory text cannot be reworded. Fill every element listed for an element slot and pass the values in observeAssent({ slots }).

CR-21 Renewal-terms prominence

Check. The font size, weight and color contrast of the renewal block relative to the surrounding text, and any set-off, are measured and stored.

Maps to. CA-08, DE-10, VA-05.

Measured. font_px, surrounding_font_px, font_weight, contrast_ratio, set_off. Not measured in minimal capture.

Live-mode effect. Warn.

How to fix. Set the renewal terms in type at least as large as the surrounding text, in contrasting type, font or color, or set them off with a border, a background, symbols or marks.

CR-22 Order of events

Check. The renewal or trial disclosure block was captured before the consent event and before any billing.confirm event, and the terms were presented before the reported payment event.

Maps to. NY-03, MA-05, VA-02.

Measured. On renewal.consent_given and billing.confirm: renewal_terms_sequence, event_sequence. At completion, when a payment event was reported: document_sequence, billing_sequence.

Live-mode effect. As the state rule that fired states.

How to fix. Present the renewal or trial disclosure block before the consent control is used and before the page submits payment. Present the terms and capture assent before the page starts billing. Call ceremony.billingConfirm() immediately before the payment request.

CR-23 Separate controls

Check. Each rule that requires its own unchecked control has a distinct control with its own event: agreement to transact electronically, consent to sensitive capture, and terms assent distinct from data consent.

Maps to. CA-01, CA-07, CA-15, VA-01, VA-15, DE-15.

Measured. separate_control, control. Evaluated on renewal.consent_given, electronic_agreement.given and sensitive_capture.consent_given.

Live-mode effect. As the state rule that fired states.

How to fix. Give each of these consents its own unchecked checkbox, distinct from the terms checkbox, and report it with its own SDK call: renewalConsent, electronicAgreement or sensitiveCaptureConsent.

CR-24 Required facts present

Check. Every fired rule has the context.facts keys it needs.

Maps to. JR-18.

Measured. missing_facts. At session creation each missing key is also listed as the warning fact_missing:<key>.

Live-mode effect. Block for Block rules: when an adopted Block condition that fired lacks a fact, the session is refused with 422 jurisdiction_fact_required, naming the key and the rule. Otherwise Warn, and the rule does not fire.

How to fix. Send each listed key in context.facts when you create the session. Each pack page in the pack catalogue lists the fact keys its rules read.

CR-25 Disclosure language

Check. Required disclosures were captured in the active language, and the customer declared the languages the offer is made in.

Maps to. VA-06, MA-03.

Measured. The rule compares the language of the captured disclosures with the languages the customer declared. It is evaluated from pack rows. Rule set 2026.11.2 returns no per-event finding for it.

Live-mode effect. As the state rule that fired states.

How to fix. Declare the languages the offer is made in when you create the session, and present each required disclosure in the language the signer is using.

CR-26 Tagged terms have captured headings

Check. Tagged terms have a captured heading that names the term, with measured type size and weight.

Maps to. TX-03, TX-04.

Measured. The heading that names the tagged term in the captured assent region, with its type size and weight. It is evaluated from pack rows. Rule set 2026.11.2 returns no per-event finding for it.

Live-mode effect. As the state rule that fired states.

How to fix. Give each tagged term its own heading that names the term, in capitals or contrasting type, inside the assent region. Do not rely on a general reference to linked terms. Where the pack supplies the heading text, take it from required_strings.

CR-27 Signer completeness

Check. The parties a state rule requires, for example employer and employee, or the party to be charged, each have a signing act on the pinned version.

Maps to. MA-08, TX-05, DE-11, VA-11.

Measured. The signing acts recorded for the same pinned document version. It is evaluated from pack rows. Rule set 2026.11.2 returns no per-event finding for it.

Live-mode effect. As the state rule that fired states.

How to fix. Run one ceremony per required party on the same document version. Each signer is a separate session and a separate record.

CR-28 Timing facts

Check. Asserted delivery and expiry times meet the gap a state rule requires, and the delivery time precedes the signing act.

Maps to. FL-05, MA-08.

Measured. delivered_at, start_date, review_period_days, days_before_signing, days_before_start. The inputs are facts you assert on the session: the time the document was delivered, and where they apply a start date and a review period. Esign Comply does not verify them. Evaluated at completion when a delivery time was sent.

Live-mode effect. Block.

How to fix. Deliver the document before the signing act and by the period the rule states, and send the delivery time in context.facts under the key the pack lists.

Working with an AI tool? This page is also available as Markdown: /docs/conformance.md