URGENT: Webchat accessibility errors for EU clients
Hi Voiceflow team,
I’m reaching out on behalf of our company with an urgent request regarding accessibility compliance of the Voiceflow webchat widget.
We’ve built multiple chatbot solutions on Voiceflow for government and public sector clients in the Czech Republic (EU). These projects must comply with WCAG 2.2 and the European Accessibility Act, which becomes enforceable at the end of June 2025. Non-compliance may result in major penalties (hundreds of thousands USD).
After a detailed accessibility audit, we found critical issues:
1. Missing
2. Some titles like “Open chat agent” / "Close chat agent" are hardcoded in English with no localization option.
3. The chat input field has only a
4. SVGs and images lack
These issues break screen reader support and other assistive tech. We currently serve over 10 government projects, and without fixes, we will be forced to stop using the widget entirely, threatening our operations.
We noticed some recent progress (e.g.,
Happy to share screenshots more or reports if needed. We truly want to continue building on Voiceflow.
-------------
Best regards,
Pavel from HypeDigitaly
hypedigitaly.ai
I’m reaching out on behalf of our company with an urgent request regarding accessibility compliance of the Voiceflow webchat widget.
We’ve built multiple chatbot solutions on Voiceflow for government and public sector clients in the Czech Republic (EU). These projects must comply with WCAG 2.2 and the European Accessibility Act, which becomes enforceable at the end of June 2025. Non-compliance may result in major penalties (hundreds of thousands USD).
After a detailed accessibility audit, we found critical issues:
1. Missing
aria-labelaria-label / titletitle attributes on many buttons (microphone, close chat, scroll-to-bottom).2. Some titles like “Open chat agent” / "Close chat agent" are hardcoded in English with no localization option.
3. The chat input field has only a
placeholderplaceholder, no <label><label>4. SVGs and images lack
altalt or accessibility attributes.These issues break screen reader support and other assistive tech. We currently serve over 10 government projects, and without fixes, we will be forced to stop using the widget entirely, threatening our operations.
We noticed some recent progress (e.g.,
titletitle attributes appearing for open/close chat) — great start. But the widget remains non-compliant in its current form, and we urge you to prioritize accessibility fixes ASAP.Happy to share screenshots more or reports if needed. We truly want to continue building on Voiceflow.
-------------
Best regards,
Pavel from HypeDigitaly
hypedigitaly.ai
