Legal
Accessibility.
We sell software to organizations that have accessibility obligations. It would be a poor advertisement if our own site failed them.
The standard we build to
This site targets WCAG 2.1 Level AA. Federal information and communication technology procurement is governed by Section 508 of the Rehabilitation Act, which incorporates WCAG 2.0 AA by reference; we build to the later version because there is no good reason to aim at the older one.
What that meant in practice
- Semantic HTML, with headings in order and landmarks on every page.
- A skip link to the main content, and a visible focus indicator on every interactive element.
- Text contrast at or above 4.5:1 for body copy and 3:1 for large text and interface components, checked against the palette rather than assumed.
- Full keyboard operation. The navigation, the mobile menu, and the contact form all work without a pointer, and the mobile menu closes on Escape.
- Form fields with real labels, required fields marked in text rather than by color alone, and errors announced to assistive technology.
- Motion reduced to nothing when the operating system reports a preference for reduced motion.
- Text that reflows to 320px without horizontal scrolling, and wide tables that scroll inside their own container rather than the page.
- No content conveyed by color alone, and no auto-playing media.
Known limitations
The capability statement is distributed as a PDF. We tag it for reading order and structure, but PDF remains a worse format for assistive technology than a web page. If you need the same content in HTML, plain text, or another format, ask and we will send it the same day.
We test with keyboard navigation, automated checks, and the screen readers available to us. We do not currently run a formal third-party audit, and we would rather say so than imply a certification we do not have.
Report a barrier
If something on this site does not work for you, tell us and we will fix it. Describe the page, what you were trying to do, and the assistive technology and browser you were using if you know them.
We aim to respond within two business days and to fix confirmed barriers within ten. If a fix will take longer than that, we will tell you why and give you the content another way in the meantime.