Find the answer you are looking for

Accessibility Features in Virtual Assistant

To promote easy access to digital content, the Web Content Accessibility Guidelines (WCAG) establish a series of guidelines to improve the experience for all users.

Virtual Assistant is progressively integrating the recommended model to improve accessibility for its users. The included elements are detailed below:

🌐 Language: The bot window explicitly declares the language/region, so that screen readers and accessibility tools process the text in the correct language from the start of the interaction.

⌨ Navigation and focus:

     â€˘ Logical tab order: A correct focus order (tabindex) has been implemented for all interactive elements in the window: header, buttons (minimize, close), quick replies, form inputs, text field, and submit button.

     â€˘  Accessible form fields and “show password” button: The ‘eye’ icon to show/hide the password is now reachable with Tab, activatable with Enter/Space, and the screen reader announces the status (“Show password” / “Hide password”).

     â€˘ “Accessibility” option in the Web channel CTA: enables a “Skip to chat” link (configurable text) to allow users with screen readers (or keyboard navigation) to jump directly to the accessible CTA to open the bot. It is configured under Settings > Channels > Web > Basic > Accessibility.

💬 Message feedback:

     â€˘ Sender identifier in messages: When navigating between messages using the Tab key, the screen reader announces the sender, indicating whether it is “your message” or “a message from the bot.”

     â€˘ Feedback when sending a message: After sending a message, the accessibility assistant announces that “a response is expected,” eliminating any uncertainty about whether the message was sent.

     â€˘ Feedback when receiving a message: When a response from the bot arrives, the screen reader indicates there is a “new message,” alerting the user.

🔍 Semantics and element descriptions: The bot uses correct semantic HTML so that the screen reader can automatically identify and describe buttons, lists, and links, telling the user how to interact with each one.

🖼 Images:

     â€˘ In Settings > Channels, for the icon, logo, and avatar elements. The text is rendered as an alt attribute in the HTML so that screen readers can read it.

     â€˘ Handling of decorative images: images without configured alternative text automatically receive alt="", indicating to the screen reader that they should be ignored.

     â€˘ Alt text for images: The optional “Alt text” field (max. 100 characters) has been added to the Image and Carousel complements. The text is rendered as an alt attribute in the HTML so that content published on the web channel can be correctly interpreted by assistive technologies, such as screen readers. 

🎬 Video: Two optional fields have been added to the Video complement.

     â€˘ Video description: This field is optional. It allows you to add a brief description of the video’s content, with a maximum limit of 100 characters. We recommend including “what it’s about” and “what the user will get” from watching it. 

     â€˘ Extended description URL: Allows you to add an optional link with a longer description. It should link to stable, accessible content in text format, not just another video. This could be, for example, a webpage or an online document.

This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.

If you decline, your information won’t be tracked when you visit this website. A single cookie will be used in your browser to remember your preference not to be tracked.