WCAG
WCAG 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 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:
Frame marking
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
-
Status Messages: We support this via Aria Live regionsEach message written by an agent is spoken to screen readers using Aria live regions.
-
Make sure text can be magnified without problemsThe widget customizes its content when magnifying the content.
-
Use text, not images, to display textThe widget complements the icons in the main menu with text
-
Select clearly which field or element is in focusFields that are in focus are clearly displayed.
-
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. To the right are the shortcomings that Hello Ebbot is working on improving per disability.
-
Problems when used without visionThe 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 impairmentSome parts have insufficient contrast. This is for aesthetic reasons and does not affect functionality.
-
Problems with reduced colour visionSome parts have insufficient contrast. This is for aesthetic reasons and does not affect functionality.
-
Problems when used without hearingThis is not applicable as the few sounds that the widget plays are complemented by a visual effect.
-
Use with hearing lossThis 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 mobilityThis 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.Incorrectly completed forms are indicated only by red color.