Public accessibility assessment

Accessibility issues detected on advanzia.com

Evolize inspected 5 public pages on advanzia.com and detected 20 automatically identifiable accessibility findings.

20Findings detected
7WCAG criteria affected
5Pages inspected
3 Sep 2026Assessment date

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

Most widespread issueButtons have no accessible nameDetected on 5 inspected pages
Most affected page/en/contact15 findings detected
Most represented WCAG criterionWCAG 2.4.3 — Focus Order6 detected findings

Is advanzia.com your website?

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

https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on advanzia.com and detected 20 accessibility findings. The most widespread issue was "Buttons have no accessible name", detected on 5 inspected pages. The most affected inspected page was "/en/contact", where 15 findings were detected. The assessment identified findings mapped to 7 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

    Buttons have no accessible name

    WCAG 4.1.2 (A) · 5 inspected pages · 9 instances
    Why this matters

    Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

    Recommended action

    Add a text description or aria-label attribute to the button element so that its purpose can be determined by assistive technology.

    View technical evidence →
  2. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 4 instances
    Why this matters

    Links expose no accessible name, so screen-reader users cannot determine their destination.

    Recommended action

    Add text to the link that describes its purpose, such as 'Download on the App Store'. Alternatively, use the 'aria-label' attribute to provide a text description of the link's purpose.

    View technical evidence →
  3. Critical

    ARIA command controls lack accessible names

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

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

    Recommended action

    Add an aria-label attribute to the button element to provide an accessible name, e.g., aria-label='Zoom to location' or aria-label='Show details'. Ensure the label accurately describes the button's purpose.

    View technical evidence →
  4. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 45 instances
    Why this 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 action

    To fix this issue, ensure that the hidden element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using CSS to set its 'display' or 'visibility' property to 'none' when it's not visible. For example, you can add the following CSS rule: '.lg\:hidden { display: none; }'

    View technical evidence →
  5. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 20 instances
    Why this 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 action

    To fix this issue, ensure that the element is either removed from the tab order when it's not visible or make it visible when it receives focus. This can be achieved by adding a conditional statement to check the element's visibility before setting its tabindex or by adjusting the CSS to display the element when it's focused.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
2.4.3Focus OrderA655 / 5
2.5.8Target Size (Minimum)AA655 / 5
1.4.3Contrast (Minimum)AA455 / 5
4.1.2Name, Role, ValueA255 / 5
2.1.1KeyboardA111 / 5
2.2.2Pause, Stop, HideA111 / 5
2.4.4Link Purpose (In Context)A111 / 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.

04 · All detected findings

Critical

Buttons have no accessible name

WCAG 4.1.2 (A)9 instances5 inspected pages

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Why it matters

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Recommended correction

Add a text description or aria-label attribute to the button element so that its purpose can be determined by assistive technology.

View 9 affected elements
Component · Ref 6U2TN6
Affected pagehttps://www.advanzia.com/en
Element#ppms_cm_bar-close-icon
Markup
<button id="ppms_cm_bar-close-icon" class="ppms_cm_bar-close-icon" data-disable-select="true">
Affected pages/ /de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact /en/customer-service
Critical

ARIA command controls lack accessible names

WCAG 4.1.2 (A)2 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

Add an aria-label attribute to the button element to provide an accessible name, e.g., aria-label='Zoom to location' or aria-label='Show details'. Ensure the label accurately describes the button's purpose.

View 2 affected elements
Component · Ref HYLKIS
Affected pagehttps://www.advanzia.com/en/contact
Element.leaflet-marker-icon
Rolebutton
Markup
<div class="leaflet-marker-icon custom-map-pin leaflet-zoom-animated leaflet-interactive" tabindex="0" role="button" style="margin-left: -24px; margin-top: -48px; width: 48px; height: 48px; transform: translate3d(608px, 192px, 0px); z-index: 192;">
High

Text has insufficient colour contrast

WCAG 1.4.3 (AA)17 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 accessibility, adjust the color scheme to meet the minimum contrast ratio of 4.5:1 for normal text and 7:1 for larger text (18pt or 14pt bold). Consider using a color contrast analyzer tool to find suitable colors.

View 17 affected elements
Component · Ref R8JWAZ
Affected pagehttps://www.advanzia.com/en
Element#ppms_cm_open-popup
Accessible nameSet your privacy
Markup
<button id="ppms_cm_open-popup" data-disable-interaction="true" class="ppms_cm_set_your_consent">Set your privacy</button>
Affected pages/ /de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact /en/customer-service
Component · Ref L4XXTY
Affected pagehttps://www.advanzia.com/en/contact
Element#ppms_cm_main_text
Accessible nameWe don't know what your privacy preferences are yet.
Markup
<p id="ppms_cm_main_text" class="ppms_cm_main_text">We don't know what your privacy preferences are yet.</p>
Affected pages/en/contact /en/customer-service
Component · Ref GN6JO5
Affected pagehttps://www.advanzia.com/en/contact
Element.leaflet-control-zoom-out > span
Accessible name
Markup
<span aria-hidden="true">−</span>
Component · Ref BIOFJG
Affected pagehttps://www.advanzia.com/en/contact
Elementa[href$="leafletjs.com"]
Accessible nameLeaflet
Markup
<a href="https://leafletjs.com" title="A JavaScript library for interactive maps">
High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)82 instances5 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

To fix this issue, ensure that the element is either removed from the tab order when it's not visible or make it visible when it receives focus. This can be achieved by adding a conditional statement to check the element's visibility before setting its tabindex or by adjusting the CSS to display the element when it's focused.

View 82 affected elements
Component · Ref XL5FPR
Affected pagehttps://www.advanzia.com/en
Elementdiv:nth-of-type(2) > nav > div > div > div:nth-of-type(2) > button
Accessible nameOpen navigation menu
Markup
<button class="text-advanzia-black hover:text-advanzia-dark-blue rounded-full bg-white p-2" aria-label="Open navigation menu" aria-expanded="false" aria-controls="mobile-menu" tabindex="0"><svg class="h-6 w-6" fill="none" viewBox="0 0 24 24" stroke="currentColor" aria-hidden="true"><path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M4 6h16M4 12h16M4 18h16"></path></svg></button>
Affected pages/ /de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact /en/customer-service
Component · Ref LDYZ0A
Affected pagehttps://www.advanzia.com/en
Elementdiv > div > div > div > div:nth-of-type(2) > button:nth-of-type(1)
Accessible nameDeutsch
Markup
<button class="px-4 py-2 text-sm rounded-full transition-colors bg-white text-advanzia-dark-blue">Deutsch</button>
Affected pages/ /de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact /en/customer-service
Component · Ref X16FQT
Affected pagehttps://www.advanzia.com/en
Elementhtml > body > div:nth-of-type(3) > button
Accessible nameScroll to top
Markup
<button class="
          flex items-center justify-center
          w-12 h-12
          bg-white
          border
          border-advanzia-dark-blue
          hover:bg-advanzia-dark-blue
          text-advanzia-dark-blue
          hover:text-white
          rounded-full
          shadow-lg
          transition-all duration-300 ease-in-out
          transform hover:scale-110
          opacity-0 translate-y-2 pointer-events-none
        " aria-label="Scroll to top"><svg xmlns="http://www.w3.org/2000/svg" width="30" height="30" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width=…
Affected pages/ /de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact
Component · Ref BS72VY
Affected pagehttps://www.advanzia.com/en
Elementbutton#ppms_cm_save-choices
Accessible nameSave and close
Markup
<button class="ppms_cm_save-choices" id="ppms_cm_save-choices">Save and close</button>
Affected pages/ /en/customer-service
Component · Ref 10ZVDQ
Affected pagehttps://www.advanzia.com/en/customer-service
Elementdiv#m-panel-0 > div > div > div:nth-of-type(1) > a:nth-of-type(1)
Accessible nameCustomer portal
Markup
<a target="_blank" rel="noopener noreferrer" class="group inline-flex items-center justify-between gap-3 font-normal focus:outline-none focus:ring-2 focus:ring-offset-2 transition-colors rounded-full text-advanzia-dark-blue border border-advanzia-dark-blue bg-white hover:bg-advanzia-dark-blue hover:text-white focus:ring-advanzia-dark-blue px-6 py-3 text-lg lg:text-xl w-full justify-between rounded-full px-5 py-3" href="https://mein.gebuhrenfrei.com/"><span>Customer portal</span><span aria-hidden="true" class="shrink-0"><svg width="31" height="32" viewBox="0 0 31 32" fill="none" xmlns="http://w…
Component · Ref GW6TSR
Affected pagehttps://www.advanzia.com/en
Elementdiv#ppms_cm_language_select_extendable_item_0
Accessible nameEnglish
Markup
<div id="ppms_cm_language_select_extendable_item_0" class="ppms_cm_language_select_extendable_item" data-type="customOption" data-value="en" data-fixed-text="true" tabindex="0">English</div>
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)42 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 fix this issue, ensure that the touch target for the 'Cookie settings' link is at least 24x24px in size. Consider increasing the size of the link or adding padding around it to make it easier to tap on mobile devices.

View 42 affected elements
Component · Ref HXUT5Z
Affected pagehttps://www.advanzia.com/en
Elementa#servicenav_link_cookiesettings
Accessible nameOpen cookie consent settings
Markup
<a id="servicenav_link_cookiesettings" href="#" class="meta__navigation-links" aria-label="Open cookie consent settings">Cookie settings</a>
Affected pages/ /de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact /en/customer-service
Component · Ref IUSXDP
Affected pagehttps://www.advanzia.com/en
Elementbutton#ppms_cm_bar-close-icon
Markup
<button id="ppms_cm_bar-close-icon" class="ppms_cm_bar-close-icon" data-disable-select="true"><svg id="ppms_cm_close_icon_svg" class="ppms_cm_close_icon_svg" height="16" width="16" xmlns="http://www.w3.org/2000/svg" data-viewbox="0 0 16 16"><switch data-disable-select="true"><g data-disable-select="true"><path d="M2.188 4.406l2.244-2.25 9.725 9.75-2.244 2.25-9.726-9.75" data-disable-select="true"></path><path d="M11.913 2.156l2.244 2.25-9.725 9.75-2.245-2.25 9.726-9.75" data-disable-select="true"></path></g></switch></svg></button>
Affected pages/ /de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact /en/customer-service
Component · Ref 3X8D2B
Affected pagehttps://www.advanzia.com/en/news/advanzia-bank-launches-mobile-payment-in-germany
Elementhtml > body > a
Accessible nameSkip to main content
Markup
<a tabindex="0" href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-4 focus:left-4 focus:z-[9999] focus:px-4 focus:py-2 focus:bg-advanzia-dark-blue focus:text-white focus:rounded-md focus:outline-none focus:ring-2 focus:ring-offset-2 focus:ring-advanzia-blue">Skip to main content</a>
Affected pages/ /de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact /en/customer-service
Component · Ref 9PUY78
Affected pagehttps://www.advanzia.com/en/news/advanzia-bank-launches-mobile-payment-in-germany
Elementbody > footer > div > div > div:nth-of-type(2) > a:nth-of-type(1)
Accessible nameLegal
Markup
<a class="hover:underline" aria-label="Legal" href="/en/legal">Legal</a>
Affected pages/ /de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact /en/customer-service
Component · Ref BWPVMD
Affected pagehttps://www.advanzia.com/en/news/advanzia-bank-launches-mobile-payment-in-germany
Elementdiv:nth-of-type(2) > div:nth-of-type(2) > nav > ol > li:nth-of-type(1) > a
Accessible nameHome
Markup
<a class="text-advanzia-dark-blue font-bold hover:text-advanzia-cyan transition-colors" href="/en">Home</a>
Affected pages/de/news/advanzia-bank-fuehrt-mobile-payment-in-deutschland-ein /en/news/advanzia-bank-launches-mobile-payment-in-germany /en/contact /en/customer-service
Component · Ref ECJ2MX
Affected pagehttps://www.advanzia.com/en/contact
Elementdiv > div > div:nth-of-type(2) > div:nth-of-type(4) > div > a
Accessible nameLeaflet
Markup
<a href="https://leafletjs.com" title="A JavaScript library for interactive maps"><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> Leaflet</a>

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.

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