Draft for counsel. Not published legal advice. Deific Connector is a Scope Labs LLC product. This is not a product of anthropic.

Accessibility

Last updated: 4 October 2026 · Draft 1.1

DRAFT — NOT YET REVIEWED BY COUNSEL. This statement was checked against the local marketing pages on 4 October 2026 (index.html and mobile/index.html) and against the legal pages generated with it. It is a goal plus a list of limits. It is not a certification, not an independent audit, and not a warranty that every person can use the page. An accessibility statement that overstates is worse than none. If a later page works differently, this statement is revised before that page is described as if this one still applied.

Our position

Scope Labs wants the public Deific website to meet Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

That is a goal we intend to work toward. It is not a certification. No one has certified these pages. No independent accessibility audit has been done. We do not claim the pages conform today.

This statement is about the Deific marketing site as it exists in the local mock. The Connector's own interface, when a build ships, is not described here as conforming or as failing. That interface was not reviewed for this draft. Before a Connector UI is held out under this statement, the statement has to be read against that UI and updated first.

We do not put an accessibility overlay or widget on the page, and we will not treat an overlay as a fix. An overlay is not a repair of the page, and it is not a conformance claim. We will not say that a third-party widget makes these pages meet WCAG. Reports should describe the barrier. They are not a request to add a widget.

Deific is a Scope Labs product. This is not a product of anthropic.

What these pages do today

Checked by reading the local files, not by a screen-reader session and not by a contrast tool.

Text page, with a visual layer. The words of the page are in HTML: headings, paragraphs, buttons, and links. The moving pictures sit in canvases beside or behind that text.

Background canvases are marked decorative. On the desktop page, the starfield (#stars), the neural-net canvas (#neural), the sun flare (#sunflare), and the accent canvas (#accents) are aria-hidden="true". On the mobile page, the sky canvas (#mobile-sky) is aria-hidden="true". The letter-by-letter spark canvas is also aria-hidden="true". They are not the text.

One canvas is exposed as an image. The "code" picture (canvas.city-canvas) has role="img" and a text label: "Helicopter orbit of the merged ws-relay codebase. Files and modules assemble themselves into one model." It is drawn with a two-dimensional canvas (getContext("2d")) that plots a scene with depth. It is not a WebGL context. There is no webgl context in either page. The label is one sentence. It is not a text equivalent of every file drawn in that picture, and the picture is not keyboard-operable.

Reduced motion is wired, and this is what it actually does. Both pages read prefers-reduced-motion: reduce once, when the script loads.

• Desktop starfield, neural canvas, sun flare, and accents: if reduced motion is on at load, the script draws one still frame and does not start the animation loop. It also does not attach the pointer-move handler that otherwise nudges that sky. If reduced motion is off, that sky animates and follows the pointer.
• The letter sequence (the D-O-N-N-A expansion) and its spark canvas: if reduced motion is on at load, the script marks the sequence settled and does not start the spark loop. CSS in that same case turns off the letter entrance animations and shows the letters. If reduced motion is off, the letters animate and a pointer or keyboard focus on a letter can light the spark canvas.
• The code-orbit canvas: if reduced motion is on at load, the script draws one frame and does not continue the orbit. If it is off, the orbit runs while the canvas is on screen.
• Mobile sky: if reduced motion is on at load, the script draws one frame and does not keep looping. A CSS rule also drops that canvas's opacity. If reduced motion is off, the dots drift.
• CSS animations on the bridge diagram (shimmer, glow, pulse, breathe) and on the letter sequence are turned off under prefers-reduced-motion: reduce, on both pages. Smooth scrolling is turned off in that case. On the desktop page the tall spacer bands (.sky-band) are hidden in that case so the scroll is not padded by empty sky.
• This pass also adds a page-level CSS backstop under the same media query: CSS animations and transitions on the marketing pages are forced to a near-zero duration. That backstop does not stop a canvas loop. The canvas loops stop only because of the script branches above.

Focus. Links already use a visible :focus-visible outline. The bridge buttons and the letter glyphs do too. The mobile "Explore" summary does too. This pass adds a skip link ("Skip to content") at the start of both marketing pages, and the same skip link on the Terms, Privacy, and Accessibility pages. It also adds a :focus-visible outline for button elements on both marketing pages. Links already had one. The bridge controls already had a more specific outline, and that outline still applies.

A control that is not only a picture. The bridge has Before / After buttons. Those are real buttons, with aria-pressed. Keyboard focus on the gate lights the same state a hover lights. That behavior does not depend on reduced motion.

Mobile menu hit area. The mobile Explore summary and the links inside it are styled with min-height: 44px. Other controls on the pages were not measured against a target-size rule. This sentence would be false if it said every control was 44 pixels.

Legal pages. Terms, Privacy, and this statement are text, with the same focus outline and a skip link. They do not run the canvases.

Known limitations

Stated so you can decide whether these pages work for you. This list is what was found in the files. It is not a finished WCAG review.

• No independent audit, and no certification. Conformance to WCAG 2.1 Level AA is a goal. It has not been tested end to end, and it has not been certified. Do not read this page as a conformance claim.
• Colour and contrast have not been measured. The pages use light text on a near-black background, with muted secondary text. No contrast ratio was calculated for this draft. Contrast work is ongoing. If a combination is hard to read, that report is welcome, and we will not answer it by inventing a ratio.
• The code picture is a moving (or, with reduced motion, a still) visual with a one-line label. It is not operable from the keyboard. There is no text list of the files it draws. The heading near it is "The code." That is not a full alternative.
• A lot of the desktop page is motion, and some of it follows the pointer. With reduced motion off, the starfield listens to pointer movement. The bridge diagram also lights when a pointer hovers the gate. Those are separate: reduced motion stops the sky loop and the pointer-nudge on that sky; it does not remove the bridge buttons.
• Reduced motion is checked once at load. The scripts do not subscribe to a later change of the operating-system setting. If you turn reduced motion on or off without reloading, the canvases can stay in the old mode until you reload. That is a gap.
• There is no on-page pause button for the canvases. The pause is the operating-system reduced-motion setting, and it applies on the next load.
• Flash and photosensitivity were not tested. The desktop page is motion-heavy when reduced motion is off: canvases, a pointer-following sky, and CSS pulses. Reduced motion, as described above, is the path that stops the loops we know about, and it applies on the next load. We do not claim the moving canvases meet the flash thresholds in WCAG 2.3.1. That was not measured, so this statement does not say they pass and does not invent a failure number either. If you have photosensitive epilepsy or a similar sensitivity, do not treat the animated view as safe for you. Use the operating-system reduced-motion setting and reload. That is not a medical judgment. It is a refusal to claim a threshold we did not measure. If something still flashes or keeps moving after that reload, treat it as a defect and tell us.
• Assistive technology was not run against these pages for this draft. We do not claim a VoiceOver, NVDA, TalkBack, or zoom pass. If a control is skipped, mislabeled, or only makes sense visually, that is a defect.
• The Connector UI is not in this statement. Nothing here describes a phone app or a desktop connector window, because those screens were not part of the files we read. "As applicable when shipped" means the same goal will be the starting point, not that the unreviewed UI already meets it.
• Some secondary text is quieter than the body text (--muted, --faint on the desktop page; similar roles on the mobile page). Whether each pair meets a contrast ratio is exactly the measurement this draft did not do.
• Time limits, reflow at 400% zoom, and a full keyboard pass were not evaluated as a checklist. We will not fill those boxes in from memory.

We do not consider this list finished. It is what is known from the files now.

No overlay

These pages do not load an accessibility overlay or a third-party widget that promises to repair the page. We will not add one as a substitute for fixing the page, and we will not claim that a widget produces WCAG conformance. Please do not send a report whose only request is that we install one. Say what failed.

Tell us what is broken

If a part of the Deific marketing site does not work with the assistive technology you use, tell us. We will treat that as a defect report, not as a feature request, and not as a warranty claim that the statement already promised a perfect page.

Scope Labs LLC 10412 China Spring Rd Ste F PMB 1120 Waco, TX 76708-5685 United States

Email: TODO. No Deific inbox was verified for this draft. Do not send Deific reports to support@scopescanner.app. That address belongs to Scope Scanner.

You do not have to disclose a diagnosis. If you choose to say that you use a screen reader, a magnifier, or reduced motion, or to describe a disability, we use that only to understand the barrier. We do not use it for advertising. We do not sell it. The Privacy Policy says the same thing in Section 14.

Please name the page (desktop mock or mobile mock), what you were trying to do, and what happened. We aim to acknowledge a report within 5 business days. That is an aim for a reply, not a promise that the barrier will be fixed in 5 days, and not a promise of a particular repair date.

Feedback about this statement

This statement should be updated when the pages change. If it overstates what the pages do — including the reduced-motion behavior above — that overstatement is itself a defect. Report it to the same address.

The Terms point here and say this statement is not a warranty. The Terms are at TERMS_OF_SERVICE.md (on the site, terms.html). The Privacy Policy is at PRIVACY_POLICY.md (on the site, privacy.html).