Public accessibility assessment

Accessibility issues detected on papallou.com

Evolize inspected 5 public pages on papallou.com and detected 21 automatically identifiable accessibility findings.

21Findings detected
6WCAG criteria affected
5Pages inspected
13 Aug 2026Assessment date

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

Most widespread issueHidden elements can still receive keyboard focusDetected on 5 inspected pages
Most affected page/14 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)9 detected findings

Is papallou.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 papallou.com and detected 21 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 5 inspected pages. The most affected inspected page was "/", where 14 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

    Links lack accessible text

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

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add alt text to the image inside the link, or provide another way for screen readers to announce the link's purpose, like using aria-label or wrapping the image in a span with text.

    View technical evidence →
  2. Critical

    Buttons have no accessible name

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

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

    Recommended action

    Add an accessible name to the button by including text within the button element or using the aria-label attribute to provide a descriptive label.

    View technical evidence →
  3. Critical

    Buttons have no accessible name

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

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

    Recommended action

    Add an accessible name to the button, either by including visible text within the button element or by using the aria-label or aria-labelledby attributes to provide a text description of the button's purpose.

    View technical evidence →
  4. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 39 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

    Ensure that hidden interactive elements are removed from the tab order or made visible when they receive focus. This can be achieved by setting the 'tabindex' attribute to '-1' or by adjusting the element's visibility styles when it receives focus.

    View technical evidence →
  5. High

    Text has insufficient colour contrast

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

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

    Recommended action

    Adjust the color of the text or its background to ensure the contrast ratio meets the minimum requirements. This can be achieved by using a color contrast analyzer tool to find suitable colors that meet the WCAG 2.1 guidelines for contrast.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA955 / 5
4.1.2Name, Role, ValueA455 / 5
1.1.1Non-text ContentA355 / 5
2.4.3Focus OrderA355 / 5
2.1.1KeyboardA155 / 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)2 instances2 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 an accessible name to the button by including text within the button element or using the aria-label attribute to provide a descriptive label.

View 2 affected elements
Component · Ref VFXOGY
Affected pagehttps://papallou.com/collections/spring-2026/products/boys-jacket-navy
Element.starting-slide > .product-image-main.product-image-main--7778081308715 > .image-wrap > .js-photoswipe__zoom.product__photo-zoom.btn--body
Accessible nameClose (esc)
Markup
<button type="button" class="btn btn--body btn--circle js-photoswipe__zoom product__photo-zoom">
Component · Ref WP0HUE
Affected pagehttps://papallou.com/products/tricycle-basket-mouse
Element.js-photoswipe__zoom
Accessible nameClose (esc)
Markup
<button type="button" class="btn btn--body btn--circle js-photoswipe__zoom product__photo-zoom">
High

ARIA attributes have invalid values

WCAG 4.1.2 (A)5 instances5 inspected pages

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

Verify that all ARIA attributes have valid values and reference existing ids. Check the 'aria-controls' attribute on the navigation links and ensure it references a valid id.

View 5 affected elements
Component · Ref EOXVRK
Affected pagehttps://papallou.com/
Element.js-drawer-open-cart
Accessible nameCart
Markup
<a href="/cart" class="site-nav__link site-nav__link--icon js-drawer-open-cart" aria-controls="CartDrawer" data-icon="bag-minimal">
Affected pages/ /pages/contact /collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse /cart
High

Text has insufficient colour contrast

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

Adjust the color of the text or its background to meet the minimum contrast ratio of 4.5:1 for normal text, as per WCAG 2.1 guidelines. This can be achieved by using a color contrast analyzer tool to find suitable colors.

View 39 affected elements
Component · Ref JW0NHT
Affected pagehttps://papallou.com/
Element.h3
Accessible nameLet’s be friends!
Markup
<p class="h3">Let’s be friends!</p>
Affected pages/ /pages/contact /collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse /cart
Component · Ref 77T8ZQ
Affected pagehttps://papallou.com/
Element#qab_message
Accessible nameSUMMER SALE 🐚 50% OFF SS26 (*final sale)
Markup
<span id="qab_message" style="color: inherit; text-shadow: none; font-size: 16px;">SUMMER SALE 🐚 50% OFF SS26 (*final sale)</span>
Affected pages/ /pages/contact /collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse /cart
Component · Ref N5ITGZ
Affected pagehttps://papallou.com/
Element.text-section > .rte
Accessible namesubscribe and receive 10% off in your inbox!
Markup
<div class="rte">subscribe and receive <br>10% off in your inbox!</div>
Affected pages/ /pages/contact /collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse /cart
Component · Ref SQGBDK
Affected pagehttps://papallou.com/
Element#Email-
Markup
<input type="email" value="" placeholder="your email" name="contact[email]" id="Email-" class="input-group-field newsletter__input" autocorrect="off" autocapitalize="off">
Affected pages/ /pages/contact /collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse /cart
Component · Ref FPGGLS
Affected pagehttps://papallou.com/products/tricycle-basket-mouse
Elementa[href="/collections/vendors?q=Maileg"]
Accessible nameMaileg
Markup
<a href="/collections/vendors?q=Maileg" title="Maileg">Maileg</a>
Affected pages/collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse
Component · Ref QPYR7N
Affected pagehttps://papallou.com/collections/spring-2026/products/boys-jacket-navy
Elementdiv[data-value="2-3"] > .variant__button-label.disabled
Accessible name2-3
Markup
<label for="ProductSelect-7778081308715-option-size-2-3" class="variant__button-label disabled">2-3</label>
Component · Ref 45OB0R
Affected pagehttps://papallou.com/
Element.btn[href$="spring-2026"]
Accessible nameSS26; Held by the Sea
Markup
<a href="/collections/spring-2026" class="btn">
Component · Ref 1K2CW7
Affected pagehttps://papallou.com/collections/spring-2026/products/boys-jacket-navy
Element.return-link
Accessible nameBack to Spring 2026
Markup
<a href="/collections/spring-2026" class="btn btn--small return-link">
      <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon--wide icon-arrow-left" viewBox="0 0 50 15"><path d="M50 5.38v4.25H15V15L0 7.5 15 0v5.38z"></path></svg> Back to Spring 2026
    </a>
Component · Ref JVAHZN
Affected pagehttps://papallou.com/pages/contact
Element#contact-page-contact-template-0 > .btn[type="submit"]
Accessible nameSend
Markup
<button type="submit" class="btn">
          Send
        </button>
High

Hidden elements can still receive keyboard focus

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

Ensure that hidden interactive elements are removed from the tab order or made visible when they receive focus. This can be achieved by setting the 'tabindex' attribute to '-1' or by adjusting the element's visibility styles when it receives focus.

View 50 affected elements
Component · Ref RJ6G7A
Affected pagehttps://papallou.com/
Elementdiv#NavDrawer > div:nth-of-type(1) > div:nth-of-type(1) > div:nth-of-type(1) > div:nth-of-type(2) > button
Accessible nameClose menu
Markup
<button type="button" class="drawer__close-button js-drawer-close">
            <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon-close" viewBox="0 0 64 64"><path d="M19 17.61l27.12 27.13m0-27.12L19 44.74"></path></svg>
            <span class="icon__fallback-text">Close menu</span>
          </button>
Affected pages/ /pages/contact /collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse /cart
Component · Ref V63012
Affected pagehttps://papallou.com/
Elementform#HeaderSearchForm > input:nth-of-type(2)
Accessible nameSearch
Markup
<input type="search" name="q" value="" placeholder="Search" class="site-header__search-input" aria-label="Search">
Affected pages/ /pages/contact /collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse /cart
Component · Ref ZYR9AY
Affected pagehttps://papallou.com/
Elementdiv:nth-of-type(1) > div:nth-of-type(1) > div:nth-of-type(1) > div:nth-of-type(1) > h1 > a:nth-of-type(2)
Accessible namePapallou
Markup
<a href="/" itemprop="url" class="site-header__logo-link logo--inverted">
          <img class="small--hide" src="//papallou.com/cdn/shop/files/papallou_wmark_rough_2x_22614a2a-fa75-45ae-8e2b-a1be8d28e8c7_240x.png?v=1613182255" srcset="//papallou.com/cdn/shop/files/papallou_wmark_rough_2x_22614a2a-fa75-45ae-8e2b-a1be8d28e8c7_240x.png?v=1613182255 1x, //papallou.com/cdn/shop/files/[email removed]?v=1613182255 2x" alt="Papallou" itemprop="logo">
          <img class="medium-up--hide" src="//papallou.com/cdn/shop/files/papallou_wmark_rough_…
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)5 instances5 inspected pages

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 focusable semantics or a tabindex to the interactive element, ensuring it can receive keyboard focus. Consider using a native HTML button element or adding a tabindex attribute to the div element.

View 5 affected elements
Component · Ref N4MFAB
Affected pagehttps://papallou.com/
Elementdiv#qab_background
Accessible namePromotional banner
Roleregion
Markup
<div id="qab_background" role="region" aria-label="Promotional banner" style="opacity: 1; margin: 0px; padding: 0px; left: 0px; height: auto; width: 100%; z-index: 29; position: relative; overflow: hidden; cursor: pointer;" onclick="qab_button_on_click(event)" ;="">
                <div id="qab_bar" style="text-align: center; margin: 0px; padding: 10px 0px; left: 0px; height: auto; width: 100%; box-sizing: border-box; border: none; background-color: rgb(211, 217, 221); color: rgb(255, 255, 255); font-size: 16px; line-height: 20px; font-family: Verdana;">
                  <div id="qab_content"…
Affected pages/ /pages/contact /collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse /cart
High

ARIA hidden element must not be focusable or contain focusable elements

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

Remove or disable any focusable elements inside the aria-hidden container, or remove the aria-hidden attribute if the container should be accessible.

View 2 affected elements
Component · Ref 57XZEF
Affected pagehttps://papallou.com/products/tricycle-basket-mouse
Element.visually-invisible
Accessible nameQuick view Tricycle basket, Mouse $6.00
Markup
<div class="grid grid--uniform visually-invisible" aria-hidden="true">
Affected pages/collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse
High

Images lack text alternatives

WCAG 1.1.1 (A)3 instances1 inspected page

Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.

Why it matters

Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.

Recommended correction

Add an alt attribute to the image with a brief description of the image content, such as alt="Product image" or alt="Image of a shoe".

View 3 affected elements
Component · Ref CTMNAU
Affected pagehttps://papallou.com/
Element.small--one-half.medium-up--one-third.collection-collage__item:nth-child(1) > .product-look-section > a > .featured_img > img
Markup
<img src="//papallou.com/cdn/shop/files/AF1EE9F1-9E4A-4971-A0A3-6AB0239D3FDC.jpg?v=1773341161">
Component · Ref 1G1EKN
Affected pagehttps://papallou.com/
Elementa[href$="boys-jacket-white"] > .featured_img > img
Markup
<img src="//papallou.com/cdn/shop/files/5E989A65-5DC9-460D-BE65-4F0910520FFC.jpg?v=1773341830">
Low

Low-quality alternative text

WCAG 1.1.1 (A)39 instances5 inspected pages

Alt text looks like a filename, a generic word ("image", "photo"), or is duplicated across unrelated images — it likely does not describe the content.

Why it matters

Alt text looks like a filename, a generic word ("image", "photo"), or is duplicated across unrelated images — it likely does not describe the content.

Recommended correction

Update the alt text for each image to provide a unique and descriptive text that accurately represents the content of the image.

View 39 affected elements
Component · Ref EN74QL
Affected pagehttps://papallou.com/
Elementdiv > div > div:nth-of-type(1) > div > a > img
Markup
<img src="//papallou.com/cdn/shop/files/[email removed]?v=1690910228" alt="Papallou">
Affected pages/ /pages/contact /collections/spring-2026/products/boys-jacket-navy /products/tricycle-basket-mouse /cart

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.