Useful is for
everybody.

Built into the experience.

• Keyboard-operable forms and chat controls, skip links, visible focus, and Escape to close the floating chat.
• Explicit labels, associated error messages and live status updates when a conversation or action changes.
• Readable color combinations. Theme publication checks body text and button-label contrast.
• Responsive layouts, generous controls, and respect for reduced-motion preferences.
• Plain-text answers and clear speaker names. Choosing a neutral or custom identity also updates the chat’s accessible name.

Customization has boundaries.

You can change the assistant’s identity and appearance while retaining its labels, keyboard controls and contrast validation. Arbitrary scripts and unrestricted CSS cannot be inserted through appearance settings.

Your host page can still affect the complete experience. Check the embedded chat alongside your navigation, forms, sticky content, and any other dialogs.

A standard we work to.

Our target is WCAG 2.2 AA. Our checks cover keyboard navigation, color contrast, form labels, and narrow-screen reflow. We review the website, control room and embedded chat together.

Customer themes retain the same accessible controls. We encourage teams to test text resize, zoom and assistive technology in the context of their own website.

If something gets in the way.

When reporting an accessibility issue through Huck’s accessibility support form, include the page or chat, what you were trying to do, your browser and assistive technology if applicable, and the result you expected. Do not include private conversation content unless needed and authorized.