Accessibility & WCAG
We believe in making digital experiences accessible for everyone.
Accessibility isn’t just about compliance—it’s about creating tools and services that everyone can use, regardless of their abilities. At Ebbot, we follow the Web Content Accessibility Guidelines (WCAG) to ensure our chat widget and other services are inclusive, practical, and user-friendly.
What WCAG means for accessibility
The Web Content Accessibility Guidelines (WCAG) set global standards for making web content accessible to all users, including people with disabilities. These guidelines cover:
Key deadlines for compliance
Under the Digital Public Service Accessibility Act, public sector organizations must comply with WCAG 2.1 AA.
The requirements must be applied depending on whether the website is new or old, or whether it relates to a mobile application.
Compliance deadlines:
How Ebbot meets accessibility standards
At Hello Ebbot, we create tools for websites in the private, public, and municipal sectors. This means we’re committed to meeting WCAG 2.1 AA standards and are regularly audited. Here are some ways we ensure compliance:
Content is compatible with screen readers using ARIA live regions.
Users can navigate all services via the keyboard.
Images within the widget are accompanied by descriptive alt text.
The widget content adapts to text magnification.
Focused elements are visually distinct.
The widget adjusts seamlessly to different device orientations.
Accessibility statement
Public operators' websites are obliged 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.
Known areas of improvement for the chat widget
The widget is the box that appears in the lower-right corner. While we’ve made significant strides, we know there’s more work to do. Here are the areas we’re actively improving:
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.
Some interface elements do not meet recommended contrast ratios, which can impact readability for users with visual impairments.
Errors in form inputs are currently highlighted using red color alone, which does not provide sufficient feedback for all users.
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.
Ready to experience accessible service automation?
Interested in how Ebbot can help you?