Trust

Accessibility

Accessibility is a requirement of our work, not a later pass. Here is the standard we hold ourselves to, and how to tell us where we fall short.

We build Panoptic products to be usable by as many people as possible, including people who rely on assistive technology. We treat accessibility as a design requirement and an acceptance criterion — not an optional enhancement added at the end.

The standard we hold

We target WCAG 2.2 Level AA as a floor across our websites and products, reaching for AAA where doing so does not harm clarity. Accessibility checks are built into our components, and an accessibility regression is treated as a defect of the same severity as broken functionality.

What that means in practice

  • Sufficient color contrast for text and meaningful interface elements.
  • Full keyboard operability, with a visible focus indicator throughout.
  • Adequate target sizes for interactive controls.
  • Respect for reduced-motion preferences.
  • Semantic HTML, with correct roles, names, and states for assistive technology.
  • Clear, accessible forms with understandable error messages.
  • A logical heading structure and descriptive link text on every page.

Honest about where we are

Holding a standard is not the same as claiming perfection. Accessibility is ongoing work, and no complex product is ever entirely free of barriers. We test as we build and fix what we find — and when we fall short, we would rather know than assume we have not. If something on a Panoptic site or product is difficult or impossible for you to use, that is a problem we want to solve.

Tell us

If you encounter an accessibility barrier, please email support@panopticdevelopment.com and describe the problem, the page or product, and the assistive technology you were using if relevant. We take these reports seriously and will work to resolve them.