Wcag,[1] provides guidelines for different levels of accessibility for visitors to website content.

Accessibility means that the content published on a website should be accessible to all visitors and users — including those with disabilities. No one should therefore be prevented from taking part in digital service.

WCAG covers websites as well as mobile applications, and has guidelines on how user-friendliness can be optimized for all types of users. External services used by websites are also included in WCAG, such as chat, FAQ, or Forms.

As of January 1, 2019, public authorities and other public actors must reach level AA of the three-degree scale included in WCAG 2.1, known as the Digital Public Service Web Accessibility Directive.

The Digital Administration Authority, where DIGG is tasked with ensuring that the Digital Public Service Accessibility Act, will have an impact, will carry out supervision through monitoring and receive any complaints received.

That's the way it was. Now over to how we at Hello Ebbot relate to this. 


Public operators need to meet wcag 2.1 AA

The Digital Public Service Act needs to be complied with by public services, state and municipal authorities, where private bodies such as schools and health care can in some cases be included.

Time when requirements are met

The requirements must be applied depending on whether the website is new or old, or whether it relates to a mobile application.

Important dates regarding when the requirements need to be met:

New websites: 23 September 2019
Existing websites: 23 September 2020
Mobile applications: June 23, 2021

WCAG in practice

Aiming for a WCAG-adapted website does not necessarily mean that you need to build in functions for voice control, reading or magnification.

By using the right services early on, and by building the website with the right technical solutions for, for example, interfaces, browsers, phones and accessibility takes care of accessibility to visitors.

How Hello Ebbot works with WCAG

Hello Ebbot develop tools and services in conversation that are used on websites in the private, public and municipal sectors. Therefore, it also places demands on us where we meet WCAG with technical solutions, and we are often audited when we are going to launch our service to our customers, mainly in the public and municipal sector. At Hello Ebbot, we strive to meet the requirements of WCAG 2.1 AA. 

Some selected examples of how Hello Ebbot meets WCAG 2.1 AA: 

  • Keyboard navigation. Allows the user to access all services using the keyboard.
  • Web readout. Allows the browser to read to the user when the widget box pops.
  • Alt attribute functions. Means that images in the widget have alt attributes.
  • Frame marking. Means that the marking and correct linking of the Ebbot widget frame is presented correctly.
  • Text magnification. Text can be enlarged.
  • Selection of elements. Selects the elements that are in focus.
  • User-friendly contrast. Provides clear contrast between text and background.

Availability - Hello Ebbot

Screen reader users need additional information to use Ebbot. They need to be informed when someone has typed in any chat bar. We'll solve that through aria-live. As a complement and additional increased availability, chat can also be accessed via the keyboard with the tab button.

Enhanced support and availability in Hello Ebbot

Read text
Status Messages: We support this via Aria Live regions

Each message written by an agent is spoken to screen readers using Aria live regions.

Enlarge text
Make sure text can be magnified without problems

The widget customizes its content when magnifying the content.

Text readout
Use text, not images, to display text

The widget complements the icons in the main menu with text

Mark clearly
Select clearly which field or element is in focus

Fields that are in focus are clearly displayed.

customizing height
Orientation: support is available.

The widget adjusts the height, which means that the orientation of the device does not matter.


Availability statement

Public operators' websites are obliged to publish an accessibility statement which shall include, inter alia, an explanation of what is not available on the website and a link to comment on deficiencies.

On this page we will review what you need to fill in regarding the technical information for Hello Ebbot's services. Hello Ebbot does not take responsibility for content created by the customer himself through integrations. 

Hello Ebbot chatwidget

The widget is the box that appears in the lower-right corner. Below are the shortcomings that Hello Ebbot is working on improving per disability.

Problems when used without vision

The widget supports keyboard navigation and relies on external software to read content. To include the widget on one page without affecting the rest of the page (or the page affecting the widget), iframes are used, which degrades keyboard navigation in some browsers. This is nothing that Hello Ebbot can affect, but we are waiting for future improvements in the browsers.

Problems with visual impairment

Some parts have insufficient contrast. This is for aesthetic reasons and does not affect functionality.

Problems with reduced colour vision.

Some parts have insufficient contrast. This is for aesthetic reasons and does not affect functionality.

Problems when used without hearing.

This is not applicable as the few sounds that the widget plays are complemented by a visual effect.

Use with hearing loss.

This is not applicable as the few sounds that the widget plays are complemented by a visual effect.

Use without vocal ability.

This is not applicable as no voice control is present in the widget.

Use with reduced fine motor skills or strength.

This is not applicable as the widget supports both keyboard navigation and pointing device navigation.

Use with reduced mobility.

This is not applicable as the widget supports both keyboard navigation and pointing device navigation.

Use with sensitivity to flicker.

This is not applicable as the widget does not display flashing elements. The customer is responsible for the content.

Problems with use with cognitive impairment.

Uncorrectly completed forms are indicated only by red color.


Curious to know more about how Ebbot could work for you?

Get a live demo on the web where we go through the tool and explore what processes Ebbot could automate in your business.
3 steps to gdpr compliance
Matilda Elfman

3 Steps To Make Sure Your Chatbot is GDPR Compliant

In what way do chatbots fall under GDPR? What kind of data is protected? And what measures need to be taken to make sure your chatbot is GDPR compliant? Read on to get these questions answered and join us for a deep dive into the exciting world of data privacy.

Read more »
Customer Experience
Matilda Elfman

Why proactive support should be your main focus 2022

The market has changed. Consumer expectations have never been this high. At the same time competition is constantly increasing. Conclusion: Customer experience has never been more important. In fact, today 89% of businesses compete primarily on the basis of customer experience. One major trend that contributes to a good customer experience is proactive support. But what is proactive support and how can you apply it?

Read more »

Autocorrect spelling mistakes in Swedish language

Understanding that typos can be one of the reasons why Ebbot cannot give the right response, our NLP team at Hello Ebbot decided to develop a new feature to autocorrect spelling mistakes, specifically for Swedish language! Our spellcheck corrector not only considers context to provide better correction, but also has fixed performance.

Read more »