Accessibility Statement
Last updated: March 2026
Our commitment
We believe everyone should be able to create great AI agents. We're actively working to make Opal Agent Creator accessible and usable for people of all abilities, and we're transparent about where we are and where we need to improve.
What we've done
lang attribute set on the HTML element for screen readers
Skip-to-content link for keyboard users
Visible focus indicators on interactive elements (focus-visible)
Reduced motion support via prefers-reduced-motion media query
Form inputs linked to labels with proper htmlFor/id attributes
Modal dialogs use ARIA dialog semantics (role, aria-modal, aria-labelledby) with focus trapping and Escape to close
Template cards are keyboard-accessible (Enter/Space to activate, tab-focusable)
Form validation errors are linked to inputs via aria-describedby and announced with role="alert"
Navigation dropdown menus use ARIA menu roles (menu, menuitem, aria-expanded, aria-haspopup)
Cookie disclosure banner uses role="region" with descriptive aria-label
Transparency: known gaps
- Some text uses
text-slate-400which may not meet WCAG AA contrast ratios against our light background - Third-party embeds (Wistia videos, Google Slides) may have accessibility limitations we can't control
- No comprehensive screen reader testing has been done yet (VoiceOver, NVDA, JAWS)
- Async operations (agent generation, eval runs) don't use ARIA live regions to announce status changes
- Mobile navigation menu doesn't trap focus when open
Standards
We're working toward conformance with WCAG 2.1 Level AA. This is an ongoing effort — we address accessibility issues as part of our regular development process.
Feedback
If you encounter any accessibility barriers or have suggestions for improvement, please email support@optimizely.com. We take accessibility feedback seriously and will respond within 5 business days.