glyphon.ai
Accessibility statement
Glyphon is built for federal and defense program offices where staff rely on assistive technology daily. This statement covers glyphon.ai only. Deployed Glyphon instances within a customer authorization boundary are governed by that engagement's own accessibility requirements.
Conformance status
We target WCAG 2.2 Level AA and the 2018 Revised Section 508 standard as our legal floor. Our status is self-assessed: automated checks run against every change in our build pipeline, and manual procedures (keyboard navigation, 200% zoom, 320px reflow, focus order, non-text contrast) are recorded in our engineering log. We do not claim third-party certification of this site's conformance.
How we test
- Automated axe-core scans on every pull request, blocking before merge. The gate covers WCAG 2.x A, AA, and WCAG 2.2 AA rule sets across all public pages: /, /government, and /accessibility.
- Manual 200% zoom test: verifying no text clips or overflows at browser text scale 200%.
- Manual 320px reflow test: single-column layout at 320px viewport width, no horizontal scrollbar on content (data tables and code blocks are exempt per WCAG 1.4.10).
- Focus order review: keyboard tab traversal confirmed to follow reading order with visible focus indicators on all interactive elements.
- Non-text contrast: interactive component boundaries verified at 3:1 against adjacent background per WCAG 1.4.11.
- Screen-reader pass: VoiceOver and NVDA walkthroughs are performed by the Human Lead on each content revision. Automation cannot substitute for a real assistive-technology pass.
- Reduced-motion: a global CSS guard disables non-essential animation when prefers-reduced-motion: reduce is set. Component-scoped guards reinforce this at the JavaScript layer.
Known limitations
axe-core covers roughly 57% of WCAG AA criteria automatically. Criteria that axe cannot fully verify (resize text, reflow, focus order, non-text contrast, screen-reader semantics) are checked via the manual procedures above and recorded in docs/accessibility/manual-review.md. Any criterion rated "Partially Supports" in our VPAT reflects a confirmed gap with a tracked remediation, not an untested assumption.
The CLI usage examples and audit-trail mockups on the homepage are scrollable code regions. Each is keyboard-focusable via tabindex="0" and carries an accessible label describing its content.
Feedback
If any part of this site is difficult to use with assistive technology, please tell us and we will address it: ai@accelerasolutions.com.
Last reviewed: 2026-06-13