Accessibility

Last Updated: June 30, 2025

‍

At Ebbot, we follow the Web Content Accessibility Guidelines (WCAG) to ensure our chat widget and other services are inclusive, practical, and user-friendly. This page outlines how we ensure accessibility, identify areas for improvement, and plans for betterment.

‍

About WCAG
‍

WCAG (Web Content Accessibility Guidelines) is the global standard for making digital content usable for people with disabilities. It covers:

‍

Optimizations for different devices and browsers.
External tools like chat widgets, forms, and FAQs.
Websites and mobile applications.

‍

How Ebbot meets accessibility standards

‍

We design our chat widget and services to align with WCAG 2.1 AA standards and regularly audit our tools to stay on track. Here’s how we make our solutions accessible:

‍

Key accessibility features:

Keyboard navigation: Users can navigate all services via the keyboard.
Screen reader support: Content is compatible with screen readers using ARIA live regions.
Alt attributes: Images within the widget are accompanied by descriptive alt text.
Text scalability: The widget content adapts to text magnification.
Clear focus indicators: Focused elements are visually distinct.
Device adaptability: The widget adjusts seamlessly to different device orientations.

‍

Accessibility statement

Public sector websites are required to publish an accessibility statement that explains any limitations and includes a way for users to give feedback.

Here, we outline the technical details for Ebbot’s service, excluding any content added through integrations. You can find the full accessibility statement in our Trust Center.

‍

Known areas of improvement

‍

While we’ve made significant progress, we recognize there’s still work to do. Here are the areas we’re actively working to improve:

‍

Keyboard navigation

The widget supports keyboard navigation and screen readers. However, the use of iframes may cause navigation challenges in some browsers. This is a browser limitation and beyond our direct control.

‍

Reporting accessibility issues

‍

Your feedback is essential to our improvement efforts. If you encounter accessibility barriers or believe we’ve fallen short of compliance, please let us know:

‍

We aim to respond within one business day and address issues promptly.

‍

Escalating complaints

‍

If you feel we haven’t addressed your concerns, you can escalate the issue to the Swedish Agency for Digital Government (Digg). Digg oversees compliance with the Digital Public Service Accessibility Act and can review our response.

‍

Submit a complaint to Digg.

‍

Steps we’re taking to improve

Accessibility audit:

Our most recent internal accessibility evaluation was conducted in June 2025.