A practical decision tool for distinguishing eligible Squarespace published-page repairs from managed checkout and embedded-content boundaries.
<main>
<p class="eyebrow">Accessibility implementation worksheet</p>
<h1>Where does a Squarespace repair actually run?</h1>
<p>Before choosing a repair route, identify the page owner and test the published flow. A site-wide script may help on eligible published pages, but it does not give you control of every checkout or embedded third-party component. This small triage tool records the next check for three common locations.</p>
<section class="card">
<h2>Choose the affected location</h2>
<fieldset><legend>Where is the barrier visible?</legend>
<label><input type="radio" name="location" value="page" checked> A published Squarespace page</label>
<label><input type="radio" name="location" value="checkout"> Squarespace-managed checkout</label>
<label><input type="radio" name="location" value="embed"> Embedded third-party content</label>
</fieldset>
<label for="evidence">Observed barrier and page URL</label><textarea id="evidence" placeholder="Example: control has no readable name on the published page; include the exact URL"></textarea>
<button type="button" id="build">Show the next verification step</button>
<div id="result" role="status" aria-live="polite">Select a location and describe the issue.</div>
</section>
<section class="card"><h2>Keep the verification sequence clear</h2><ol><li>Confirm whether the current Squarespace plan offers site-wide Code Injection.</li><li>If eligible, add the approved snippet, save it, and verify it on published pages in ADAFix before enabling repairs.</li><li>Retest the actual affected flow with keyboard and assistive technology as appropriate; installation alone does not certify accessibility.</li><li>For managed checkout or embeds, identify the responsible platform or third party and record a separate review path.</li></ol></section>
<p>The <a href="https://adafix.app/platforms/squarespace.html">Squarespace accessibility repair eligibility and live checks</a> page describes the site-wide Code Injection route, its plan dependency, and the boundary for managed checkout and embedded content. This independent worksheet helps frame an inspection; it does not inspect a site or promise a fix.</p>
</main>