Accessibility

Built to WCAG 2.2 Level AA.

This statement describes what has been implemented and verified, and what has not. We would rather name an unmeasured area than claim conformance we have not tested.

The standard we target

ShipLock targets the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is the benchmark referenced by the Americans with Disabilities Act in US enforcement practice, by Section 508 for federal procurement, and by the European Accessibility Act. We treat it as the design standard for the product, not as a checklist applied afterwards.

What is implemented

  • Semantic structure throughout: landmarks, a single document heading order, and labelled regions on every panel rather than styled div containers.
  • Full keyboard operation. Every interactive control is reachable and operable without a pointer, and focus is visible against both themes.
  • Text contrast meeting or exceeding 4.5:1, and non-text contrast of 3:1 for controls and focus indicators.
  • Status conveyed by more than colour. Severity carries a text label wherever it carries a colour, so the distinction survives greyscale and the common forms of colour blindness.
  • Reduced-motion support: every animation is behind prefers-reduced-motion, and none of them is required to understand the content.
  • Content that reflows to 320px without horizontal scrolling, and remains usable at 200% zoom.
  • Form fields with programmatically associated labels, and errors described in text rather than by colour or position.

Known limitations

We have not yet completed an audit with assistive technology across the full range of screen readers, so conformance is asserted from implementation and automated checking rather than from verified user testing. Some dense finding tables are usable but not yet optimal to navigate by screen reader, and code and SQL blocks are presented as preformatted text without per-token semantics.

Neither is a reason to wait before telling us something is unusable. If a barrier stops you completing a task, that takes priority over the roadmap.

Reporting a barrier

Write to support@shiplock.dev with the page and what you were trying to do. We aim to acknowledge within two business days and to give you a workaround in the same reply where one exists. If you need information held in your dashboard in a different format, ask and we will provide it.

Last reviewed 30 July 2026. This statement is reviewed whenever the interface changes materially.