Accessibility

WCAG 2.2 Level AA

Codename Sonar, operated by Artisan Technical Computer Services, LLC, is designed to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. This page is the accessibility statement and the guidelines this service follows. It is not a substitute for a certified audit. Source: W3C WCAG 2.2 · How to meet WCAG

Four principles

  • Perceivable

    Information and user interface components must be presentable to users in ways they can perceive.

  • Operable

    User interface components and navigation must be operable. Do not require interaction that a user cannot perform.

  • Understandable

    Information and the operation of the user interface must be understandable.

  • Robust

    Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.

How this service applies Level AA

  1. 1.1.1 Non-text content

    Images, icons, and the radar canvas have text alternatives. Decorative marks are hidden from assistive technology.

  2. 1.3.1 Info and relationships

    Headings, landmarks, labels, and lists describe structure. Status is not conveyed by layout alone.

  3. 1.4.1 Use of color

    Status is also given in text (tooltips and accessible names). Color is never the only signal. New sweep data also blinks a neon pip; motion pauses when the operator prefers reduced motion.

  4. 1.4.3 Contrast (minimum)

    Body, labels, and controls target 4.5:1 against their background. Large text and icons target 3:1.

  5. 1.4.10 Reflow

    Layouts wrap to a phone-width viewport without requiring two-dimensional scrolling for main content.

  6. 1.4.13 Content on hover or focus

    Tooltips can be dismissed with Escape, hovered, and remain until dismissed or focus moves away.

  7. 2.1.1 Keyboard

    Primary flows work with a keyboard. A skip link jumps to main content.

  8. 2.4.4 Link purpose (in context)

    Links name their destination. Report tiles include the page name and whether it has data.

  9. 2.4.7 Focus visible

    Keyboard focus shows a 2px accent outline with offset on interactive controls.

  10. 2.5.8 Target size (minimum)

    Hit targets are at least 24×24 CSS pixels. Primary actions use a larger 44px-class control where practical.

  11. 3.1.1 Language of page

    The document language is set to English.

  12. 3.2.1 On focus

    Focus does not trigger unexpected context changes.

  13. 3.3.2 Labels or instructions

    Forms have visible or programmatically associated labels. Errors are described in text.

  14. 4.1.2 Name, role, value

    Controls expose accessible names and states (expanded, current page, modal).

What a sweep can infer

A remote scan cannot certify another site. Where HTTP is in the lock, the report maps a few observable signals to WCAG 2.2 — page title (2.4.2) and content language (3.1.1). Missing title or language is a gap or a watch item on the compliance scorecard. That mapping is a vantage-point heuristic, not an accessibility audit of the target.

Known limits

  • The radar display is a labeled canvas summary of scan progress, not a fully described real-time chart.
  • USB firmware flashing requires a Chromium browser with Web Serial. That hardware path is not available in every user agent.
  • PayPal checkout surfaces are third-party. Their accessibility is governed by PayPal.
  • This is an accessibility target for WCAG 2.2 Level AA, not a certified third-party audit of every view in every browser.

Accessibility comments may be sent through the contact published on this service, or noted in your operator account. Terms of Service · Back to sensor