Automated technical assessment of 5 publicly accessible pages · Scanned 13 Aug 2026. Inspected 5 of 5 selected pages.
Findings
Critical
Buttons have no accessible name
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Component
5 affected pages
5 instances
WCAG WCAG 2.1 SC 4.1.2 Name, Role, Value (Level A)
Ref I4FUV6
Affected pagehttps://gardeshop.com/
Element.form__submit
Markup<button type="submit" class="form__submit js-newsletter-submit" value="">
How to fixAdd an accessible name to the button by including text within the button element or providing an aria-label attribute with a descriptive value.
Critical
Links lack accessible text
Links expose no accessible name, so their destination is unknown to screen reader users.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 2.4.4 Link Purpose (In Context) (Level A)
Ref 5HC1AU
Affected pagehttps://gardeshop.com/cart
Elementa[area-label="Facebook"]
Markup<a href="https://www.facebook.com/gardeshop" area-label="Facebook" target="_blank">
How to fixAdd text to the link, or use aria-label with a descriptive value that screen readers can read, like 'Follow us on Facebook'.
Critical
Links lack accessible text
Links expose no accessible name, so their destination is unknown to screen reader users.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 2.4.4 Link Purpose (In Context) (Level A)
Ref EOZH76
Affected pagehttps://gardeshop.com/products/dante-come-as-you-are-bar-cart-1
Elementa[area-label="Facebook"]
Markup<a href="https://www.facebook.com/gardeshop" area-label="Facebook" target="_blank">
How to fixAdd text to the link, or use aria-label with a descriptive value that screen readers can read, like 'Follow us on Facebook'.
Critical
Links lack accessible text
Links expose no accessible name, so their destination is unknown to screen reader users.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 2.4.4 Link Purpose (In Context) (Level A)
Ref W8CCJ6
Affected pagehttps://gardeshop.com/
Elementa[area-label="Facebook"]
Markup<a href="https://www.facebook.com/gardeshop" area-label="Facebook" target="_blank">
How to fixAdd text to the link, or use aria-label with a descriptive value that screen readers can read, like 'Follow us on Facebook'.
Critical
Links lack accessible text
Links expose no accessible name, so their destination is unknown to screen reader users.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 2.4.4 Link Purpose (In Context) (Level A)
Ref A6530U
Affected pagehttps://gardeshop.com/collections/storage/products/dante-come-as-you-are-bar-cart-1
Elementa[area-label="Facebook"]
Markup<a href="https://www.facebook.com/gardeshop" area-label="Facebook" target="_blank">
How to fixAdd text to the link, or use aria-label with a descriptive value that screen readers can read, like 'Follow us on Facebook'.
Critical
Links lack accessible text
Links expose no accessible name, so their destination is unknown to screen reader users.
Component
1 affected page
2 instances
WCAG WCAG 2.1 SC 2.4.4 Link Purpose (In Context) (Level A)
Ref MXBEX3
Affected pagehttps://gardeshop.com/pages/payment
Elementa[area-label="Facebook"]
Markup<a href="https://www.facebook.com/gardeshop" area-label="Facebook" target="_blank">
How to fixAdd text to the link, or use aria-label with a descriptive value that screen readers can read, like 'Follow us on Facebook'.
High
Interactive controls are not keyboard-accessible
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.
Component
5 affected pages
5 instances
WCAG WCAG 2.1 SC 2.1.1 Keyboard (Level A)
Ref RRVM3R
Affected pagehttps://gardeshop.com/
Elementdetails#Details-menu-drawer-container > summary
Accessible nameMenu
Rolebutton
Markup<summary class="header-drawer__button focus-inset" aria-label="Menu" role="button" aria-expanded="false" aria-controls="menu-drawer"><svg xmlns="http://www.w3.org/2000/svg" width="25" height="13.5" viewBox="0 0 25 13.5">
<g transform="translate(0 0.75)">
<path d="M-327.645,16179.5h25" transform="translate(327.645 -16179.495)" fill="none" stroke="currentColor" stroke-width="1.5"></path>
<path d="M-327.645,16179.5h20" transform="translate(327.645 -16173.495)" fill="none" stroke="currentColor" stroke-width="1.5"></path>
<path d="M-327.645,16179.5h15" transform="translate(327.645 -16… How to fixAdd a tabindex attribute to the summary element or ensure it has focusable semantics to make the menu control accessible via keyboard navigation.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
5 affected pages
35 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref 553IQG
Affected pagehttps://gardeshop.com/
Elementdiv > div > div:nth-of-type(2) > ul > li:nth-of-type(1) > a
Accessible nameSeating
Markup<a href="/collections/seating" class="header__nav-megamenu-link full-unstyled-link focus-inset" aria-label="Seating">Seating</a>
How to fixEnsure that all focusable elements are visible when they receive focus, or remove them from the tab order if they are not intended to be interacted with. Consider using 'display: none' or 'visibility: hidden' to remove the element from the tab order, or use 'tabindex=-1' to remove it from the tab order while still allowing it to be focused programmatically.
High
Hidden elements can still receive keyboard focus
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Component
5 affected pages
15 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref TIUXNB
Affected pagehttps://gardeshop.com/
Elementli:nth-of-type(1) > div > div > div > div:nth-of-type(1) > a:nth-of-type(1)
Accessible nameDesigners + Artists
Markup<a class="header__nav-megamenu-title" href="/pages/designers">Designers + Artists</a>
How to fixRemove the element from the tab order by setting the 'tabindex' attribute to '-1' or by hiding it using 'display: none' or 'visibility: hidden' in CSS, if it's not intended to be interacted with.
High
Form fields use placeholder text as the only label
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.
Component
5 affected pages
11 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A), WCAG 2.1 SC 3.3.2 Labels or Instructions (Level A)
Ref AZ2ONT
Affected pagehttps://gardeshop.com/
Elementinput#Header-Input
Rolecombobox
Markup<input type="search" id="Header-Input" name="q" placeholder="Search..." role="combobox" aria-expanded="false" aria-owns="predictive-search-results-list" aria-controls="predictive-search-results-list" aria-haspopup="listbox" aria-autocomplete="list" autocorrect="off" autocomplete="off" autocapitalize="off" spellcheck="false" class="field__input focus-inset">
How to fixAdd a visible label to the form field, either by using a `<label>` element or by using the `aria-label` attribute if a visible label is not feasible.
High
Interactive controls are not keyboard-accessible
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.
Component
5 affected pages
55 instances
WCAG WCAG 2.1 SC 2.1.1 Keyboard (Level A)
Ref 5W6AWO
Affected pagehttps://gardeshop.com/
Elementdetails#Details-menu-drawer-menu-item-1 > summary
Accessible nameExplore
Rolebutton
Markup<summary class="header-drawer__link focus-inset" role="button" aria-expanded="false" aria-controls="link-explore">Explore<span class="header-drawer__plus"></span><!-- /.header-drawer__plus -->
</summary> How to fixAdd a tabindex attribute with a value of 0 or greater to the control, or use a native HTML element like a button that inherently supports keyboard focus.
High
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
5 affected pages
5 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref WP1LLB
Affected pagehttps://gardeshop.com/
Element#subscribe-email
Markup<input type="email" class="form__field" name="contact[email]" id="subscribe-email" value="" placeholder="Email">
How to fixIncrease the contrast between the text color and background color of the email input field to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3.
High
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
5 affected pages
10 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 38T3WX
Affected pagehttps://gardeshop.com/
Element.footer__col--double-small.footer__col.small-hide:nth-child(2) > .footer__links.list-unstyled > .footer__links-item:nth-child(3) > .full-unstyled-link.focus-inset
Accessible nameStudio
Markup<a href="https://gardeshop.com/pages/studio?view=studio" class="full-unstyled-link focus-inset">Studio</a>
How to fixIncrease the contrast between the text color and background color of the link to meet the WCAG 2.1 minimum contrast ratio thresholds.
High
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
5 affected pages
5 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 6GJNVA
Affected pagehttps://gardeshop.com/
Element.footer__subscribe-subtitle
Accessible nameJoin our mailing list.
Markup<div class="footer__subscribe-subtitle">
Join our mailing list.
</div> How to fixAdjust the background or text color to meet the minimum contrast ratio of 4.5:1 for normal text, as recommended by the Web Content Accessibility Guidelines (WCAG 2.1).
High
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
5 affected pages
5 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref RR9WO7
Affected pagehttps://gardeshop.com/
Elementh5
Accessible nameMailing List
Markup<h5 class="footer__subscribe-title">
Mailing List
</h5> How to fixIncrease the contrast between the text color and background color of the 'Mailing List' heading by using a darker or lighter shade, or by adding a background image or texture that provides sufficient contrast.
High
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
5 affected pages
75 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 488EO5
Affected pagehttps://gardeshop.com/
Element.footer__links.list-unstyled > .footer__links-item:nth-child(1) > .full-unstyled-link.focus-inset[href$="furniture"]
Accessible nameFurniture
Markup<a href="/collections/furniture" class="full-unstyled-link focus-inset">Furniture</a>
How to fixIncrease the contrast between the text color and background color of the link to meet the WCAG 2.1 minimum contrast ratio standards.
High
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
5 affected pages
10 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref D7F0VS
Affected pagehttps://gardeshop.com/
Element.footer__col--double-small.footer__col.small-hide:nth-child(2) > .footer__col-title
Accessible nameAbout
Markup<span class="footer__col-title">About</span>
How to fixIncrease the contrast between the text color and background color by using a color with a higher contrast ratio, such as using a darker or lighter shade.
High
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
5 affected pages
5 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref RDRMAL
Affected pagehttps://gardeshop.com/
Element.footer__col--double-large > .footer__col-title
Accessible nameProducts
Markup<span class="footer__col-title">Products</span>
How to fixIncrease the contrast between the text color and background color of the 'Products' footer section to meet the minimum contrast ratio thresholds as defined by WCAG 2.1 SC 1.4.3.
High
Modal dialog does not trap keyboard focus
An open modal leaves the content behind it keyboard-focusable, so keyboard and screen reader users can tab out of the dialog into hidden page content.
Component
4 affected pages
4 instances
WCAG WCAG 2.1 SC 2.4.3 Focus Order (Level A)
Ref U73W4D
Affected pagehttps://gardeshop.com/
Elementdiv#CartDrawer > div:nth-of-type(2)
Accessible nameYour selection
Roledialog
Markup<div class="cart-drawer__inner" role="dialog" aria-modal="true" aria-label="Your selection" tabindex="-1">
<div class="cart-drawer__head">
<div class="cart-drawer__head-bar">
<button class="cart-drawer__close" type="button" onclick="this.closest('cart-drawer').close()" aria-label="Close" data-drawer-close=""><svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" viewBox="0 0 16 16" fill="currentColor">
<path d="M4.835,4.835a1.143,1.143,0,0,1,1.618,0L12.5,10.884l6.047-6.049a1.144,1.144,0,0,1,1.618,1.618L14.115,12.5l6.049,6.047a1.144,1.144,0,0,1-1.618,1.618L12.5… How to fixTo fix this issue, ensure that the modal dialog traps keyboard focus by setting the 'tabindex' attribute to '-1' on the modal container and handling focus events to keep focus within the dialog.
High
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
4 affected pages
4 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref U65ZDK
Affected pagehttps://gardeshop.com/
Element.footer__copyright > p:nth-child(2)
Accessible name© 2026 Garde. All rights reserved.
Markup<p>© 2026 Garde. All rights reserved.</p>
How to fixIncrease the contrast between the text color and the background color by adjusting the CSS styles for the element, ensuring the contrast ratio meets the minimum requirements of WCAG 2.1 SC 1.4.3.
High
Summary elements must have discernible text
Summary elements must have discernible text
Component
5 affected pages
5 instances
WCAG WCAG SC 4.1.2
Ref KQ6Z4U
Affected pagehttps://gardeshop.com/
Element.disclosure-has-popup > .header__utils-link
Markup<summary class="header__utils-link">
How to fixAdd text to the summary element that describes its purpose, or provide an alternative text description for the SVG icon using the aria-label or aria-labelledby attribute.
High
Interactive controls are not keyboard-accessible
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.
Component
3 affected pages
9 instances
WCAG WCAG 2.1 SC 2.1.1 Keyboard (Level A)
Ref MF1DZ8
Affected pagehttps://gardeshop.com/
Elementdetails#Details-1-footer-footer > summary
Accessible nameProducts
Rolebutton
Markup<summary class="footer__mobile-summary focus-offset" role="button" aria-expanded="false">
<span>Products</span>
<span class="footer__disclosure-icon"></span><!-- /.footer__disclosure-icon -->
</summary> How to fixAdd focusable semantics or a tabindex to the interactive control to ensure it can receive keyboard focus.
High
Interactive controls are not keyboard-accessible
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.
Component
2 affected pages
6 instances
WCAG WCAG 2.1 SC 2.1.1 Keyboard (Level A)
Ref K9MN7U
Affected pagehttps://gardeshop.com/products/dante-come-as-you-are-bar-cart-1
Elementdetails#Accordion-1-product-template--16145167909040__main > summary
Accessible nameDimensions
Rolebutton
Markup<summary class="product__summary focus-offset" role="button" aria-expanded="false">
<span>Dimensions</span>
<span class="product__disclosure-icon accordion__icon"></span><!-- /.product__disclosure-icon -->
</summary> How to fixAdd focusable semantics or a tabindex to the interactive control to ensure it can receive keyboard focus. For example, consider adding a tabindex attribute or using an HTML element that inherently supports keyboard focus, such as a button element.
High
Images lack text alternatives
Informative images have no alternative text, so their meaning is unavailable to people using assistive technology.
Component
1 affected page
3 instances
WCAG WCAG 2.1 SC 1.1.1 Non-text Content (Level A)
Ref M6ZRGJ
Affected pagehttps://gardeshop.com/
Elementimg[width="1978"]
Markup<img srcset="//gardeshop.com/cdn/..." data-sizes="auto" data-src="//gardeshop.com/cdn/..." class="no-js-hidden small-h..." width="1978" height="1702" style="object-position: 50...." sizes="1440px" src="//gardeshop.com/cdn/...">
How to fixAdd an alt attribute to each image that provides a brief description of the image's content or purpose. For example, <img alt="Description of the image" src="image-source">. If the image is decorative and doesn't convey important information, use an empty alt attribute: alt="".
Medium
Navigation regions are not distinguishable
The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.
Component
5 affected pages
10 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A)
Ref TGQ8EY
Affected pagehttps://gardeshop.com/
Elementdiv#shopify-section-header > header > div > div > nav:nth-of-type(1)
Accessible nameExplore
Designers + Artists
Makers
Furniture
Seating
Tables
Storage
Consoles
Beds
Outdoor
Mirrors
Lighting
Wall lighting
Ceiling lighting
Table lighting
Floor lighting
In Stock
Furniture
Mirrors
Rugs
Lighting
Accessories
Wall Art
Objects + Ceramics
Wallpaper
Leather + Storage
Books
Textiles
Pillows + Throws
Rugs
Delcourt Textiles
Table Linens
Tabletop
Dinnerware
Glassware
Barware
Flatware + Cutlery
…[truncated by Evolize: exceeded D1 value limit]
Markup<nav class="header__nav small-hide">
<ul class="header__nav-items list-unstyled"><li class="header__nav-item">
<a href="/collections" class="header__nav-link full-unstyled-link focus-inset">Explore
</a>
<div class="header__nav-megamenu" tabindex="-1">
<div class="header__nav-megamenu-inner">
<div class="header__nav-megamenu-cols">
<div class="header__nav-megamenu-col">
… How to fixAdd an 'aria-label' or 'aria-labelledby' attribute to each navigation landmark to provide a unique and descriptive name. This will enable screen readers to announce the name of each navigation region, making it easier for users to navigate the page.
Medium
Navigation regions are not distinguishable
The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.
Component
5 affected pages
5 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A)
Ref CTDLZ2
Affected pagehttps://gardeshop.com/
Elementdiv#menu-drawer > div > nav
Accessible nameExplore
Furniture
View All
Seating
Tables
Storage
Consoles
Beds
Outdoor
Mirrors
Lighting
View All
Wall Lighting
Ceiling Lighting
Table Lighting
Floor Lighting
In Stock
View All
Furniture
Mirrors
rugs
Lighting
Accessories
View All
wall art
objects + ceramics
leather + storage
Book + games
Textiles
View All
pillows + throws
rugs
linens + towels
Tabletop
View All
dinnerware
glassware
barware
flatware + cutlery
serving + trays
Scents
View All
candles + incense
holders
Jewelry
DELPHINE CORDIE
KIMY GRINGOIRE
DESIGNERS + ARTISTSMakers
About
GardePress
Help
ReturnsPaymentFrequently Asked Questions
Sign in
Markup<nav class="header-drawer__nav">
<ul class="header-drawer__menu list-unstyled" role="list"><li class="header-drawer__menu-item"><details id="Details-menu-drawer-menu-item-1">
<summary class="header-drawer__link focus-inset" role="button" aria-expanded="false" aria-controls="link-explore">Explore<span class="header-drawer__plus"></span><!-- /.header-drawer__plus -->
</summary>
<div class="header-drawer__submenu" id="link-explore" tabindex="-1">
<ul class="header-drawer__menu list-unstyled" role="list" t… How to fixAdd an 'aria-label' or 'aria-labelledby' attribute to each navigation landmark to provide a unique and descriptive name.
Medium
Touch targets are too small
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
5 affected pages
5 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref GJA0OM
Affected pagehttps://gardeshop.com/
Element.form__submit
Markup<button type="submit" class="form__submit js-newsletter-submit" value="">
How to fixIncrease the size of the submit button to at least 24x24px or ensure that the button's container has sufficient padding to meet the minimum target size requirement.
Medium
Form fields use placeholder text as the only label
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.
Component
2 affected pages
2 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A), WCAG 2.1 SC 3.3.2 Labels or Instructions (Level A)
Ref 80NIUF
Affected pagehttps://gardeshop.com/products/dante-come-as-you-are-bar-cart-1
Elementtextarea#ContactForm-body
Accessible nameHello,
I am interested in DANTE Goods And Bads COME AS YOU ARE BAR CART L31.5” x W13.4” x H31.5”.
https://gardeshop.com/products/dante-come-as-you-are-bar-cart-1?variant=40222535549104
Markup<textarea rows="5" id="ContactForm-body" name="contact[Message]" placeholder="MESSAGE" class="field__input">Hello,
I am interested in DANTE Goods And Bads COME AS YOU ARE BAR CART L31.5” x W13.4” x H31.5”.
https://gardeshop.com/products/dante-come-as-you-are-bar-cart-1?variant=40222535549104</textarea>
How to fixAdd a visible and programmatic label to the form field, ensuring it remains available even when the user interacts with the field.
Medium
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 18OA2T
Affected pagehttps://gardeshop.com/cart
Elementp:nth-child(2)
Accessible name© 2026 Garde. All rights reserved.
Markup<p>© 2026 Garde. All rights reserved.</p>
How to fixAdjust the color of the text or its background to ensure the contrast ratio meets the minimum requirement of 4.5:1 for normal text. This can be achieved by using a color contrast analyzer tool to find suitable colors that meet the accessibility standards.
Low
Content sits outside any landmark region
Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.
Component
2 affected pages
2 instances
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A)
Ref R0S8UO
Affected pagehttps://gardeshop.com/products/dante-come-as-you-are-bar-cart-1
Elementdiv#shopify-section-cookie-banner > cookie-banner > div > div > div:nth-of-type(1) > p
Accessible nameWe use cookies to improve user experience and analyze website traffic.
Markup<p>We use cookies to improve user experience and analyze website traffic.</p>
How to fixTo fix this, ensure that all meaningful content is wrapped in a landmark element (like <header>, <nav>, <main>, <footer>, or <aside>) so that assistive technology users can access it through landmark navigation.
Low
Touch targets are too small
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Component
5 affected pages
10 instances
WCAG WCAG 2.2 SC 2.5.8 Target Size (Minimum) (Level AA)
Ref U6TMY8
Affected pagehttps://gardeshop.com/
Elementa[area-label="Facebook"]
Markup<a href="https://www.facebook.com/gardeshop" area-label="Facebook" target="_blank">
How to fixIncrease the size of interactive controls to at least 24x24 pixels, or ensure that they have sufficient padding to meet this minimum size requirement. Alternatively, consider using a larger tap target and visually styling it to be smaller if needed.
Low
Page has no level-one heading
The page exposes no <h1>, so its topic is not conveyed in the heading structure.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.3.1 Info and Relationships (Level A)
Ref FVJV7B
Affected pagehttps://gardeshop.com/
Elementhtml > body
Accessible nameSkip to content
<link href="//gardeshop.com/cdn/shop/t/8/assets/component-cart-items.css?v=39432873252519747141688072036" rel="stylesheet" type="text/css" media="all" />
Close
0
Your selection
Your cart is empty
We use cookies to improve user experience and analyze website traffic.
AcceptClose
Explore
Furniture
View All
Seating
Tables
Storage
Consoles
Beds
Outdoor
Mirrors
Lighting
View All
Wall Lighting
Ceiling Lighting
Table Lighting
Floor Lighting
In Stock
View All
Furniture
Mirrors
rugs
Lighting
Accessories
View All
wall art
objects + ceramics
leather + storage
Book + games
Textiles
View All
pillows + throws
rugs
linens + towels
Tabletop
View All
dinnerware
glassware
barware
flatware + cutlery
serving + trays
Scents
View All
candles + incense
holders
Jewelry
DELPHINE CORDIE
KIMY GRINGOIRE
DESIGNERS + ARTISTSMakers
About
GardePress
Help
ReturnsPaymentFrequently Asked Questions
Sign in
Explore
Designers + Artists
Makers
Furniture
Seating
Tables
Storage
…[truncated by Evolize: exceeded D1 value limit]
Markup<body class="
template
template--default-index
animate-index
">
<a class="skip-to-content-link button visually-hidden" href="#MainContent">Skip to content</a><link href="//gardeshop.com/cdn/shop/t/8/assets/component-cart-drawer.css?v=69757764611436621601687885327" rel="stylesheet" type="text/css" media="all"><link rel="stylesheet" href="//gardeshop.com/cdn/shop/t/8/assets/component-cart-items.css?v=39432873252519747141688072036" media="all" onload="this.media='all'">
<noscript><link href="//gardeshop.com/cdn/shop/t/8/assets/component-cart-items.css?v=39432873252519747… How to fixAdd a level-one heading (h1) to the page that accurately describes its content or purpose. This heading should be the first heading on the page and should be descriptive and concise.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
4 instances
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref I5ZAA9
Affected pagehttps://gardeshop.com/
Elementli:nth-child(1) > .featured-tile.featured-tile--large > .featured-tile__content
Accessible nameLighting
Markup<div class="featured-tile__content">Lighting</div>
How to fixIncrease the contrast between the text and background colors by using a color with a higher contrast ratio, such as changing the text color to a darker or lighter shade, or adjusting the background color to provide more contrast.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref 57L0A0
Affected pagehttps://gardeshop.com/
Elementa[href$="collections"]
Accessible nameExplore
Markup<a href="/collections" class="header__nav-link full-unstyled-link focus-inset">Explore
</a> How to fixIncrease the contrast between the text color and background color of the 'Explore' navigation link to meet the minimum contrast ratio of 4.5:1 for normal text.
Low
Text has insufficient colour contrast
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Component
1 affected page
1 instance
WCAG WCAG 2.1 SC 1.4.3 Contrast (Minimum) (Level AA)
Ref POS6ZO
Affected pagehttps://gardeshop.com/
Element.header__nav-link.full-unstyled-link[href="#"]
Accessible nameAbout
Markup<a href="#" class="header__nav-link full-unstyled-link focus-inset">About
</a> How to fixIncrease the contrast between the text color and background color of the navigation link to meet the minimum contrast ratio thresholds.