EVOLIZEDIGITAL RISK INTELLIGENCE
RUN FREE ASSESSMENT
RUN FREE ASSESSMENT
Public accessibility assessment

Accessibility issues detected on willkommenszentrum.berlin.de

Evolize inspected 5 public pages on willkommenszentrum.berlin.de and detected 27 automatically identifiable accessibility findings.

27Findings detected
6WCAG criteria affected
5Pages inspected
26 Aug 2026Assessment date

Highest detected severity: Critical · 2 high-priority findings · 100% inspected-page coverage

Most widespread issueText has insufficient colour contrastDetected on 5 inspected pages
Most affected page/glossary/familienservicebuero-family-services-office16 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)12 detected findings

Is willkommenszentrum.berlin.de your website?

Keep this assessment current and get notified when new accessibility issues are detected.

MONITOR THIS WEBSITERUN A FREE ASSESSMENT
https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on willkommenszentrum.berlin.de and detected 27 accessibility findings. The most widespread issue was "Text has insufficient colour contrast", detected on 5 inspected pages. The most affected inspected page was "/glossary/familienservicebuero-family-services-office", where 16 findings were detected. The assessment identified findings mapped to 6 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.

02 · Start here

These findings combine the highest severity and broadest reach detected during this assessment.

  1. Critical

    ARIA command controls lack accessible names

    WCAG 4.1.2 (A) · 1 inspected page · 22 instances
    Why this matters

    Assistive technologies cannot communicate the purpose of these controls, which may prevent users from operating them reliably.

    Recommended action

    This control is a <div> with role="button" acting as a button. Prefer replacing it with a native <button>, which is focusable and operable by keyboard by default. Give it an accessible name that describes the action it performs: provide visible text when a visible label is appropriate, an aria-label for an icon-only control (for example aria-label="Dismiss notification"), or aria-labelledby when an existing visible label already describes it. Avoid vague names such as "Button", "Action", or the component's internal name.

    View technical evidence →
  2. High

    Interactive controls are not keyboard-accessible

    WCAG 2.1.1 (A) · 1 inspected page · 24 instances
    Why this matters

    A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

    Recommended action

    Add a tabindex attribute to the interactive element, or use a native HTML element with built-in keyboard focus support, such as a button element.

    View technical evidence →
  3. Medium

    Navigation regions are not distinguishable

    WCAG 1.3.1 (A) · 5 inspected pages · 10 instances
    Why this matters

    The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

    Recommended action

    Add an accessible name to the navigation region to distinguish it from others. This can be achieved by adding an 'aria-label' attribute to the element with the 'navigation' role.

    View technical evidence →
  4. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 5 inspected pages · 5 instances
    Why this matters

    Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

    Recommended action

    To make this control easier to use, increase its size to at least 24x24 pixels or ensure that it has a larger tap target. Consider adding padding or a wrapper element with sufficient size to achieve this.

    View technical evidence →
  5. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 5 inspected pages · 5 instances
    Why this matters

    Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

    Recommended action

    Increase the size of the touch target to at least 24x24px to ensure reliable activation by touch on mobile devices. Consider using CSS to set a minimum width and height for the element, or wrapping the element in a container with sufficient padding.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA1255 / 5
2.5.8Target Size (Minimum)AA855 / 5
1.3.1Info and RelationshipsA255 / 5
2.4.3Focus OrderA222 / 5
4.1.2Name, Role, ValueA222 / 5
2.1.1KeyboardA111 / 5

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

Continuous monitoring

A scan shows today's exposure. Monitoring shows what changes next.

Evolize continuously reassesses public website pages, detects newly introduced or recurring accessibility findings, and tracks remediation over time.

MONITOR WILLKOMMENSZENTRUM.BERLIN.DESEE PRICING

04 · All detected findings

Critical

ARIA command controls lack accessible names

WCAG 4.1.2 (A)22 instances1 inspected page

Assistive technologies cannot communicate the purpose of these controls, which may prevent users from operating them reliably.

Why it matters

Assistive technologies cannot communicate the purpose of these controls, which may prevent users from operating them reliably.

Recommended correction

This control is a <div> with role="button" acting as a button. Prefer replacing it with a native <button>, which is focusable and operable by keyboard by default. Give it an accessible name that describes the action it performs: provide visible text when a visible label is appropriate, an aria-label for an icon-only control (for example aria-label="Dismiss notification"), or aria-labelledby when an existing visible label already describes it. Avoid vague names such as "Button", "Action", or the component's internal name.

View 22 affected elements
Component · Ref 6DMA9E
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Element.leaflet-map-divicon.leaflet-marker-icon.leaflet-interactive:nth-child(1)
Accessible name52.488523, 13.308125
Rolebutton
Markup
<div class="leaflet-marker-icon leaflet-map-divicon leaflet-zoom-animated leaflet-interactive" tabindex="0" role="button" style="transform: translate3d(427px, 234px, 0px); z-index: 234;">
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)24 instances1 inspected page

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Why it matters

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Recommended correction

Add a tabindex attribute to the interactive element, or use a native HTML element with built-in keyboard focus support, such as a button element.

View 24 affected elements
Component · Ref HG3S0W
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Elementa#trigger--map-marker-flyin--2629
Rolebutton
Markup
<a id="trigger--map-marker-flyin--2629" role="button" class="js-flyin-overlay-toggler initialized" data-layout="flyin" data-containerid="#map-marker-flyin--2629" data-auralopentext="Click to open overlay" data-auralclosetext="Click to close overlay" data-opentext="Click to flyin" data-closetext="Schließen" data-title="FamilienServiceBüro" aria-expanded="false">
    </a>
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)53 instances5 inspected pages

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Why it matters

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Recommended correction

To improve the accessibility of this element, consider adjusting the text color or background color to meet the minimum contrast ratio of 4.5:1 for normal text. You can use online tools to determine the contrast ratio and select colors that meet the accessibility standards.

View 53 affected elements
Component · Ref F0QBZ
Affected pagehttps://willkommenszentrum.berlin.de/en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments
Elementol > li:nth-child(3)
Accessible nameMietschuldenfreiheitsbescheinigung (certificate of arrears-free rent payments)
Markup
<li>
                      Mietschuldenfreiheitsbescheinigung (certificate of arrears-free rent payments)
                  </li>
Affected pages/en/about-us /glossary/familienservicebuero-family-services-office /en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments /en/search
Component · Ref 1SC7V4
Affected pagehttps://willkommenszentrum.berlin.de/en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments
Elementli:nth-child(1) > a[href="/en"]
Accessible nameHome
Markup
<a href="/en">Home</a>
Affected pages/en/about-us /glossary/familienservicebuero-family-services-office /en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments /en/search
Component · Ref IPYD9T
Affected pagehttps://willkommenszentrum.berlin.de/en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments
Element.to-top
Accessible nameTop of page
Markup
<a class="to-top" href="#top">Top of page</a>
Affected pages/en/about-us /en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments /en/search
Component · Ref XBCDJT
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Element.leaflet-control-attribution
Accessible nameLeaflet(Link ist extern) | © OpenStreetMap(Link ist extern) contributors
Markup
<div class="leaflet-control-attribution leaflet-control">
Component · Ref 68QWR3
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Elementa[href$="leafletjs.com"] > .extlink-nobreak
Accessible nameLeaflet(Link ist extern)
Markup
<span class="extlink-nobreak">
Component · Ref PB05RZ
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Element.leaflet-control-zoom-out > span[aria-hidden="true"]
Accessible name−
Markup
<span aria-hidden="true">−</span>
Component · Ref SVG2OZ
Affected pagehttps://willkommenszentrum.berlin.de/
Element.playback-button
Accessible nameAnimation anhalten
Markup
<button class="playback-button">Animation anhalten</button>
Component · Ref KVLA4W
Affected pagehttps://willkommenszentrum.berlin.de/
Elementa[href$="fuer-gefluechtete"]
Accessible nameFür Geflüchtete
Markup
<a class="title" data-mainlink="true" href="/fuer-gefluechtete">  Für Geflüchtete
</a>
Component · Ref QLUCY5
Affected pagehttps://willkommenszentrum.berlin.de/
Element.subtitle > span[lang="de"][dir="ltr"]
Accessible nameDeine Themen. Unsere Unterstützung.
Markup
<span lang="de" dir="ltr">Deine Themen. Unsere Unterstützung.</span>
Component · Ref OA2CFE
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Element.leaflet-control-scale-line
Accessible name5 km
Markup
<div class="leaflet-control-scale-line" style="width: 54px;">5 km</div>
Component · Ref NJ27AY
Affected pagehttps://willkommenszentrum.berlin.de/
Elementp:nth-child(1) > span[lang="de"][dir="ltr"]
Accessible nameWillkommen in Berlin!
Markup
<span lang="de" dir="ltr">Willkommen in Berlin!</span>
Component · Ref T77Z0O
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Element.view-content > h3:nth-child(1)
Accessible nameBezirksamt Charlottenburg-Wilmersdorf
Markup
<h3>Bezirksamt Charlottenburg-Wilmersdorf</h3>
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)45 instances5 inspected pages

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Why it matters

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Recommended correction

To make this control easier to use, increase its size to at least 24x24 pixels or ensure that it has a larger tap target. Consider adding padding or a wrapper element with sufficient size to achieve this.

View 45 affected elements
Component · Ref JQAUCV
Affected pagehttps://willkommenszentrum.berlin.de/en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments
Elementheader#header > div:nth-of-type(2) > div:nth-of-type(1) > div > a
Accessible nameWillkommenszentrum
Markup
<a href="/en" title="To the homepage">
          Willkommenszentrum
        </a>
Affected pages/ /en/about-us /glossary/familienservicebuero-family-services-office /en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments /en/search
Component · Ref LI95MX
Affected pagehttps://willkommenszentrum.berlin.de/en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments
Elementhtml > body > a
Accessible nameSkip to main content
Markup
<a href="#main-content" class="visually-hidden focusable skip-link">
      Skip to main content
    </a>
Affected pages/ /en/about-us /glossary/familienservicebuero-family-services-office /en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments /en/search
Component · Ref M0OYW0
Affected pagehttps://willkommenszentrum.berlin.de/en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments
Elementdiv#content-header > nav > ol > li:nth-of-type(1) > a
Accessible nameHome
Markup
<a href="/en">Home</a>
Affected pages/en/about-us /glossary/familienservicebuero-family-services-office /en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments /en/search
Component · Ref HT7P37
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Elementspan > article > div:nth-of-type(2) > div:nth-of-type(3) > div:nth-of-type(2) > a
Accessible name(030) 9029 22222(Link ist eine Telefonnummer)
Markup
<a href="tel:%28030%29902922222" class="tel" data-extlink="">(030) 9029 <span class="extlink-nobreak">22222<svg focusable="false" width="1em" height="1em" class="tel" data-extlink-placement="append" aria-label="(Link ist eine Telefonnummer)" viewBox="0 0 181.352 181.352" role="img" aria-hidden="false"><title>(Link ist eine Telefonnummer)</title><path xmlns="http://www.w3.org/2000/svg" d="M169.393,167.37l-14.919,9.848c-9.604,6.614-50.531,14.049-106.211-53.404C-5.415,58.873,9.934,22.86,17.134,14.555L29.523,1.678c2.921-2.491,7.328-2.198,9.839,0.811l32.583,38.543l0.02,0.02c2.384,2.824,2.306,7.22-0…
Component · Ref F8L94N
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Elementdiv#leaflet-map-view-location-block-map-locations > div:nth-of-type(4) > div:nth-of-type(4) > div:nth-of-type(2) > a:nth-of-type(1)
Accessible nameLeaflet(Link ist extern)
Markup
<a href="https://leafletjs.com" title="A JavaScript library for interactive maps (wird in einem neuen Fenster geöffnet)" class="ext" data-extlink="" target="_blank" rel="noopener noreferrer"><svg aria-hidden="true" xmlns="http://www.w3.org/2000/svg" width="12" height="8" viewBox="0 0 12 8" class="leaflet-attribution-flag"><path fill="#4C7BE1" d="M0 0h12v4H0z"></path><path fill="#FFD500" d="M0 4h12v3H0z"></path><path fill="#E0BC00" d="M0 7h12v1H0z"></path></svg> <span class="extlink-nobreak">Leaflet<svg focusable="false" width="1em" height="1em" class="ext" data-extlink-placement="append" aria-…
Component · Ref SBN1SW
Affected pagehttps://willkommenszentrum.berlin.de/
Elementsection > ul > li:nth-of-type(1) > div > div:nth-of-type(2) > a
Accessible nameFür Geflüchtete
Markup
<a class="title" data-mainlink="true" href="/fuer-gefluechtete">  Für Geflüchtete
</a>
Component · Ref FCVN4V
Affected pagehttps://willkommenszentrum.berlin.de/en/search
Elementdiv > ul > li:nth-of-type(1) > article > h3 > a
Accessible nameLearning German
Markup
<a href="/en/learning-german" rel="bookmark">Learning German</a>
Component · Ref WUNQFM
Affected pagehttps://willkommenszentrum.berlin.de/
Elementdiv#block-content-frontpage-slider-2-field-frontpage-slidetext > button
Accessible nameAnimation anhalten
Markup
<button class="playback-button">Animation anhalten</button>
Medium

Navigation regions are not distinguishable

WCAG 1.3.1 (A)10 instances5 inspected pages

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Why it matters

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Recommended correction

Add an accessible name to the navigation region to distinguish it from others. This can be achieved by adding an 'aria-label' attribute to the element with the 'navigation' role.

View 10 affected elements
Component · Ref OROOCI
Affected pagehttps://willkommenszentrum.berlin.de/
Elementdiv#block-dwz-languageswitcher
Accessible nameEnglishDeutschРусскийTürkçeعربية
Rolenavigation
Markup
<div class="language-switcher-language-url" id="block-dwz-languageswitcher" role="navigation">
  
  
      <div><ul class="list--clean"><li data-drupal-language="en" data-drupal-link-system-path="<front>"><a href="/en" class="language-link" hreflang="en" data-drupal-link-system-path="<front>">English</a></li><li data-drupal-language="de" data-drupal-link-system-path="<front>" class="is-active" aria-current="page"><a href="/" class="language-link is-active" hreflang="de" data-drupal-link-system-path="<front>" aria-current="page">Deutsch</a></li><li data-drupal-language="ru" data-drupal-link-sys…
Affected pages/ /en/about-us /glossary/familienservicebuero-family-services-office /en/glossary/mietschuldenfreiheitsbescheinigung-certificate-arrears-free-rent-payments /en/search
Medium

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)27 instances2 inspected pages

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Why it matters

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Recommended correction

Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

View 27 affected elements
Component · Ref A9DXDW
Affected pagehttps://willkommenszentrum.berlin.de/glossary/familienservicebuero-family-services-office
Elementdiv#leaflet-map-view-location-block-map-locations > div:nth-of-type(3) > div:nth-of-type(4) > div:nth-of-type(1)
Accessible name52.488523, 13.308125
Rolebutton
Markup
<div class="leaflet-marker-icon leaflet-map-divicon leaflet-zoom-animated leaflet-interactive" tabindex="0" role="button" style="transform: translate3d(427px, 234px, 0px); z-index: 234;"><div id="map-marker--2629--wrapper" class="leaflet-pin--wrapper"><span class="hidden"><span class="latlon latlon-lat">52.488523</span>, <span class="latlon latlon-lon">13.308125</span></span>    <img src="/themes/custom/dwz/images/pin-light-green.svg" width="25" height="41" class="leaflet-marker-icon leaflet-zoom-animated leaflet-interactive custom-flyin-overlay-proxy" alt="" tabindex="0" data-destination="#tr…
Component · Ref 55W1R2
Affected pagehttps://willkommenszentrum.berlin.de/en/search
Elementdiv > div > nav > ul > li:nth-of-type(1) > a
Accessible namePage 1
Markup
<a href="?page=0" title="Current page" aria-current="page">
            <span class="visually-hidden">
              Page
            </span>1</a>
Low

ARIA attributes have invalid values

WCAG 4.1.2 (A)2 instances1 inspected page

ARIA attributes reference ids that do not exist or hold invalid values, breaking the accessibility tree.

Why it matters

ARIA attributes reference ids that do not exist or hold invalid values, breaking the accessibility tree.

Recommended correction

Ensure that all ARIA attributes have valid values. In this case, verify that the id 'pagination-heading' exists in the document and that the aria-label attribute is correctly set to 'Seite wechseln'. Update the aria-labelledby attribute to reference a valid id if necessary.

View 2 affected elements
Component · Ref L1HKEC
Affected pagehttps://willkommenszentrum.berlin.de/en/search
Element.pagination
Accessible nameSeite wechseln
Rolenavigation
Markup
<nav class="pagination" role="navigation" aria-labelledby="pagination-heading" aria-label="Seite wechseln">
Low

Content sits outside any landmark region

WCAG 1.3.1 (A)2 instances1 inspected page

Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.

Why it matters

Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.

Recommended correction

Wrap the content in a landmark region such as a header, nav, main, footer, or aside to enable assistive technology users to reach it via landmark navigation.

View 2 affected elements
Component · Ref 6KTA7H
Affected pagehttps://willkommenszentrum.berlin.de/
Elementdiv#swiper-wrapper-f43f5af32c65f21e > li:nth-of-type(1)
Accessible name1 / 5
Rolegroup
Markup
<li class="swiper-slide swiper-slide-text-long swiper-slide-visible swiper-slide-fully-visible swiper-slide-active" role="group" aria-label="1 / 5" data-swiper-slide-index="0" style="width: 1440px; opacity: 1; transform: translate3d(0px, 0px, 0px);"><p class="title"><span lang="de" dir="ltr">Willkommen in Berlin!</span></p><p class="subtitle"><span lang="de" dir="ltr">Deine Themen. Unsere Unterstützung.</span></p></li>

05 · Most affected inspected pages

06 · About this assessment

Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.

  • Publicly accessible surfaces only — no credentials, private systems, or source-code access.
  • Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
  • Results reflect the site at the scan date and may have changed since.

Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment

07 · Continuous monitoring

This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.

MONITOR THIS WEBSITESEE PRICING

Is information in this report inaccurate or outdated? Request a correction or removal.