We build websites for cities, cultural venues and festivals. That raises a question we had not asked ourselves honestly for a long time: Is our own website actually accessible? So we tested it \u2013 with the same tools and criteria that public authorities and auditors use. The result was instructive. And it shows quite well why the topic is becoming important for so many clients right now.<\/p>\n
Almost one in ten people in Germany lives with a recognised severe disability, plus people with low vision, motor impairments or simply a small phone screen in bright sunlight. For them, an accessible website is the difference between \u201cI can use this\u201d and \u201cI give up\u201d.<\/p>\n
Then there is the legal side: public bodies \u2013 cities, municipalities, state authorities \u2013 have long been required to make their websites accessible and to publish an accessibility statement. Since 28 June 2025, the German Accessibility Strengthening Act (BFSG) also applies to many companies offering digital services to consumers. For services, micro-enterprises with fewer than ten employees and an annual turnover of no more than two million euros are among those exempt. The benchmark is the same in every case: the Web Content Accessibility Guidelines (WCAG) 2.1, level AA.<\/p>\n
Our site runs on WordPress, Elementor and a purchased theme \u2013 like a great many websites in culture and small business. At first glance, everything looked fine. Still, the audit brought quite a few things to light:<\/p>\n
None of this was intentional. These are typical errors built into ready-made themes and page builders \u2013 and you do not notice them as long as you use a mouse and a good screen yourself.<\/p>\n
The good news: almost everything could be fixed without rebuilding the website. A visible focus outline in our brand colour, a \u201cSkip to content\u201d link, lighter text, a clean heading structure, names for all icon links, alternative text for the images and a menu that also opens by keyboard. For visitors using a mouse, the site looks almost exactly as before. For everyone else, it now works.<\/p>\n
Finally, we published an Accessibility Statement<\/a> . It sets out what we have implemented \u2013 and, honestly, what is not yet perfect, such as embedded third-party videos without captions.<\/p>\n If you get stuck on any of these points, a closer look is worthwhile.<\/p>\n Accessibility is now a fixed part of every website project we do. We also audit existing websites, fix issues without rebuilding everything, write the accessibility statement and show your team how to keep the site accessible as new content is added. Find out more on our page Websites & Communication<\/a> \u2013 or write to us directly.<\/p>\n Note: This article provides an overview and is not legal advice. Whether and which obligations apply to you depends on the individual case.<\/em><\/p>","protected":false},"excerpt":{"rendered":" Wir haben unsere eigene Website auf Barrierefreiheit gepr\u00fcft \u2013 mit \u00fcberraschenden Ergebnissen. Was wir gefunden, wie wir es behoben haben und f\u00fcnf Checks, die ihr selbst machen k\u00f6nnt.<\/p>","protected":false},"author":1,"featured_media":2192,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"footnotes":""},"categories":[19,59],"tags":[],"class_list":["post-2189","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-digital-strategy","category-eliah-gogo-creative-studio"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tFive checks you can do yourself today<\/h2>\n
\n
How we support you<\/h2>\n