Our target
Synaptic uses the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as its product target. WCAG organizes accessibility around content that is perceivable, operable, understandable, and robust. This statement describes the current product direction; it is not a claim of independent certification.
Accessibility is part of design, implementation, and review for the public site and authenticated workspace. We aim to remove barriers without requiring users to disclose a disability.
Support present today
- A keyboard-visible skip link leads directly to the main content region.
- Semantic landmarks, headings, navigation labels, table captions, form labels, and descriptive control names are used across the application.
- Keyboard focus has a visible global treatment, with additional high-contrast focus states on dense workspace controls.
- Loading, search, credential, copy, and save feedback uses status or live-region semantics where asynchronous state must be announced.
- Layout and type scale adapt at multiple responsive breakpoints rather than requiring a fixed desktop canvas.
- A reduced-motion media query disables smooth scrolling and reduces animations and transitions when the operating system requests it.
Known limitations
Code graphs are visually dense, spatial interfaces. Graph nodes have names and keyboard-focusable links, but some exploratory relationships may not yet have a complete nonvisual equivalent. Very large data tables, graph canvases, and command-search result sets can also require more navigation than simpler pages.
No VPAT, Accessibility Conformance Report, or independent WCAG certification is published for the current release. We will not describe the service as fully conformant until representative flows have been tested with assistive technology and documented against the applicable success criteria.
Feedback and assistance
If a feature blocks access, contact enterprise@synaptic.dev. Include the page or workflow, what you were trying to accomplish, the browser and assistive technology involved, and a description of the barrier. Do not include passwords, API keys, repository credentials, customer source, or other secrets.
We will use the report to reproduce the barrier, identify an equivalent path where available, and prioritize remediation according to impact.
Compatibility and testing
The interface is built on standards-based HTML, CSS, and browser controls and is intended for current browsers with keyboard and screen-reader support. Exact behavior can vary by operating system, browser, screen reader, zoom setting, and enterprise extension.
The testing matrix is still being expanded. Automated checks can find markup problems, but they do not replace keyboard, zoom, contrast, screen-reader, and task-based review by people.
Standards and updates
Our reference is the current W3C WCAG 2 overview, with Level AA as the working target. Product changes, newly identified barriers, and changes to applicable standards can require this statement to be updated.
The date at the top identifies the current version. Contractual accessibility requirements or assessment requests should be raised through the applicable enterprise agreement or sent to enterprise@synaptic.dev.