Since 28 June 2025 the European Accessibility Act has applied across the EU. It obliges companies to make certain products and services accessible \u2014 and that has concrete consequences for customer service. Anyone dealing with customers by phone, chat, email or web forms has to design those channels so that people with visual, hearing or motor impairments can use them too.<\/p>\n\n\n\n
Each member state implements the directive in its own law: Germany through the Barrierefreiheitsst\u00e4rkungsgesetz, France and the other states through their own instruments. The substance is the same everywhere, the wording and the enforcement bodies differ.<\/p>\n\n\n\n
The scope covers online retail, banking and telecommunications services along with the support processes that accompany them. Where a company sells affected products or services to consumers, the customer service around them must provide information about accessibility and be compatible with assistive technology. A help desk should be able to say reliably whether and how an offering can be used without barriers.<\/p>\n\n\n\n
Micro-enterprises \u2014 fewer than ten employees and up to two million euros in annual turnover \u2014 are exempt for services. For everyone else, breaches can lead to warnings and fines. The commercial effect weighs heavier still: whoever builds barriers permanently shuts out a substantial share of potential customers.<\/p>\n\n\n\n
The relevant standards are the Web Content Accessibility Guidelines and the European standard EN 301 549, which references them. They apply to digital content, but the underlying principles carry over to every service channel: content must be perceivable, operable, understandable and robust.<\/p>\n\n\n\n
In practice that means a phone menu should not depend on hearing alone, a chat window has to work with a screen reader, and a form must be completable by keyboard. None of this is exotic \u2014 it is craft.<\/p>\n\n\n\n
A central principle is that important information should be conveyed through at least two senses, for instance visually and audibly. In practice a single channel rarely suffices. A company reachable only by phone excludes deaf people. One offering only a purely graphical chat makes life hard for people with impaired vision.<\/p>\n\n\n\n
Accessible service therefore arises where customers can choose freely between equivalent channels:<\/p>\n\n\n\n
This is where myContactCenter comes in. The platform brings voice, chat, email, fax and messaging together in one interface, so equivalent channels are not a project in themselves but a configuration. Speech recognition turns spoken requests into text, speech synthesis turns text into announcements \u2014 the same content, reachable through a second sense.<\/p>\n\n\n\n
The graphical process designer lets you build call flows that work without listening: written confirmation instead of an audible one, call-back instead of waiting on hold, a switch from voice to chat within the same case.<\/p>\n\n\n\n
Look at the channels you offer today and ask, for each one, who cannot use it. That question is quicker to answer than any audit and usually points straight to the gap. Everything else follows from there.<\/p>\n\n\n\n
This article gives a general overview and does not replace legal advice. Which obligations apply in a specific case depends on the products and services offered and on the national implementation.<\/p>\n","protected":false},"excerpt":{"rendered":"
The European Accessibility Act has applied since June 2025. What it means for customer service, and how an omnichannel platform helps meet it.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_il_seo_titel":"Accessible customer service in contact centres","_il_seo_beschreibung":"The European Accessibility Act has applied since June 2025 and covers your service channels. What it means for voice, chat and forms.","footnotes":""},"categories":[33],"tags":[],"class_list":["post-56965","post","type-post","status-publish","format-standard","hentry","category-law-and-regulation"],"_links":{"self":[{"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/posts\/56965","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/comments?post=56965"}],"version-history":[{"count":1,"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/posts\/56965\/revisions"}],"predecessor-version":[{"id":56989,"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/posts\/56965\/revisions\/56989"}],"wp:attachment":[{"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/media?parent=56965"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/categories?post=56965"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ilogixx.de\/en\/wp-json\/wp\/v2\/tags?post=56965"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}