Scan results for www.xandres.com/be_en

Accessible

Congratulations! Our scan indicates that your webpage is accessible. We’re thrilled you chose to be inclusive and comply with legislation.

#
Element
Relevant
Successes
Failures
Score
1
Elements that act as buttons but use non-button tags (e.g., span, div, a) should include a role="button" attribute.
Yes
7
5
58

Code snapshots of successful elements

  • 1 
                <button id="CybotCookiebotDialogBodyButtonDecline" class="CybotCookiebotDialogBodyButton" tabindex="0" lang="nl">Weigeren</button>
  • 2 
                <button id="CybotCookiebotDialogBodyLevelButtonCustomize" class="CybotCookiebotDialogBodyButton" tabindex="0" lang="nl">Aanpassen<div class="CybotCookiebotDialogArrow"></div></button>
  • 3 
                <button id="CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll" class="CybotCookiebotDialogBodyButton" tabindex="0" lang="nl">Alles toestaan</button>
  • 4 
                <div aria-label="Previous post" class="bzfy-c-carousel-control" role="button" tabindex="0" style="background: rgb(51, 51, 51); user-select: none;"><div aria-hidden="true" class="bzfy-icon bzfy-icon--arrow-left"><svg height="32" viewBox="0 0 512 512" ...
  • 5 
                <div aria-label="Next post" class="bzfy-c-carousel-control bzfy-c-carousel-control--right" role="button" tabindex="0" style="background: rgb(51, 51, 51); user-select: none;"><div aria-hidden="true" class="bzfy-icon bzfy-icon--arrow-right"><svg height...
  • 6 
                <span class="countrylanguage" tabindex="0" role="button">Belgium - English</span>
  • 7 
                <button class="action subscribe primary" type="submit" aria-label="Subscribe">
                            <span>Subscribe</span>
                        </button>

Code snapshots of failed elements

  • 1 
                <a id="contentarea" tabindex="-1"></a>
  • 2 
                <div class="bzfy-c-carousel-slide-wrap bzfy-c-carousel-slide-wrap--clickable" id="post-0"><div style="padding-left: 0.5px; padding-right: 0.5px;"><div aria-haspopup="dialog" aria-hidden="false" aria-label="Media thumbnail 1 of 29, opens dialog with s...
  • 3 
                <div class="bzfy-c-carousel-slide-wrap bzfy-c-carousel-slide-wrap--clickable" id="post-1"><div style="padding-left: 0.5px; padding-right: 0.5px;"><div aria-haspopup="dialog" aria-hidden="true" aria-label="Media thumbnail 2 of 29, opens dialog with so...
  • 4 
                <div class="bzfy-c-carousel-slide-wrap bzfy-c-carousel-slide-wrap--clickable" id="post-2"><div style="padding-left: 0.5px; padding-right: 0.5px;"><div aria-haspopup="dialog" aria-hidden="true" aria-label="Media thumbnail 3 of 29, opens dialog with so...
  • 5 
                <div class="bzfy-c-carousel-slide-wrap bzfy-c-carousel-slide-wrap--clickable" id="post-3"><div style="padding-left: 0.5px; padding-right: 0.5px;"><div aria-haspopup="dialog" aria-hidden="true" aria-label="Media thumbnail 4 of 29, opens dialog with so...
#
Element
Relevant
Successes
Failures
Score
2
Buttons should include text explaining their functionality, and if icons are used as buttons, a screen-reader only text or an "aria-label" attribute should be used for that description.
Yes
10
0
100

Code snapshots of successful elements

  • 1 
                <button id="CybotCookiebotDialogBodyButtonDecline" class="CybotCookiebotDialogBodyButton" tabindex="0" lang="nl">Weigeren</button>
  • 2 
                <button id="CybotCookiebotDialogBodyLevelButtonCustomize" class="CybotCookiebotDialogBodyButton" tabindex="0" lang="nl">Aanpassen<div class="CybotCookiebotDialogArrow"></div></button>
  • 3 
                <button id="CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll" class="CybotCookiebotDialogBodyButton" tabindex="0" lang="nl">Alles toestaan</button>
  • 4 
                <button type="submit" class="action search" disabled="">
                    <span>Search</span>
                </button>
  • 5 
                <button type="button" class="pagebuilder-banner-button pagebuilder-button-secondary" data-element="button" data-pb-style="TPGHGI6">SHOP PRE-SALE</button>
  • 6 
                <div aria-haspopup="dialog" aria-hidden="false" aria-label="Media thumbnail 1 of 29, opens dialog with social media content and featured product list." class="bzfy-c-carousel-post bzfy-c-carousel-post--minimalistic" data-post-key="958627bc-180a-4347-...
  • 7 
                <div aria-label="Previous post" class="bzfy-c-carousel-control" role="button" tabindex="0" style="background: rgb(51, 51, 51); user-select: none;"><div aria-hidden="true" class="bzfy-icon bzfy-icon--arrow-left"><svg height="32" viewBox="0 0 512 512" ...
  • 8 
                <div aria-label="Next post" class="bzfy-c-carousel-control bzfy-c-carousel-control--right" role="button" tabindex="0" style="background: rgb(51, 51, 51); user-select: none;"><div aria-hidden="true" class="bzfy-icon bzfy-icon--arrow-right"><svg height...
  • 9 
                <span class="countrylanguage" tabindex="0" role="button">Belgium - English</span>
  • 10 
                <button class="action subscribe primary" type="submit" aria-label="Subscribe">
                            <span>Subscribe</span>
                        </button>
#
Element
Relevant
Successes
Failures
Score
3
Links should include text that sets expectations about the page they lead to. If empty links are used as layout wrapping elements, provide a description using screen-reader only text or an "aria-label" attribute.
Yes
67
0
100

Code snapshots of successful elements

  • 1 
                <a class="action skip contentarea" href="#contentarea" >
    <span>
        Skip to Content    </span>
</a>
  • 2 
                <a class="logo" href="https://www.xandres.com/be_en/" aria-label="Visit the Homepage of Xandres">
    <img src="https://www.xandres.com/media/logo/default/Xandres_workmark_LOGO.svg" alt="Xandres" width="300" height="30">
</a>
  • 3 
                <a href="https://www.xandres.com/be_en/xandres/sale" aria-expanded="false" aria-haspopup="true">
                        <span>PRE-SALE</span>
                    </a>
  • 4 
                <a href="https://www.xandres.com/be_en/xandres/new-collection" aria-expanded="false" aria-haspopup="true">
                        <span>NEW IN</span>
                    </a>
  • 5 
                <a href="https://www.xandres.com/be_en/xandres" aria-expanded="false" aria-haspopup="true">
                        <span>SHOP</span>
                    </a>
  • 6 
                <a href="https://www.xandres.com/be_en/inspiration" aria-expanded="false" aria-haspopup="true">
                        <span>INSPIRATION</span>
                    </a>
  • 7 
                <a href="https://www.xandres.com/be_en/history" aria-expanded="false" aria-haspopup="true">
                        <span>ABOUT US</span>
                    </a>
  • 8 
                <a class="action showcart" href="https://www.xandres.com/be_en/checkout/cart/" data-bind="scope: 'minicart_content'">
        <span class="text">My Cart</span>
        <span class="counter qty empty" data-bind="css: { empty: !!getCartParam('summary_c...
  • 9 
                <a href="https://www.xandres.com/be_en/guestwishlist" class="action wishlist showwishlist" aria-label="Wishlist">
        <span class="counter qty empty" data-bind="css: { empty: getWishlistCount() == 0 }">
            <span class="counter-number">
 ...
  • 10 
                <a class="action customer showcustomer" aria-label="Customer Account" href="https://www.xandres.com/be_en/customer/account/index/"><span>Customer Account</span></a>
#
Element
Relevant
Successes
Failures
Score
4
Links that open in a new tab or a new window should either have an "aria-label" attribute or a screen-reader only element explaining to screen-readers that this opens in a new tab.
Yes
0
12
0

Code snapshots of failed elements

  • 1 
                <a tabindex="0" href="https://www.instagram.com/xandres_belgium/" target="_blank" rel="noopener">@xandres_belgium</a>
  • 2 
                <a tabindex="0" href="https://recognition.ecovadis.com/hPPWG6thHkKmEt3KAaq67w" target="_blank" rel="noopener"><img style="width: 100px; height: 100px;" src="https://www.xandres.com/media/wysiwyg/csr.webp" alt="" width="80" height="80"></a>
  • 3 
                <a tabindex="0" href="https://trustmark.becom.digital/nl/Xandres_4065734" target="_blank" rel="noopener"><img style="margin-top: 30px; margin-bottom: 30px; width: 125px; height: 35px;" src="https://www.xandres.com/media/wysiwyg/Becom_badge_green_exte...
  • 4 
                <a href="https://www.xandres.com/be_en/privacy/" aria-label="Privacy Policy Aria" target="_blank" rel="noopener noreferrer">Privacy Policy</a>
  • 5 
                <a href="https://www.xandres.com/be_en/cookies/" aria-label="Cookie Policy Aria" target="_blank" rel="noopener noreferrer">Cookie Policy </a>
  • 6 
                <a href="https://www.xandres.com/be_en/terms-and-conditions/" aria-label="Terms of Service Aria" target="_blank" rel="noopener noreferrer">terms and conditions</a>
  • 7 
                <a href="https://policies.google.com/privacy" aria-label="Privacy Policy Aria" target="_blank" rel="noopener noreferrer">Privacy Policy</a>
  • 8 
                <a href="https://policies.google.com/terms" aria-label="Terms of Service Aria" target="_blank" rel="noopener noreferrer">terms and conditions</a>
  • 9 
                <a href="https://www.facebook.com/xandresbelgium/" class="social-icon facebook" target="_blank" style="text-align: center; margin-right: 16px;" aria-label="Facebook Xandres Belgium" rel="noopener noreferrer"></a>
  • 10 
                <a href="https://www.instagram.com/xandres_belgium/" class="social-icon instagram" target="_blank" style="text-align: center; margin-left: 16px; margin-right: 16px;" aria-label="Instagram Xandres Belgium" rel="noopener noreferrer"></a>
#
Element
Relevant
Successes
Failures
Score
5
An H1 heading provides information to screen-reader users about the main topic of the page. Each page should have exactly one H1 heading.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <div id="CybotCookiebotDialogBodyContentTitle" class="CybotCookiebotDialogBodyContentHeading" lang="nl" role="heading" aria-level="1">Deze website maakt gebruik van cookies</div>
#
Element
Relevant
Successes
Failures
Score
6
HTML heading elements (h1-h6) should contain text content. If they include images or links, those elements must provide alternative text or screen-reader-only text.
No
0
0
#
Element
Relevant
Successes
Failures
Score
7
Elements that visually function as headings but are not coded with a heading tag should include a role="heading" attribute or be updated to use the correct heading tag
Yes
1
17
6

Code snapshots of successful elements

  • 1 
                <span id="modal-title-29" class="modal-title" data-role="title" role="heading">
            
            Where do you want it delivered?
            

            
        </span>

Code snapshots of failed elements

  • 1 
                <span style="font-size: 86px; line-height: 86px; color: #ffffff;"><em><span style="font-family: freigeist;">pre-<strong>sale</strong></span></em></span>
  • 2 
                <em><span style="font-family: freigeist;">pre-<strong>sale</strong></span></em>
  • 3 
                <span style="font-family: freigeist;">pre-<strong>sale</strong></span>
  • 4 
                <strong>sale</strong>
  • 5 
                <span style="font-size: 40px; line-height: 40px; color: #ffffff;"><span style="font-family: freigeist; font-weight: 400;">NEW ARRIVALS</span></span>
  • 6 
                <span style="font-family: freigeist; font-weight: 400;">NEW ARRIVALS</span>
  • 7 
                <span style="font-size: 20px;"><span style="text-decoration: underline;"><span style="line-height: 70px;"><span style="font-family: freigeist;">DISCOVER</span></span></span></span>
  • 8 
                <span style="text-decoration: underline;"><span style="line-height: 70px;"><span style="font-family: freigeist;">DISCOVER</span></span></span>
  • 9 
                <span style="line-height: 70px;"><span style="font-family: freigeist;">DISCOVER</span></span>
  • 10 
                <span style="font-family: freigeist;">DISCOVER</span>
#
Element
Relevant
Successes
Failures
Score
8
Heading levels should not be skipped and must follow a consistent hierarchy. For example, you should not use h2 and h4 headings without including an h3 in between.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
9
Interactive elements such as links, buttons and form fields should all be navigable using the keyboard by either using a focusable element (a, button, input, etc.) or including the "tabindex" attribute that equals to "0".
Yes
4
0
100

Code snapshots of successful elements

  • 1 
                <div aria-haspopup="dialog" aria-hidden="false" aria-label="Media thumbnail 1 of 29, opens dialog with social media content and featured product list." class="bzfy-c-carousel-post bzfy-c-carousel-post--minimalistic" data-post-key="958627bc-180a-4347-...
  • 2 
                <div aria-label="Previous post" class="bzfy-c-carousel-control" role="button" tabindex="0" style="background: rgb(51, 51, 51); user-select: none;"><div aria-hidden="true" class="bzfy-icon bzfy-icon--arrow-left"><svg height="32" viewBox="0 0 512 512" ...
  • 3 
                <div aria-label="Next post" class="bzfy-c-carousel-control bzfy-c-carousel-control--right" role="button" tabindex="0" style="background: rgb(51, 51, 51); user-select: none;"><div aria-hidden="true" class="bzfy-icon bzfy-icon--arrow-right"><svg height...
  • 4 
                <span class="countrylanguage" tabindex="0" role="button">Belgium - English</span>
#
Element
Relevant
Successes
Failures
Score
10
Interactive elements that can be navigated using the keyboard should be surrounded by a visual outline whenever they are focused.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
11
Active popups should include aria-modal="true" and role="dialog" attributes to help screen-reader users navigate them effectively.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <div id="CybotCookiebotDialog" name="CybotCookiebotDialog" role="dialog" aria-modal="true" aria-labelledby="CybotCookiebotDialogBodyContentTitle" tabindex="-1" lang="nl" dir="ltr" ng-non-bindable="" style="display: flex;" data-template="overlay" clas...
#
Element
Relevant
Successes
Failures
Score
12
Each page should include hidden skip links that allow users (via keyboard or screen reader) to bypass certain blocks and navigate directly to main landmarks like the main content, menu, or footer.
Yes
-
Fail
0

Code snapshots of failed elements

  • 1 
                <a class="nav-sections-item-switch" data-toggle="switch" href="#store.menu" >
                        Menu                    </a>
  • 2 
                <a href="https://www.xandres.com/be_en/history#fitting" >
                                                                                    <span >Fitting &amp; Craftwomenship</span>
                                                                 ...
  • 3 
                <a href="https://www.xandres.com/be_en/history#innovation" >
                                                                                    <span >Innovation</span>
                                                                                ...
  • 4 
                <a href="https://www.xandres.com/be_en/history#fashion" >
                                                                                    <span >Fashion competence</span>
                                                                           ...
  • 5 
                <a href="https://www.xandres.com/be_en/history#fitting" >
                                                        <span >Fitting &amp; Craftwomenship</span>
                                                    </a>
  • 6 
                <a href="https://www.xandres.com/be_en/history#innovation" >
                                                        <span >Innovation</span>
                                                    </a>
  • 7 
                <a href="https://www.xandres.com/be_en/history#fashion" >
                                                        <span >Fashion competence</span>
                                                    </a>
  • 8 
                <a style="text-decoration: none;" tabindex="0" href="https://www.xandres.com/be_en/contact#customer" >Contact us</a>
  • 9 
                <a style="text-decoration: none;" tabindex="0" href="https://www.xandres.com/be_en/terms-and-conditions#complaints" >Complaints</a>
  • 10 
                <a style="text-decoration: none;" tabindex="0" href="https://www.xandres.com/be_en/terms-and-conditions#guarantee" >Guarantee</a>
#
Element
Relevant
Successes
Failures
Score
13
Elements hidden using CSS (e.g., opacity, height, text-indent, off-canvas) should include an "aria-hidden" attribute set to "true" when hidden and dynamically updated to "false" when they become visible.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
14
Elements hidden using CSS (e.g., opacity, height, text-indent, off-canvas) should have a tabindex attribute set to less than 0 and be dynamically updated to 0 when they become visible.
No
0
0
#
Element
Relevant
Successes
Failures
Score
15
Menus should be built using the HTML5 "nav" element or include a "role" attribute set to "menu" or "navigation" to indicate a navigation landmark for screen readers.
No
0
0
#
Element
Relevant
Successes
Failures
Score
16
Menu items that have a dropdown should include an aria-haspopup="true" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
17
Menu items that have a dropdown should include an "aria-expanded" attribute set to "false" by default, which changes to "true" when the dropdown is opened, and back to "false" when closed.
No
0
0
#
Element
Relevant
Successes
Failures
Score
18
Images should have an alternative text description that describes both the objects and the embedded text that the image contains, using the "alt" attribute.
Yes
3
3
50

Code snapshots of successful elements

  • 1 
                <img id="CybotCookiebotDialogPoweredbyImage" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAO4AAAAuCAYAAAAvBiWWAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAABEsSURBVHhe7ZwLsFxFmccnCeDukmSYO6e7zzkzuRdCJO7VFfBGQd0lykNESl1FrV...
  • 2 
                <img src="https://www.xandres.com/media/logo/default/Xandres_workmark_LOGO.svg" alt="Xandres" width="300" height="30">
  • 3 
                <img alt="Photo by justinevanruymbeke published at 19 May 2025" class="bzfy-o-image" loading="lazy" sizes="783.551724137931px" srcset="https://cdn.flbx.io/image/eyJrZXkiOiJhSFIwY0hNNkx5OTNkM2N1YVc1emRHRm5jbUZ0TG1OdmJTOXdMMFJLTUY5VVpteE5URkkxTHc9PS80I...

Code snapshots of failed elements

  • 1 
                <div class="pagebuilder-banner-wrapper background-image-685ea306aa413" role="img" data-background-images="{\&quot;desktop_image\&quot;:\&quot;https://www.xandres.com/media/wysiwyg/Beeld_Header_6.jpg\&quot;}" data-background-type="image" data-video-lo...
  • 2 
                <div class="pagebuilder-banner-wrapper background-image-685ea306aa49b" role="img" data-background-images="{\&quot;desktop_image\&quot;:\&quot;https://www.xandres.com/media/wysiwyg/FW25XADC04_5_4.jpg\&quot;}" data-background-type="image" data-video-lo...
  • 3 
                <div class="pagebuilder-banner-wrapper background-image-685ea306aa4a6" role="img" data-background-images="{\&quot;desktop_image\&quot;:\&quot;https://www.xandres.com/media/wysiwyg/SS25XADCC04_4_6.jpg\&quot;}" data-background-type="image" data-video-l...
#
Element
Relevant
Successes
Failures
Score
19
Background images that are not just for decoration purposes should have the same treatment as standard images. They should include a role="img" attribute and an alternative text description using an "aria-label" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
20
Font icons, SVGs, or images used as spacers, decorations, or when their purpose is already described by other content, should include a role="presentation" or role="none" attribute.
Yes
12
0
100

Code snapshots of successful elements

  • 1 
                <svg aria-hidden="true" focusable="false" height="100%" viewBox="0 0 24 24" width="100%" ><g fill="#000000" ><path d="M20 6h2a2 2 0 012 2v14a2 2 0 01-2 2H8a2 2 0 01-2-2v-2h12a2 2 0 002-2V6zM2 0h14a2 2 0 012 2v14a2 2 0 01-2 2H2a2 2 0 01-2-2V2a2 2 0 01...
  • 2 
                <svg height="32" viewBox="0 0 512 512" width="32" ><polygon fill="#fff" points="352,115.4 331.3,96 160,256 331.3,416 352,396.7 201.5,256 " ></polygon></svg>
  • 3 
                <svg height="32" viewBox="0 0 512 512" width="32" ><polygon fill="#fff" points="160,115.4 180.7,96 352,256 180.7,416 160,396.7 310.5,256 " ></polygon></svg>
  • 4 
                <img src="https://www.xandres.com/media/wysiwyg/paymentmethod/bancontact.svg" height="15" width="20" alt="" style="vertical-align:middle; margin-left:10px" loading="lazy">
  • 5 
                <img src="https://www.xandres.com/media/wysiwyg/paymentmethod/paypal.svg" height="15" width="20" alt="" style="vertical-align:middle; margin-left:10px" loading="lazy">
  • 6 
                <img src="https://www.xandres.com/media/wysiwyg/paymentmethod/ideal.svg" height="15" width="20" alt="" style="vertical-align:middle; margin-left:10px" loading="lazy">
  • 7 
                <img src="https://www.xandres.com/media/wysiwyg/paymentmethod/Mastercard.svg" height="15" width="20" alt="" style="vertical-align:middle; margin-left:10px" loading="lazy">
  • 8 
                <img src="https://www.xandres.com/media/wysiwyg/paymentmethod/visa.svg" height="15" width="20" alt="" style="vertical-align:middle; margin-left:10px" loading="lazy">
#
Element
Relevant
Successes
Failures
Score
21
Figure elements used to display images should have a role="none" attribute, and the image itself should provide a description using the "alt" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
22
Each "area" element within a map tag should have an "alt" attribute that provides an alternative text description, similar to standard images.
No
0
0
#
Element
Relevant
Successes
Failures
Score
23
Small or hidden tracking pixel images (used for analytics or marketing) should include a role="none" or role="presentation" attribute to exclude them from screen-readers.
No
0
0
#
Element
Relevant
Successes
Failures
Score
24
Form fields should include either an "aria-label" attribute or an associated "label" element to describe the field's purpose (e.g., email, phone, name).
Yes
2
0
100

Code snapshots of successful elements

  • 1 
                <input id="minisearch-input-top-search" type="text" name="q" value="" placeholder="Search" class="input-text" maxlength="128" role="combobox" aria-haspopup="false" aria-autocomplete="both" aria-expanded="false" autocomplete="off" data-block="autocomp...
  • 2 
                <input name="email" type="email" id="newsletter" placeholder="Enter your email address" data-validate="{required:true, 'validate-email':true}" aria-required="true">
#
Element
Relevant
Successes
Failures
Score
25
Form elements must have unique IDs to ensure that their corresponding labels provide accurate information.
No
0
0
#
Element
Relevant
Successes
Failures
Score
26
Required form fields should include aria-required="true" to inform screen-reader users of the field's validation.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <input name="email" type="email" id="newsletter" placeholder="Enter your email address" data-validate="{required:true, 'validate-email':true}" aria-required="true">
#
Element
Relevant
Successes
Failures
Score
27
aria-describedby and aria-labelledby attributes should reference the ID of an element that either has a text description or an "aria-label" attribute.
Yes
19
0
100

Code snapshots of successful elements

  • 1 
                <div tabindex="-1" role="dialog" class="ui-dialog ui-corner-all ui-widget ui-widget-content ui-front mage-dropdown-dialog" aria-describedby="ui-id-1" style="display: none;" ><div class="block block-minicart ui-dialog-content ui-widget-content" data-r...
  • 2 
                <div tabindex="-1" role="dialog" class="ui-dialog ui-corner-all ui-widget ui-widget-content ui-front mage-dropdown-dialog" aria-describedby="ui-id-3" style="display: none;" ><div class="block block-customer ui-dialog-content ui-widget-content" data-r...
  • 3 
                <aside role="dialog" class="modal-popup phpro-cart-modal
               
               _inner-scroll" aria-labelledby="modal-title-24" aria-describedby="modal-content-24" data-role="modal" data-type="popup" tabindex="0" >
<div data-role="focusable-s...
  • 4 
                <aside role="dialog" class="modal-popup phpro-store-redirect-popup-two _inner-scroll _show" aria-labelledby="modal-title-29" aria-describedby="modal-content-29" data-role="modal" data-type="popup" tabindex="0" style="z-index: 902;">
<div data-role="f...
  • 5 
                <div id="CybotCookiebotDialog" name="CybotCookiebotDialog" role="dialog" aria-modal="true" aria-labelledby="CybotCookiebotDialogBodyContentTitle" tabindex="-1" lang="nl" dir="ltr" ng-non-bindable="" style="display: flex;" data-template="overlay" clas...
  • 6 
                <div id="CybotCookiebotDialogBody" class="CybotCookiebotDialogTabPanel" role="tabpanel" aria-labelledby="CybotCookiebotDialogNavDeclaration" lang="nl" ><div class="CybotCookiebotScrollContainer" ><div id="CybotCookiebotDialogBodyContent" class="Cybot...
  • 7 
                <div id="CybotCookiebotDialogTabContentDetails" class="CybotCookiebotDialogTabPanel CybotCookiebotDialogHide CybotCookiebotScrollArea" role="tabpanel" aria-labelledby="CybotCookiebotDialogNavDetails" lang="nl" ><div class="CybotCookiebotFader" style=...
  • 8 
                <div id="CybotCookiebotDialogDetailBodyContentCookieTabsNecessary" class="CollapseCard CybotCookiebotDialogHide" aria-labelledby="CybotCookiebotDialogDetailBodyContentCookieContainerNecessaryCard" ><div class="CybotCookiebotDialogDetailBodyContentCoo...
  • 9 
                <div id="CybotCookiebotDialogDetailBodyContentCookieTabsPreference" class="CollapseCard CybotCookiebotDialogHide" aria-labelledby="CybotCookiebotDialogDetailBodyContentCookieContainerPreferenceCard" ><div class="CybotCookiebotDialogDetailBodyContentC...
  • 10 
                <div id="CybotCookiebotDialogDetailBodyContentCookieTabsStatistics" class="CollapseCard CybotCookiebotDialogHide" aria-labelledby="CybotCookiebotDialogDetailBodyContentCookieContainerStatisticsCard" ><div class="CybotCookiebotDialogDetailBodyContentC...
#
Element
Relevant
Successes
Failures
Score
28
Search forms should include a role="search" attribute or be wrapped in an element with this role to indicate a search landmark for screen-readers.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <form id="minisearch-form-top-search" class="form minisearch" action="https://www.xandres.com/be_en/catalogsearch/result/" method="get" role="search">
            <div class="field search">
                <label class="label" for="minisearch-input-t...
#
Element
Relevant
Successes
Failures
Score
29
All forms should include a submission button built as an input type="submit" or a "button" element, or have a role="button" attribute. The button can be hidden if the form supports submission via the Enter key.
Yes
2
0
100

Code snapshots of successful elements

  • 1 
                <form id="minisearch-form-top-search" class="form minisearch" action="https://www.xandres.com/be_en/catalogsearch/result/" method="get" role="search">
            <div class="field search">
                <label class="label" for="minisearch-input-t...
  • 2 
                <form class="form subscribe" novalidate="novalidate" action="https://www.xandres.com/be_en/newsletter/subscription/new/" method="post" id="newsletter-validate-detail">
                    <div class="field newsletter">
                        <div cl...
#
Element
Relevant
Successes
Failures
Score
30
The validity status of each form element must be represented using the "aria-invalid" attribute with "true" or "false" values, and should update dynamically as the status changes.
No
0
0
#
Element
Relevant
Successes
Failures
Score
31
The title tag in the head section should be present and describe the current webpage accurately. This title appears in the browser tab, search engine results, and helps screen-reader users understand the page's content.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
32
The HTML tag should include a "lang" attribute representing the main language of the webpage to help screen-readers provide accurate pronunciation.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
33
The viewport meta tag should enable vision-impaired users to pinch-zoom to at least twice the standard size by including user-scalable="yes" and maximum-scale=2 (or higher) in the content attribute.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <meta name="viewport" content="width=device-width, initial-scale=1">
#
Element
Relevant
Successes
Failures
Score
34
Landmarks like main content and footer should use their corresponding HTML5 elements (&lt;main&gt;, &lt;footer&gt;) or include an "aria-label" and "role" attribute (e.g., role="main" or role="contentinfo"). Landmarks like search and navigation are covered elsewhere.
Yes
2
0
100

Code snapshots of successful elements

  • 1 
                <main id="maincontent" class="page-main-full-width"><a id="contentarea" tabindex="-1" ></a>
<div class="page messages" style="display: none;" ><div data-placeholder="messages" ></div>
<div data-bind="scope: 'messages'" >
    <!-- ko if: cookieMessage...
  • 2 
                <footer class="page-footer"><div class="footer content"><style >#html-body [data-pb-style=OVSIFVD]{justify-content:flex-start;display:flex;flex-direction:column;background-position:left top;background-size:cover;background-repeat:no-repeat;background...
#
Element
Relevant
Successes
Failures
Score
35
Font sizes should be at least 11px to ensure readability across most font families. This requirement should also be verified when using dynamic units like REM or percentages.
Yes
91
5
95

Code snapshots of failed elements

  • 1 
                <span aria-hidden="true" class="bzfy-o-likes">2501<div aria-hidden="false" class="bzfy-icon bzfy-icon--likes" ><svg height="20" viewBox="0 0 20 20" width="20" ><g fill="none" fill-rule="evenodd" ><rect height="20" width="20" ></rect><path d="M10 16.8...
  • 2 
                <span aria-hidden="true" class="bzfy-o-likes">0<div aria-hidden="false" class="bzfy-icon bzfy-icon--likes" ><svg height="20" viewBox="0 0 20 20" width="20" ><g fill="none" fill-rule="evenodd" ><rect height="20" width="20" ></rect><path d="M10 16.875a...
  • 3 
                <span aria-hidden="true" class="bzfy-o-likes">8<div aria-hidden="false" class="bzfy-icon bzfy-icon--likes" ><svg height="20" viewBox="0 0 20 20" width="20" ><g fill="none" fill-rule="evenodd" ><rect height="20" width="20" ></rect><path d="M10 16.875a...
  • 4 
                <span aria-hidden="true" class="bzfy-o-likes">2232<div aria-hidden="false" class="bzfy-icon bzfy-icon--likes" ><svg height="20" viewBox="0 0 20 20" width="20" ><g fill="none" fill-rule="evenodd" ><rect height="20" width="20" ></rect><path d="M10 16.8...
#
Element
Relevant
Successes
Failures
Score
36
Letter spacing should not be set below -1px to maintain readability across most font families. This should also be verified when using dynamic units like REM or percentages.
Yes
96
0
100
#
Element
Relevant
Successes
Failures
Score
37
Text elements should meet a minimum contrast ratio of 4.5:1 between the foreground (text color) and the background.
Yes
83
8
91

Code snapshots of successful elements

  • 1 
                <a id="CybotCookiebotDialogNavDeclaration" class="CybotCookiebotDialogNavItemLink CybotCookiebotDialogActive" href="#" data-target="CybotCookiebotDialogBody" tabindex="0" role="tab" aria-selected="true" lang="nl">Toestemming</a>
  • 2 
                <a id="CybotCookiebotDialogNavDetails" class="CybotCookiebotDialogNavItemLink" href="#" data-target="CybotCookiebotDialogTabContentDetails" tabindex="0" role="tab" aria-selected="false" lang="nl">Details</a>
  • 3 
                <a id="CybotCookiebotDialogNavAbout" class="CybotCookiebotDialogNavItemLink" href="#" data-target="CybotCookiebotDialogDetailBodyContentTextAbout" tabindex="0" role="tab" aria-selected="false" lang="nl">Over </a>
  • 4 
                <div id="CybotCookiebotDialogBodyContentTitle" class="CybotCookiebotDialogBodyContentHeading" lang="nl" role="heading" aria-level="1">Deze website maakt gebruik van cookies</div>
  • 5 
                <div id="CybotCookiebotDialogBodyContentText" lang="nl">We gebruiken cookies om content en advertenties te personaliseren, om functies voor social media te bieden en om ons websiteverkeer te analyseren. Ook delen we informatie over uw gebruik van onz...
  • 6 
                <button id="CybotCookiebotDialogBodyButtonDecline" class="CybotCookiebotDialogBodyButton" tabindex="0" lang="nl">Weigeren</button>
  • 7 
                <button id="CybotCookiebotDialogBodyLevelButtonCustomize" class="CybotCookiebotDialogBodyButton" tabindex="0" lang="nl">Aanpassen<div class="CybotCookiebotDialogArrow"></div></button>
  • 8 
                <button id="CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll" class="CybotCookiebotDialogBodyButton" tabindex="0" lang="nl">Alles toestaan</button>
  • 9 
                <span>NEW IN</span>
  • 10 
                <span>SHOP</span>

Code snapshots of failed elements

  • 1 
                <span>PRE-SALE</span>
  • 2 
                <span style="font-family: freigeist;">pre-<strong>sale</strong></span>
  • 3 
                <strong>sale</strong>
  • 4 
                <span style="font-family: freigeist;">20% OFF WHEN BUYING TWO ITEMS</span>
  • 5 
                <span style="font-family: freigeist; font-weight: 400;">NEW ARRIVALS</span>
  • 6 
                <span style="font-family: freigeist;">DISCOVER</span>
  • 7 
                <span style="font-family: freigeist; font-weight: 400;">CAPSULE COLLECTION</span>
#
Element
Relevant
Successes
Failures
Score
38
Carousels should include an "aria-label" attribute (e.g., carousel or slider) to indicate their functionality. They should also be marked as a landmark for screen-readers with a role="contentinfo" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
39
Control elements such as next and previous icons should include an "aria-label" attribute or a screen-reader only text that explains the functionality to screen-readers.
No
0
0
#
Element
Relevant
Successes
Failures
Score
40
A common accessibility mistake is treating carousels as live regions using the "aria-live attribute" with "polite" or "assertive" values. This can cause screen readers to cut off or skip important announcements.
No
0
0
#
Element
Relevant
Successes
Failures
Score
41
Carousel pagination items (usually used as small dots at the bottom of the carousel) should indicate their functionality and slide number they control using an "aria-label" and a screen-reader only text.
No
0
0
#
Element
Relevant
Successes
Failures
Score
42
Tables used for layout purposes should include a role="presentation" attribute to indicate to screen-readers that it is not a data table.
No
0
0
#
Element
Relevant
Successes
Failures
Score
43
If nested tables are used (a table element within a table cell), set the nested tables "role" attribute to "presentation".
No
0
0
#
Element
Relevant
Successes
Failures
Score
44
Tables without a thead row containing th elements should use the role="rowheader" attribute on td elements in the tr that visually represent the table headings.
No
0
0
#
Element
Relevant
Successes
Failures
Score
45
Visually deleted texts (e.g., a previous price on sale items) should include an "aria-label" attribute or a screen-reader only text to indicate that it is deleted.
No
0
0
#
Element
Relevant
Successes
Failures
Score
46
The main element of breadcrumbs should include a role="navigation" attribute and an "aria-label" to describe its functionality.
No
0
0
#
Element
Relevant
Successes
Failures
Score
47
Ratings/scores that are represented visually using stars, meters or other indicators should either have an "aria-label" attribute or a screen-reader only texts conveying the score/rate.
No
0
0
#
Element
Relevant
Successes
Failures
Score
48
An accessibility interface allows visually-impaired users to adjust UI elements like font size, colors, and spacing to suit their needs. While not a compliance requirement, it can help improve accessibility compliance.
No
0
0
#
Element
Relevant
Successes
Failures
Score
49
Iframe elements should include a "title" or "aria-label" attribute that explains their purpose, functionality, or destination. If irrelevant, they should be hidden from screen readers.
Yes
2
0
100

Code snapshots of successful elements

  • 1 
                <iframe tabindex="-1" role="presentation" aria-hidden="true" title="Blank" src="https://consentcdn.cookiebot.com/sdk/bc-v4.min.html" style="position: absolute; width: 1px; height: 1px; top: -9999px;" ></iframe>
  • 2 
                <iframe id="insider-worker" src="https://xandresbe.api.useinsider.com/worker-new.html" style="display: none;" ></iframe>