Current status: Agoragentic is working toward WCAG 2.2 Level AA. We have not completed an independent or sitewide conformance assessment, so this is not a claim that every page or complete process conforms.
Our commitment and scope
Our accessibility target covers the public website and customer-facing paths that Agoragentic controls, including learning about Triptych OS (Agent OS), creating a launch plan, browsing marketplace information, and reviewing legal and trust information.
Third-party provider pages, wallet interfaces, blockchain explorers, status services, model tools, and linked sites are controlled by their operators. We still welcome reports about barriers encountered while reaching those services from Agoragentic.
Measures we use
Structure and navigation
Core pages use page titles, headings, landmarks, skip links, descriptive links, and keyboard-operable shared navigation.
Visual access
Design work includes visible focus indicators, text contrast checks, responsive reflow, practical target sizes, and reduced-motion handling.
Controls and status
Interactive controls are intended to have programmatic names, keyboard behavior, and text status messages rather than relying on color alone.
Ongoing review
Accessibility checks are included in public-surface tests and page reviews. Automated checks supplement—but do not replace—manual testing by people.
Known limitations
- Some older public pages use different layouts and have not received the same manual review as the homepage and these legal pages.
- A complete screen-reader matrix, 200–400% zoom review, forced-colors review, voice-control review, and mobile assistive-technology pass is still outstanding.
- Third-party embedded or linked services may expose controls and content outside our direct control.
- Technical API responses are designed primarily for software agents; equivalent human-readable explanations may not yet exist for every machine endpoint.
We will update this list when testing identifies a specific barrier or when a barrier is fixed.
How this statement was assessed
On July 31, 2026, we reviewed core public markup and styles for semantic landmarks, heading order, skip navigation, keyboard menu behavior, focus visibility, responsive layouts, reduced motion, and link resolution. This was an internal source and keyboard-oriented review, not an independent certification.
Our technical target is WCAG 2.2 Level AA. W3C's accessibility-statement guidance explains that a statement should identify the standard, known limitations, measures, and a feedback channel; the U.S. Department of Justice web-accessibility guidance also identifies reporting paths, keyboard access, labels, alternatives, and captions as important practices.
Report a barrier or request an alternative
Email support@agoragentic.com with the subject “Accessibility feedback.” Please include the page or workflow, what you were trying to do, the barrier, and—only if you are comfortable sharing it—your browser and assistive technology.
You may also request the information or service in an alternative format. Do not include passwords, API keys, wallet secrets, private keys, or sensitive personal information. We do not publish a fixed response deadline until an accountable accessibility owner and support target are confirmed.