Public accessibility assessment

Accessibility issues detected on kappahl.com

Evolize inspected 5 public pages on kappahl.com and detected 26 automatically identifiable accessibility findings.

26Findings detected
9WCAG criteria affected
5Pages inspected
1 Sep 2026Assessment date

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

Most widespread issueTouch targets are too small on mobileDetected on 5 inspected pages
Most affected page/en-us/about-kappahl-group/media--news/press-photos15 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)7 detected findings

Is kappahl.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 kappahl.com and detected 26 accessibility findings. The most widespread issue was "Touch targets are too small on mobile", detected on 5 inspected pages. The most affected inspected page was "/en-us/about-kappahl-group/media--news/press-photos", where 15 findings were detected. The assessment identified findings mapped to 9 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

    Form fields are missing labels

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

    Form inputs have no programmatically associated label, so assistive technology cannot announce what to enter.

    Recommended action

    Associate a <label> with each field via for/id, or use aria-label / aria-labelledby. Placeholder text is not a label.

    View technical evidence →
  2. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 4 inspected pages · 8 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, remove the 'tabindex' attribute or set it to '-1' for the button with id 'flyout-menu-item-about-us-button' when it is not visible, so that it does not receive keyboard focus when it is hidden. Alternatively, ensure the button is visible when it receives focus.

    View technical evidence →
  3. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 4 inspected pages · 8 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 button element is removed from the tab order by setting its 'tabindex' attribute to '-1' or by using the 'display: none' or 'visibility: hidden' CSS properties to completely hide it. This will prevent sighted keyboard users from losing track of focus when navigating through the page.

    View technical evidence →
  4. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 4 inspected pages · 8 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 'Skip to content' link is visible when it receives keyboard focus. You can do this by removing any CSS rules that hide the link, or by adding a visible focus indicator to the link. For example, you can add the following CSS rule: .e.f.g.h.i.j.k.l.m.n.o.p.q.r.s.t.u.v.w.x.y.z.a0.a1.a2.a3.a4.a5.a6:focus { visibility: visible; }

    View technical evidence →
  5. High

    ARIA hidden element must not be focusable or contain focusable elements

    WCAG 4.1.2 (A) · 4 inspected pages · 8 instances
    Why this matters

    ARIA hidden element must not be focusable or contain focusable elements

    Recommended action

    To fix this issue, ensure that the dialog element with aria-hidden='true' is not focusable and does not contain any focusable elements. Consider removing the focusable elements or setting aria-hidden to false when the dialog is visible.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA755 / 5
2.5.8Target Size (Minimum)AA655 / 5
1.3.1Info and RelationshipsA555 / 5
2.4.3Focus OrderA344 / 5
2.4.1Bypass BlocksA255 / 5
4.1.2Name, Role, ValueA255 / 5
1.4.4Resize TextAA111 / 5
2.1.2No Keyboard TrapA122 / 5
3.3.2Labels or InstructionsA111 / 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

Form fields are missing labels

WCAG 1.3.1 (A)2 instances1 inspected page

Form inputs have no programmatically associated label, so assistive technology cannot announce what to enter.

Why it matters

Form inputs have no programmatically associated label, so assistive technology cannot announce what to enter.

Recommended correction

Associate a <label> with each field via for/id, or use aria-label / aria-labelledby. Placeholder text is not a label.

View 2 affected elements
Component · Ref 63SVIR
Affected pagehttps://id.kappahl.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D5d5acfc6-ca3a-4f51-93b2-94509e036fdf%26redirect_uri%3Dhttps%253A%252F%252Fwww.kappahl.com%252Fapi%252Foauth%252Fcallback%26response_type%3Dcode%26scope%3Dcustomers.read%2520customers.write%2520offline_access%2520openid%26code_challenge%3D3W5PGm6XevADCN1QRWt4no3DlQiqz1bzzLYSpC8-2XE%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D639238671619619883.NmMxM2EzZmMtYTA3NS00YzM3LWE5ZmQtZjlkOWQ0ZjkxNGFhMGVhZjQ3MTYtZmFiYS00OTk4LTllMGYtY2ZhYzFkMGY4Nzkw%26login_hint%3DUS%26state%3DCfDJ8CHyIOQm2N5Omb1rW3Dfh3lPeWTEpO8AxpxGuWPp74BEjx_mE4_1fNRJgRviwaGoXdE73ywyuL0bh7l9glvtErYDODyft6Px5nRy2JI-fArw0KQ00zzEN9pMKDDQGbF4j4nff3iBKzAH-ICoP1dKTa7ZIhRNrBFxqq8jueb48hp49tKy0f8Byb04y2whGlEs9KVhRb65AarvtnEPUStMxaR0cKbo3kLS8i_l7ohvlqTtvfd0ePEy78xc4HUpWh-VP8MVSty6p9FqhygaFLkiCcA-jljD2-XzmLITgq7DK-GRXR7K0NB6yIJ7ZMSnp9k6zFf-iNtDOty0i4G_oN_EKGzu2A6QZ7htphS9bGYM5TRCa5NmF8zoAHJgWrDcBnCHUrbsTf3mXJ-15KnrYuhyeuO0cbuYDoNDypazRwzUD0x4qdpW6zewGpae4EukRgcSannk33PZnGeVIjAsoEC2miB2kxjpyO9ucfdOvG-mdZB1LHTWTT0Qj1Sw1eFN3u-Ye9YTTltswd4cNlkyRO_26Yrfhg3vVCojsjSFj4XS44RZvqfiJxisHbUHBCIEet5apg%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.0.1.0
Element#username
Markup
<input class="input-field" id="username" placeholder=" " autocomplete="username" type="text" name="Input.Username" value="">
High

ARIA hidden element must not be focusable or contain focusable elements

WCAG 4.1.2 (A)8 instances4 inspected pages

ARIA hidden element must not be focusable or contain focusable elements

Why it matters

ARIA hidden element must not be focusable or contain focusable elements

Recommended correction

To fix this issue, ensure that the dialog element with aria-hidden='true' is not focusable and does not contain any focusable elements. Consider removing the focusable elements or setting aria-hidden to false when the dialog is visible.

View 8 affected elements
Component · Ref LVLZCN
Affected pagehttps://www.kappahl.com/en-us
Elementdialog
Accessible nameAbout usSustainabilityWork with usMedia & newsThis is Kappahl GroupManagement & BoardHistoryOverviewSustainability targetsClimateSocial sustainabilitySustainability reportsSuppliers & factoriesLabels and certificationsPartnerships & collaborationsSupporting children’s rightsOverviewCurrent vacanciesOpen applicationWork placement & dissertationWork in our storesWork within the Kappahl GroupCulture & valuesWork-life balanceOverview & media contactsNewsPress imagesAccessibilityContact usReport a concern
Markup
<dialog aria-hidden="true" class="h6 h7 h8 h9 a8 ha hb hc hd b6 c7 he hf hg hh hi hj hk hl b c hm hn d5 ho o bw bx by bz q gq" style="transform: translateX(-100%);">
Affected pages/ /en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)24 instances4 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 'Skip to content' link is visible when it receives keyboard focus. You can do this by removing any CSS rules that hide the link, or by adding a visible focus indicator to the link. For example, you can add the following CSS rule: .e.f.g.h.i.j.k.l.m.n.o.p.q.r.s.t.u.v.w.x.y.z.a0.a1.a2.a3.a4.a5.a6:focus { visibility: visible; }

View 24 affected elements
Component · Ref EOTEKB
Affected pagehttps://www.kappahl.com/en-us
Elementdiv#container > div > a
Accessible nameSkip to content
Markup
<a class="e f g h i j k l m n o p q r s t u v w x y z a0 a1 a2 a3 a4 a5 a6" data-scope-link="true" href="/en-us#main">Skip to content</a>
Affected pages/ /en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Component · Ref BHYAJ5
Affected pagehttps://www.kappahl.com/en-us
Elementdiv > div > dialog > div > div > button
Accessible nameClose
Markup
<button aria-label="Close" type="button" class="hp hq b4 r a3 a4 a5 a6 a7 a8 bg ce dv bc bd be bf bi t bj bk v ai ah bm bn ga cs bq br ab bs bt bu a2 bv bw bx by bz c0 c1"><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" width="1em" height="1em" alt="" aria-hidden="true" class="cq hr hs c9 ca bs"><path stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" d="m20 4.077-16 16m0-16 16 16"></path></svg></button>
Affected pages/ /en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Component · Ref 4CDO1R
Affected pagehttps://www.kappahl.com/en-us
Elementbutton#flyout-menu-item-about-us-button
Accessible nameAbout us
Roletab
Markup
<button role="tab" id="flyout-menu-item-about-us-button" aria-controls="flyout-menu-item-about-us" aria-selected="true" tabindex="0" type="button" class="a3 a4 a5 a6 a7 a8 bg hx bc bd be bf p ew bi t u hy v ai em bm bn eo ep bq br ab bs bt bu bv bw bx by bz c0 c1"><span class="hz d5 c3 c4 eq c5 c6 c7">About us</span></button>
Affected pages/ /en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)24 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

Increase the contrast between the text color (#000000) and the background color by using a color with a higher contrast ratio, or adjust the font size to meet the minimum contrast requirements.

View 24 affected elements
Component · Ref L4QOHX
Affected pagehttps://www.kappahl.com/en-us
Element#usercentrics-root,.Paragraph.SCXW71050547[paraid="181109893"]:nth-child(3) > font
Markup
<font color="#000000" face="Segoe UI, Segoe UI Web, Arial, Verdana, sans-serif">
Affected pages/ /en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Component · Ref PFHBET
Affected pagehttps://www.kappahl.com/en-us/contact-us
Element#usercentrics-root,.sc-fxwrCY
Markup
<a href="https://usercentrics.com/consent-management-platform-powered-by-usercentrics/?utm_source=banner_uc&amp;utm_medium=referral&amp;utm_content=v2" tabindex="0" target="_blank" rel="noopener nofollow" class="sc-fxwrCY jvcgqo">Powered by Usercentrics Consent Management</a>
Affected pages/en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Component · Ref QQOFEH
Affected pagehttps://www.kappahl.com/en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections
Element.di.dk.dh:nth-child(5) > span
Accessible nameNewbie celebrates 15 years with iconic products and limited collections
Markup
<span>Newbie celebrates 15 years with iconic products and limited collections</span>
Affected pages/en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Component · Ref 8TDY6F
Affected pagehttps://id.kappahl.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D5d5acfc6-ca3a-4f51-93b2-94509e036fdf%26redirect_uri%3Dhttps%253A%252F%252Fwww.kappahl.com%252Fapi%252Foauth%252Fcallback%26response_type%3Dcode%26scope%3Dcustomers.read%2520customers.write%2520offline_access%2520openid%26code_challenge%3D3W5PGm6XevADCN1QRWt4no3DlQiqz1bzzLYSpC8-2XE%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D639238671619619883.NmMxM2EzZmMtYTA3NS00YzM3LWE5ZmQtZjlkOWQ0ZjkxNGFhMGVhZjQ3MTYtZmFiYS00OTk4LTllMGYtY2ZhYzFkMGY4Nzkw%26login_hint%3DUS%26state%3DCfDJ8CHyIOQm2N5Omb1rW3Dfh3lPeWTEpO8AxpxGuWPp74BEjx_mE4_1fNRJgRviwaGoXdE73ywyuL0bh7l9glvtErYDODyft6Px5nRy2JI-fArw0KQ00zzEN9pMKDDQGbF4j4nff3iBKzAH-ICoP1dKTa7ZIhRNrBFxqq8jueb48hp49tKy0f8Byb04y2whGlEs9KVhRb65AarvtnEPUStMxaR0cKbo3kLS8i_l7ohvlqTtvfd0ePEy78xc4HUpWh-VP8MVSty6p9FqhygaFLkiCcA-jljD2-XzmLITgq7DK-GRXR7K0NB6yIJ7ZMSnp9k6zFf-iNtDOty0i4G_oN_EKGzu2A6QZ7htphS9bGYM5TRCa5NmF8zoAHJgWrDcBnCHUrbsTf3mXJ-15KnrYuhyeuO0cbuYDoNDypazRwzUD0x4qdpW6zewGpae4EukRgcSannk33PZnGeVIjAsoEC2miB2kxjpyO9ucfdOvG-mdZB1LHTWTT0Qj1Sw1eFN3u-Ye9YTTltswd4cNlkyRO_26Yrfhg3vVCojsjSFj4XS44RZvqfiJxisHbUHBCIEet5apg%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.0.1.0
Element#username
Markup
<input class="input-field" id="username" placeholder=" " autocomplete="username" type="text" name="Input.Username" value="">
Component · Ref 0EHINQ
Affected pagehttps://www.kappahl.com/en-us/contact-us
Element.df.di.dg > span
Accessible nameContact us
Markup
<span>Contact us</span>
Component · Ref BHW624
Affected pagehttps://www.kappahl.com/en-us/about-kappahl-group/media--news/press-photos
Elementa[href$="about-kappahl-group"] > span
Accessible nameAbout Kappahl Group
Markup
<span>About Kappahl Group</span>
Component · Ref 0D2WNA
Affected pagehttps://www.kappahl.com/en-us/about-kappahl-group/media--news/press-photos
Element.df.dg.di:nth-child(2) > .dl.dm.dn > span
Accessible nameMedia & news
Markup
<span>Media &amp; news</span>
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)62 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 all interactive controls have a minimum touch target size of 24x24 pixels. Consider increasing the size of the 'Contact us' link or adding padding around it to meet this requirement.

View 62 affected elements
Component · Ref DURLBZ
Affected pagehttps://www.kappahl.com/en-us
Elementdiv#footer-link-group-contact > div > ul > li:nth-of-type(1) > a
Accessible nameContact us
Markup
<a class="df e1 cz bm bn bo bp f2 x f3 z f4 a1 f5 ah a3 a4 a5 a6" data-scope-link="true" href="/en-us/contact-us" tabindex="-1">Contact us</a>
Affected pages/ /en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Component · Ref HI2Q8F
Affected pagehttps://www.kappahl.com/en-us
Elementdiv > dialog > div > ul > li:nth-of-type(1) > a
Accessible nameThis is Kappahl Group
Markup
<a href="/en-us/about-kappahl-group/this-is-kappahl-group" tabindex="-1">This is Kappahl Group</a>
Affected pages/ /en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Component · Ref XTKVW4
Affected pagehttps://www.kappahl.com/en-us
Elementdiv > footer > div > div > div:nth-of-type(5) > button
Accessible nameCookies
Markup
<button aria-haspopup="true" type="button" class="a3 a4 a5 a6 a7 a8 bg dv bc bd be bf bi t u js v ai ah bm bn bo bp bq br ab bs bt bu a2 bv bw bx by bz c0 c1"><span class="c3 c4 eq c5 c6 c7">Cookies</span></button>
Affected pages/ /en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Component · Ref 4F8IGD
Affected pagehttps://www.kappahl.com/en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections
Elementdiv > div > div > ul > li:nth-of-type(1) > a
Accessible nameAbout Kappahl Group
Markup
<a class="dl dm c dn x do z dp a1 dq ah a3 a4 a5 a6" data-scope-link="true" href="/en-us/about-kappahl-group"><span>About Kappahl Group</span><svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" width="1em" height="1em" alt="" class="dr c8 c9 ca bs"><path stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" d="M5 12h14m0 0-7-7m7 7-7 7"></path></svg></a>
Affected pages/en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Component · Ref D4GRCP
Affected pagehttps://id.kappahl.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D5d5acfc6-ca3a-4f51-93b2-94509e036fdf%26redirect_uri%3Dhttps%253A%252F%252Fwww.kappahl.com%252Fapi%252Foauth%252Fcallback%26response_type%3Dcode%26scope%3Dcustomers.read%2520customers.write%2520offline_access%2520openid%26code_challenge%3D3W5PGm6XevADCN1QRWt4no3DlQiqz1bzzLYSpC8-2XE%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D639238671619619883.NmMxM2EzZmMtYTA3NS00YzM3LWE5ZmQtZjlkOWQ0ZjkxNGFhMGVhZjQ3MTYtZmFiYS00OTk4LTllMGYtY2ZhYzFkMGY4Nzkw%26login_hint%3DUS%26state%3DCfDJ8CHyIOQm2N5Omb1rW3Dfh3lPeWTEpO8AxpxGuWPp74BEjx_mE4_1fNRJgRviwaGoXdE73ywyuL0bh7l9glvtErYDODyft6Px5nRy2JI-fArw0KQ00zzEN9pMKDDQGbF4j4nff3iBKzAH-ICoP1dKTa7ZIhRNrBFxqq8jueb48hp49tKy0f8Byb04y2whGlEs9KVhRb65AarvtnEPUStMxaR0cKbo3kLS8i_l7ohvlqTtvfd0ePEy78xc4HUpWh-VP8MVSty6p9FqhygaFLkiCcA-jljD2-XzmLITgq7DK-GRXR7K0NB6yIJ7ZMSnp9k6zFf-iNtDOty0i4G_oN_EKGzu2A6QZ7htphS9bGYM5TRCa5NmF8zoAHJgWrDcBnCHUrbsTf3mXJ-15KnrYuhyeuO0cbuYDoNDypazRwzUD0x4qdpW6zewGpae4EukRgcSannk33PZnGeVIjAsoEC2miB2kxjpyO9ucfdOvG-mdZB1LHTWTT0Qj1Sw1eFN3u-Ye9YTTltswd4cNlkyRO_26Yrfhg3vVCojsjSFj4XS44RZvqfiJxisHbUHBCIEet5apg%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.0.1.0
Elementdiv#primary-login-view > button:nth-of-type(2)
Accessible nameForgot password?
Markup
<button class="text-button" name="Input.Button" value="reset-password">Forgot password?</button>
Component · Ref HGW161
Affected pagehttps://www.kappahl.com/en-us
Elementdiv > div:nth-of-type(6) > div > section > div:nth-of-type(2) > a
Accessible nameAll news
Markup
<a class="fh ab c ce bm bn bo bp s t u v w x y z a0 a1 a2 ah a3 a4 a5 a6" data-scope-link="true" href="/en-us/about-kappahl-group/media--news/news">All news<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" width="1em" height="1em" alt="" aria-hidden="true" class="cq fi cs c9 ca bs"><path stroke="currentColor" stroke-linecap="square" d="M4 12h16m0 0-4-4m4 4-4 4"></path></svg></a>
Medium

Content sits outside any landmark region

WCAG 1.3.1 (A)8 instances4 inspected pages

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 (e.g. header, nav, main, footer, aside) to enable assistive technology users to reach it via landmark navigation. For example, wrap the list of links in a <nav> element.

View 8 affected elements
Component · Ref PAD0CM
Affected pagehttps://www.kappahl.com/en-us
Elementdiv > div > dialog > div > ul > li:nth-of-type(10)
Accessible nameLabels and certifications
Markup
<li><a href="/en-us/sustainability/labels-certifications" tabindex="-1">Labels and certifications</a></li>
Affected pages/ /en-us/contact-us /en-us/about-kappahl-group/media--news/news/2025/newbie-celebrates-15-years-with-iconic-products-and-limited-collections /en-us/about-kappahl-group/media--news/press-photos
Medium

Keyboard focus may be trapped

WCAG 2.1.2 (A)2 instances2 inspected pages

Repeated Tab presses did not move focus through the page as expected — focus appears to cycle within a small set of elements, which can strand keyboard users. Requires manual confirmation.

Why it matters

Repeated Tab presses did not move focus through the page as expected — focus appears to cycle within a small set of elements, which can strand keyboard users. Requires manual confirmation.

Recommended correction

Review the page's focus management to ensure keyboard users can navigate through all interactive elements without getting stuck in a loop. Check for elements with `tabindex` set to a value other than 0 or -1, and ensure that the page's focus order is logical and consistent. Consider adding a `tabindex` of -1 to elements that should not receive focus, and verify that the page's JavaScript code does not interfere with the default focus behavior.

View 2 affected elements
Component · Ref 0H3ZR9
Affected pagehttps://www.kappahl.com/en-us
Elementdiv#usercentrics-root
Markup
<div></div>
Affected pages/ /en-us/contact-us
Medium

Page must have means to bypass repeated blocks

WCAG 2.4.1 (A)2 instances1 inspected page

Page must have means to bypass repeated blocks

Why it matters

Page must have means to bypass repeated blocks

Recommended correction

To address this issue, consider adding a 'Skip to main content' link at the top of the page, allowing users to bypass repeated blocks such as navigation menus and jump directly to the main content. This can be achieved by adding an anchor link with a visible or hidden target element that has an ID, and using JavaScript to focus on this element when the link is clicked.

View 2 affected elements
Component · Ref S2NUY3
Affected pagehttps://id.kappahl.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D5d5acfc6-ca3a-4f51-93b2-94509e036fdf%26redirect_uri%3Dhttps%253A%252F%252Fwww.kappahl.com%252Fapi%252Foauth%252Fcallback%26response_type%3Dcode%26scope%3Dcustomers.read%2520customers.write%2520offline_access%2520openid%26code_challenge%3D3W5PGm6XevADCN1QRWt4no3DlQiqz1bzzLYSpC8-2XE%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D639238671619619883.NmMxM2EzZmMtYTA3NS00YzM3LWE5ZmQtZjlkOWQ0ZjkxNGFhMGVhZjQ3MTYtZmFiYS00OTk4LTllMGYtY2ZhYzFkMGY4Nzkw%26login_hint%3DUS%26state%3DCfDJ8CHyIOQm2N5Omb1rW3Dfh3lPeWTEpO8AxpxGuWPp74BEjx_mE4_1fNRJgRviwaGoXdE73ywyuL0bh7l9glvtErYDODyft6Px5nRy2JI-fArw0KQ00zzEN9pMKDDQGbF4j4nff3iBKzAH-ICoP1dKTa7ZIhRNrBFxqq8jueb48hp49tKy0f8Byb04y2whGlEs9KVhRb65AarvtnEPUStMxaR0cKbo3kLS8i_l7ohvlqTtvfd0ePEy78xc4HUpWh-VP8MVSty6p9FqhygaFLkiCcA-jljD2-XzmLITgq7DK-GRXR7K0NB6yIJ7ZMSnp9k6zFf-iNtDOty0i4G_oN_EKGzu2A6QZ7htphS9bGYM5TRCa5NmF8zoAHJgWrDcBnCHUrbsTf3mXJ-15KnrYuhyeuO0cbuYDoNDypazRwzUD0x4qdpW6zewGpae4EukRgcSannk33PZnGeVIjAsoEC2miB2kxjpyO9ucfdOvG-mdZB1LHTWTT0Qj1Sw1eFN3u-Ye9YTTltswd4cNlkyRO_26Yrfhg3vVCojsjSFj4XS44RZvqfiJxisHbUHBCIEet5apg%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.0.1.0
Elementhtml
Accessible nameKappahl | Log in Log in Enter Email or Mobile number Enter your password Log in Forgot password? or log in with Apple Become member Back to Kappahl.com
Markup
<html lang="en">
Medium

Page has no main landmark

WCAG 1.3.1 (A)2 instances1 inspected page

No <main> or role=main region is present, so screen reader users cannot jump to primary content.

Why it matters

No <main> or role=main region is present, so screen reader users cannot jump to primary content.

Recommended correction

Add a main landmark to the page by wrapping the primary content in a <main> element or an element with role="main". This will allow screen reader users to jump to the primary content.

View 2 affected elements
Component · Ref 6H6V8M
Affected pagehttps://id.kappahl.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D5d5acfc6-ca3a-4f51-93b2-94509e036fdf%26redirect_uri%3Dhttps%253A%252F%252Fwww.kappahl.com%252Fapi%252Foauth%252Fcallback%26response_type%3Dcode%26scope%3Dcustomers.read%2520customers.write%2520offline_access%2520openid%26code_challenge%3D3W5PGm6XevADCN1QRWt4no3DlQiqz1bzzLYSpC8-2XE%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D639238671619619883.NmMxM2EzZmMtYTA3NS00YzM3LWE5ZmQtZjlkOWQ0ZjkxNGFhMGVhZjQ3MTYtZmFiYS00OTk4LTllMGYtY2ZhYzFkMGY4Nzkw%26login_hint%3DUS%26state%3DCfDJ8CHyIOQm2N5Omb1rW3Dfh3lPeWTEpO8AxpxGuWPp74BEjx_mE4_1fNRJgRviwaGoXdE73ywyuL0bh7l9glvtErYDODyft6Px5nRy2JI-fArw0KQ00zzEN9pMKDDQGbF4j4nff3iBKzAH-ICoP1dKTa7ZIhRNrBFxqq8jueb48hp49tKy0f8Byb04y2whGlEs9KVhRb65AarvtnEPUStMxaR0cKbo3kLS8i_l7ohvlqTtvfd0ePEy78xc4HUpWh-VP8MVSty6p9FqhygaFLkiCcA-jljD2-XzmLITgq7DK-GRXR7K0NB6yIJ7ZMSnp9k6zFf-iNtDOty0i4G_oN_EKGzu2A6QZ7htphS9bGYM5TRCa5NmF8zoAHJgWrDcBnCHUrbsTf3mXJ-15KnrYuhyeuO0cbuYDoNDypazRwzUD0x4qdpW6zewGpae4EukRgcSannk33PZnGeVIjAsoEC2miB2kxjpyO9ucfdOvG-mdZB1LHTWTT0Qj1Sw1eFN3u-Ye9YTTltswd4cNlkyRO_26Yrfhg3vVCojsjSFj4XS44RZvqfiJxisHbUHBCIEet5apg%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.0.1.0
Elementhtml > body
Accessible nameLog in Enter Email or Mobile number Enter your password Log in Forgot password? or log in with Apple Become member Back to Kappahl.com
Markup
<body>
    
<div class="nav-page">
    <nav class="navbar navbar-expand-lg">

        <a href="https://kappahl.com" class="navbar-brand">
            <img alt="KappAhl logo" src="/kappahl-logotype_rgb_black.svg" class="navbar-icon">
        </a>
    </nav>
</div>


    

    <div>
        


<div class="page-container">
    <div class="body-container">
        
            <form action="/Account/Login" method="post">
                <input type="hidden" id="Input_ReturnUrl" name="Input.ReturnUrl" value="/connect/authorize/callback?client_id=5d5acfc6-ca3a-4f51-93b2-94509e036fdf&amp;redirect_uri…
Medium

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)2 instances1 inspected page

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Why it matters

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Recommended correction

Provide a visible and programmatic label for the form field, instead of relying solely on the placeholder text. Update the HTML to include a proper label element, such as <label for="username">Enter Email or Mobile number</label>, and ensure it is correctly associated with the input field using the 'for' attribute.

View 2 affected elements
Component · Ref DNHSEN
Affected pagehttps://id.kappahl.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D5d5acfc6-ca3a-4f51-93b2-94509e036fdf%26redirect_uri%3Dhttps%253A%252F%252Fwww.kappahl.com%252Fapi%252Foauth%252Fcallback%26response_type%3Dcode%26scope%3Dcustomers.read%2520customers.write%2520offline_access%2520openid%26code_challenge%3D3W5PGm6XevADCN1QRWt4no3DlQiqz1bzzLYSpC8-2XE%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D639238671619619883.NmMxM2EzZmMtYTA3NS00YzM3LWE5ZmQtZjlkOWQ0ZjkxNGFhMGVhZjQ3MTYtZmFiYS00OTk4LTllMGYtY2ZhYzFkMGY4Nzkw%26login_hint%3DUS%26state%3DCfDJ8CHyIOQm2N5Omb1rW3Dfh3lPeWTEpO8AxpxGuWPp74BEjx_mE4_1fNRJgRviwaGoXdE73ywyuL0bh7l9glvtErYDODyft6Px5nRy2JI-fArw0KQ00zzEN9pMKDDQGbF4j4nff3iBKzAH-ICoP1dKTa7ZIhRNrBFxqq8jueb48hp49tKy0f8Byb04y2whGlEs9KVhRb65AarvtnEPUStMxaR0cKbo3kLS8i_l7ohvlqTtvfd0ePEy78xc4HUpWh-VP8MVSty6p9FqhygaFLkiCcA-jljD2-XzmLITgq7DK-GRXR7K0NB6yIJ7ZMSnp9k6zFf-iNtDOty0i4G_oN_EKGzu2A6QZ7htphS9bGYM5TRCa5NmF8zoAHJgWrDcBnCHUrbsTf3mXJ-15KnrYuhyeuO0cbuYDoNDypazRwzUD0x4qdpW6zewGpae4EukRgcSannk33PZnGeVIjAsoEC2miB2kxjpyO9ucfdOvG-mdZB1LHTWTT0Qj1Sw1eFN3u-Ye9YTTltswd4cNlkyRO_26Yrfhg3vVCojsjSFj4XS44RZvqfiJxisHbUHBCIEet5apg%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.0.1.0
Elementinput#username
Markup
<input class="input-field" id="username" placeholder=" " autocomplete="username" type="text" name="Input.Username" value="">
Medium

Zooming and scaling must not be disabled

WCAG 1.4.4 (AA)2 instances1 inspected page

Zooming and scaling must not be disabled

Why it matters

Zooming and scaling must not be disabled

Recommended correction

To fix this issue, update the meta viewport tag to allow zooming and scaling by removing the 'maximum-scale=1' attribute or setting it to a value greater than 1. For example: <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">

View 2 affected elements
Component · Ref O2S8K6
Affected pagehttps://id.kappahl.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D5d5acfc6-ca3a-4f51-93b2-94509e036fdf%26redirect_uri%3Dhttps%253A%252F%252Fwww.kappahl.com%252Fapi%252Foauth%252Fcallback%26response_type%3Dcode%26scope%3Dcustomers.read%2520customers.write%2520offline_access%2520openid%26code_challenge%3D3W5PGm6XevADCN1QRWt4no3DlQiqz1bzzLYSpC8-2XE%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D639238671619619883.NmMxM2EzZmMtYTA3NS00YzM3LWE5ZmQtZjlkOWQ0ZjkxNGFhMGVhZjQ3MTYtZmFiYS00OTk4LTllMGYtY2ZhYzFkMGY4Nzkw%26login_hint%3DUS%26state%3DCfDJ8CHyIOQm2N5Omb1rW3Dfh3lPeWTEpO8AxpxGuWPp74BEjx_mE4_1fNRJgRviwaGoXdE73ywyuL0bh7l9glvtErYDODyft6Px5nRy2JI-fArw0KQ00zzEN9pMKDDQGbF4j4nff3iBKzAH-ICoP1dKTa7ZIhRNrBFxqq8jueb48hp49tKy0f8Byb04y2whGlEs9KVhRb65AarvtnEPUStMxaR0cKbo3kLS8i_l7ohvlqTtvfd0ePEy78xc4HUpWh-VP8MVSty6p9FqhygaFLkiCcA-jljD2-XzmLITgq7DK-GRXR7K0NB6yIJ7ZMSnp9k6zFf-iNtDOty0i4G_oN_EKGzu2A6QZ7htphS9bGYM5TRCa5NmF8zoAHJgWrDcBnCHUrbsTf3mXJ-15KnrYuhyeuO0cbuYDoNDypazRwzUD0x4qdpW6zewGpae4EukRgcSannk33PZnGeVIjAsoEC2miB2kxjpyO9ucfdOvG-mdZB1LHTWTT0Qj1Sw1eFN3u-Ye9YTTltswd4cNlkyRO_26Yrfhg3vVCojsjSFj4XS44RZvqfiJxisHbUHBCIEet5apg%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.0.1.0
Elementmeta[name="viewport"]
Markup
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no, maximum-scale=1 ">
Low

Page has no level-one heading

WCAG 1.3.1 (A)2 instances1 inspected page

The page exposes no <h1>, so its topic is not conveyed in the heading structure.

Why it matters

The page exposes no <h1>, so its topic is not conveyed in the heading structure.

Recommended correction

To fix this issue, add a level-one heading (<h1>) to the page to convey its topic and provide a clear structure for screen readers and other assistive technologies. The heading should be descriptive and concise, and should be the first heading on the page.

View 2 affected elements
Component · Ref PQSNDT
Affected pagehttps://id.kappahl.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D5d5acfc6-ca3a-4f51-93b2-94509e036fdf%26redirect_uri%3Dhttps%253A%252F%252Fwww.kappahl.com%252Fapi%252Foauth%252Fcallback%26response_type%3Dcode%26scope%3Dcustomers.read%2520customers.write%2520offline_access%2520openid%26code_challenge%3D3W5PGm6XevADCN1QRWt4no3DlQiqz1bzzLYSpC8-2XE%26code_challenge_method%3DS256%26response_mode%3Dform_post%26nonce%3D639238671619619883.NmMxM2EzZmMtYTA3NS00YzM3LWE5ZmQtZjlkOWQ0ZjkxNGFhMGVhZjQ3MTYtZmFiYS00OTk4LTllMGYtY2ZhYzFkMGY4Nzkw%26login_hint%3DUS%26state%3DCfDJ8CHyIOQm2N5Omb1rW3Dfh3lPeWTEpO8AxpxGuWPp74BEjx_mE4_1fNRJgRviwaGoXdE73ywyuL0bh7l9glvtErYDODyft6Px5nRy2JI-fArw0KQ00zzEN9pMKDDQGbF4j4nff3iBKzAH-ICoP1dKTa7ZIhRNrBFxqq8jueb48hp49tKy0f8Byb04y2whGlEs9KVhRb65AarvtnEPUStMxaR0cKbo3kLS8i_l7ohvlqTtvfd0ePEy78xc4HUpWh-VP8MVSty6p9FqhygaFLkiCcA-jljD2-XzmLITgq7DK-GRXR7K0NB6yIJ7ZMSnp9k6zFf-iNtDOty0i4G_oN_EKGzu2A6QZ7htphS9bGYM5TRCa5NmF8zoAHJgWrDcBnCHUrbsTf3mXJ-15KnrYuhyeuO0cbuYDoNDypazRwzUD0x4qdpW6zewGpae4EukRgcSannk33PZnGeVIjAsoEC2miB2kxjpyO9ucfdOvG-mdZB1LHTWTT0Qj1Sw1eFN3u-Ye9YTTltswd4cNlkyRO_26Yrfhg3vVCojsjSFj4XS44RZvqfiJxisHbUHBCIEet5apg%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.0.1.0
Elementhtml > body
Accessible nameLog in Enter Email or Mobile number Enter your password Log in Forgot password? or log in with Apple Become member Back to Kappahl.com
Markup
<body>
    
<div class="nav-page">
    <nav class="navbar navbar-expand-lg">

        <a href="https://kappahl.com" class="navbar-brand">
            <img alt="KappAhl logo" src="/kappahl-logotype_rgb_black.svg" class="navbar-icon">
        </a>
    </nav>
</div>


    

    <div>
        


<div class="page-container">
    <div class="body-container">
        
            <form action="/Account/Login" method="post">
                <input type="hidden" id="Input_ReturnUrl" name="Input.ReturnUrl" value="/connect/authorize/callback?client_id=5d5acfc6-ca3a-4f51-93b2-94509e036fdf&amp;redirect_uri…

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.