Accessibility

• Keyboard navigation, every interactive element in the chat UI is reachable via Tab, activated via Enter/Space, and dismissable via Escape where applicable.
• Semantic HTML, headings (h1 to h4), lists, tables, form labels, buttons, and ARIA roles are used correctly throughout.
• Focus indicators, the primary focus ring uses the gold accent color with sufficient contrast against the background.
• Color contrast, body text against the dark background meets AA (≥4.5:1). Large text and UI components meet AA Large.
• Responsive layout, the chat and Trust Center render cleanly down to 375px viewport widths without horizontal scrolling.
• Form accessibility, every input has a programmatically associated label, required fields are marked, inline errors are announced to assistive tech via aria-invalid and error-message regions.
• Voice input, the chat composer supports Web Speech API dictation with a visible "Listening…" indicator.

• Streaming message announcement, streamed assistant responses update frequently; we do not yet announce every chunk to screen readers (the alternative would be overwhelming). A "response complete" announcement is planned.
• Code block labels, the language label on code blocks is visible but not yet announced as a structured landmark to screen readers.
• Tool output structure, some tool results (such as web-search results) render as custom cards; screen reader users get usable text, but the visual card structure is not yet a perfect semantic mirror.
• Automated WCAG audit, we have not yet commissioned an external VPAT (Voluntary Product Accessibility Template). Planned for the SOC 2 Type 1 milestone.

• VoiceOver on macOS + iOS (primary)
• NVDA on Windows (secondary, via remote testing)
• Keyboard-only navigation (no mouse/trackpad)
• High-contrast mode (Windows)
• Browser zoom up to 200%

If JCIL.AI is not working for you because of an accessibility barrier, please let us know, these reports are a priority and we treat them like security issues.

Submit through the compliance contact form with topic general compliance question(there isn't a dedicated accessibility topic yet; mention "accessibility" in the message and it routes to the same founder inbox). We acknowledge within two business days and work with you on a resolution or workaround.