Accessibility statement of digital service Leadoo

Accessibility of the digital service

Chatbot service partly meets the requirements of the Web Content Accessibility Recommendations (WCAG 2.1) levels A and AA.

Inaccessible content

Inaccessible content (according to WCAG 2.1 levels A and AA criteria). The following content and/or functionality is not yet compliant

Status messages

Not all chatbot messages or timestamps are read by the screen reader. Some messages are read more than once. (WCAG 4.1.3, robust)

Visible focus and focus order

Some parts of the chatbot lack visible focus, focus shifts incorrectly or focus does not meet contrast requirements. Focus order is partly illogical. (WCAG 1.3.2, 1.4.11 perceivable, 2.4.7 operable)

Contrasts

Some of the colour combinations used in the chatbot do not meet the contrast requirements. (WCAG 1.4.3, perceivable)

Name, role, value

The bot has elements, such as buttons, that lack an accessible name. In addition, there are elements, such as buttons, whose state or changed state is not conveyed to the assistive technology. (WCAG 4.1.2 robust)

Alt texts for icons

Some icons lack proper alt texts. (WCAG 1.1.1 perceivable)

Inconsistent navigation

The key used to send responses varies depending on the field used; multi-line responses are sent using a key other than the enter key, and screen reader users are not instructed to use a different approach. (WCAG 3.2.3 understandable)

Required fields

Some of the required fields are not marked as required. (WCAG 3.3.2 understandable)

Keyboard navigation

The bot contains elements that cannot be used with the keyboard. (WCAG 2.1.1 operable)

Accessibility of the digital service

Inpagebot service partly meets the requirements of the Web Content Accessibility Recommendations (WCAG 2.1) levels A and AA.

Inaccessible content

Inaccessible content (according to WCAG 2.1 levels A and AA criteria)

The following content and/or functionality is not yet compliant.

Status messages

Not all chatbot messages or timestamps are read by the screen reader. Some messages are read more than once. The reading order is sometimes illogical: the label associated with the field is read first, followed by the bot's response to the previous question.(WCAG 1.3.2 perveivable, 4.1.3, robust)

Visible focus and focus order

Some parts of the chatbot lack visible focus, focus shifts incorrectly or focus does not meet contrast requirements. Focus order is partly illogical. (WCAG 1.3.2, 1.4.11 perceivable, 2.4.7 operable)

Contrasts

Some of the colour combinations used in the Inpagebot do not meet the contrast requirements. (WCAG 1.4.3, perceivable)

Name, role, value

The bot has elements, such as buttons, that lack an accessible name. In addition, there are elements, such as buttons, whose state or changed state is not conveyed to the assistive technology. (WCAG 4.1.2 robust)

Alt texts for icons

Some icons lack proper alt texts. (WCAG 1.1.1 perceivable)

Inconsistent navigation

The key used to send responses varies depending on the field used; multi-line responses are sent using a key other than the enter key. (WCAG 3.2.3 understandable)

Required fields

Some of the required fields are not marked as required. (WCAG 3.3.2 understandable)

Accessibility of the digital service

Visualbot service partly meets the requirements of the Web Content Accessibility Recommendations (WCAG 2.1) levels A and AA.

Inaccessible content

Inaccessible content (according to WCAG 2.1 levels A and AA criteria)

The following content and/or functionality is not yet compliant.

Alt texts for images

Some images lack proper alt texts. (WCAG 1.1.1 perceivable)

Contrasts

Some of the colour combinations used in the bot do not meet the contrast requirements. (WCAG 1.3.2, 1.4.11 perceivable, 2.4.7 operable)

Focus order

Focus order is partly illogical and things are read to the screen reader in an illogical order. (WCAG 1.3.2 perceivable, 2.4.3 operable)

Required fields

Some of the required fields are not marked as required. (WCAG 3.3.2 understandable)

Inconsistent navigation

The key used to send responses varies depending on the field used; multi-line responses are sent using a key other than the enter key, and screen reader users are not instructed to use a different approach. (WCAG 3.2.3 understandable)

Accessibility of the digital service

CTAbot service partly meets the requirements of the Web Content Accessibility Recommendations (WCAG 2.1) levels A and AA.

Inaccessible content

Inaccessible content (according to WCAG 2.1 levels A and AA criteria)

The following content and/or functionality is not yet compliant

Visible focus and contrasts

Some parts of the CTAbot lack visible focus or focus does not meet contrast requirements. (WCAG 1.3.2, 1.4.11 perceivable, 2.4.7 operable)

Name, role, value

The bot has elements, such as buttons, that lack an accessible name. In addition, there are elements, such as buttons, whose state or changed state is not conveyed to the assistive technology. (WCAG 4.1.2 robust)

Alt texts for icons

Some icons lack proper alt texts. (WCAG 1.1.1 perceivable)

Inconsistent navigation

The key used to send responses varies depending on the field used; multi-line responses are sent using a key other than the enter key. (WCAG 3.2.3 understandable)

Required fields

Some of the required fields are not marked as required. (WCAG 3.3.2 understandable)