Public accessibility assessment

Accessibility issues detected on martie.com

Evolize inspected 5 publicly accessible pages on martie.com and detected 31 automatically identifiable accessibility findings. 13 findings were classified as critical or high priority. The findings map to 9 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve links lack accessible text, hidden elements can still receive keyboard focus, aria hidden element must not be focusable or contain focusable elements.

31findings detected
13critical + high
5pages inspected
13 Aug 2026assessed

Independent public assessment. martie.com is not necessarily affiliated with or a customer of Evolize.

https://

01 · Accessibility summary

Evolize inspected 5 publicly accessible pages on martie.com and detected 31 automatically identifiable accessibility findings. 13 findings were classified as critical or high priority. The findings map to 9 WCAG success criterions. The sections below show affected pages, technical evidence and recommended remediation. The most frequent issues involve links lack accessible text, hidden elements can still receive keyboard focus, aria hidden element must not be focusable or contain focusable elements.

02 · Priority findings

03 · WCAG criteria affected

CriterionNameLevelFindingsPages
1.4.3Contrast (Minimum)AA133
2.4.3Focus OrderA55
2.4.4Link Purpose (In Context)A31
1.1.1Non-text ContentA23
1.3.1Info and RelationshipsA23
2.1.1KeyboardA22
2.5.8Target Size (Minimum)AA22
2.4.1Bypass BlocksA15
4.1.2Name, Role, ValueA15

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 rescans public websites, detects newly introduced or recurring accessibility issues, tracks remediation and verifies fixes.

04 · All detected findings

Critical

Links lack accessible text

WCAG 2.4.4 (A)9 instances1 affected page
ComponentRef KM6JT9

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

Affected pagehttps://martie.com/
Element.mbanner-cream.mbanner[href$="just-landed"]
Markup
<a href="/collections/just-landed" class="mbanner mbanner-cream" style="--banner-desktop-aspect-ratio: 3.904;--banner-mobile-aspect-ratio: 1.6904761904761905;">
How to fixAdd text to these links, even if it's just a brief description of where the link goes, to help screen reader users understand their purpose.
ComponentRef 3CI7QS

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

Affected pagehttps://martie.com/
Element#shopify-section-template--16670796710133__carousel_X9MwnE > martie-carousel > .swiper.mcarousel__wrapper.swiper-initialized > .swiper-wrapper > .swiper-slide[data-swiper-slide-index="0"] > .mbanner-cream.mbanner
Markup
<a href="https://martie.com/collections/new-in-beauty" class="mbanner mbanner-cream" style="--banner-desktop-aspect-ratio: 3.904;--banner-mobile-aspect-ratio: 1.6904761904761905;">
How to fixAdd text to these links that describes their purpose, or use the 'aria-label' attribute to provide an accessible name for screen readers.
ComponentRef PXV12D

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

Affected pagehttps://martie.com/
Element#shopify-section-template--16670796710133__carousel_X9MwnE > martie-carousel > .swiper.mcarousel__wrapper.swiper-initialized > .swiper-wrapper > .swiper-slide-next.swiper-slide[data-swiper-slide-index="3"] > .mbanner-cream.mbanner
Markup
<a href="https://martie.com/products/avocado-oil-for-high-heat-cooking-baking" class="mbanner mbanner-cream" style="--banner-desktop-aspect-ratio: 4.0;--banner-mobile-aspect-ratio: 1.6904761904761905;">
How to fixAdd text to the link that describes its destination, or use the 'aria-label' attribute to provide a text description for screen readers.
High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)50 instances5 affected pages
ComponentRef SHSR5K

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://martie.com/
Elementdiv#shopify-section-sidebar > div:nth-of-type(1) > nav > div > a:nth-of-type(1)
Accessible nameJOIN FOR FREE
Markup
<a href="/account/register" class="sidebar-auth-buttons__join">
          <img src="//martie.com/cdn/shop/t/120/assets/icon-gift-heart.svg?v=61532771418684991111775514018" alt="" width="18" height="18">
          JOIN FOR FREE
        </a>
How to fixEnsure that all interactive elements are visible when they receive focus, or remove them from the tab order if they are not intended to be interacted with. This can be achieved by setting 'display: none' or 'visibility: hidden' on the element, or by using 'tabindex=-1' to remove it from the tab order.
Affected pages/ /pages/contact /products/elbows-52 /products/ingredients /pages/sell-your-products
ComponentRef D1C25W

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://martie.com/
Elementdiv#shopify-section-sidebar > div:nth-of-type(1) > nav > ul:nth-of-type(2) > li:nth-of-type(1) > a
Accessible nameHow it Works
Markup
<a href="/pages/howitworks" class="site-nav__link">
                

                  <img decoding="async" width="26px" height="26px" class="sidebar_img_off" src="//martie.com/cdn/shop/files/icon-how-it-works.svg?v=8928923217109078248" alt="How it Works Icon">
                  <img decoding="async" width="26px" height="26px" class="sidebar_img_on" src="//martie.com/cdn/shop/files/icon-how-it-works-selected.svg?v=18303001566563273724" alt="How it Works Icon">
                

                How it Works
              </a>
How to fixTo fix this issue, ensure that the link is either visible when it receives focus or remove it from the tab order by setting the 'tabindex' attribute to '-1' or by using 'display: none' or 'visibility: hidden' CSS properties to hide it.
Affected pages/ /pages/contact /products/elbows-52 /products/ingredients /pages/sell-your-products
ComponentRef 7IGE06

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://martie.com/
Elementheader#site-header > div > div:nth-of-type(1) > div > div > button
Accessible nameMenu
Markup
<button class="mobile-menu__button" aria-label="Menu" data-menu-button="" aria-expanded="false">
        <img src="//martie.com/cdn/shop/t/120/assets/icon-hamburger-black.svg?v=76289423371448193701765397450" width="23" height="14" alt="Menu">
      </button>
How to fixRemove the element from the tab order by setting the 'tabindex' attribute to '-1' or by making the element visible when it receives focus. Alternatively, ensure that the element is properly hidden from screen readers by using 'display: none' or 'visibility: hidden' in CSS.
Affected pages/ /pages/contact /products/elbows-52 /products/ingredients /pages/sell-your-products
ComponentRef VM7LEJ

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://martie.com/
Elementdiv#mobile-menu-header > a
Accessible nameMartie
Markup
<a href="/" title="Martie">
      <div class="site-logo">
        <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 800 168.75">
          <g id="Layer_2" data-name="Layer 2"><g id="Art"><path d="M138.49,145c0-6.61,1.11-11.68,4.85-24.9,2.42-8.81,3.75-14.76,3.75-17.62,0-5.73-3.09-9.25-7.94-9.25-2.42,0-5.5,1.32-8.37,4l-9.47,44.5c-4,18.73-10.57,24.9-23.79,24.9H92.23c-13.88,0-26.66-5.74-22.47-24.9l7.49-35.25c1.54-7.71-1.1-13.21-6.61-13.21-3.3,0-5.73,1.1-8.59,3.08l-9.69,45.38c-4,18.73-10.58,24.9-23.8,24.9H23.28c-13.88,0-26.66-5.74-22.47-24.9L18.65,57.28c.22-1.11,6.83-3.53,15.2-3.53,10.36,0,20.27…
How to fixRemove the element from the tab order or make it visible when it receives focus. This can be achieved by setting the 'tabindex' attribute to '-1' or by adjusting the CSS to display the element when it has focus.
Affected pages/ /pages/contact /products/elbows-52 /products/ingredients /pages/sell-your-products
ComponentRef KHKU2S

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Affected pagehttps://martie.com/
Elementa#account_login_link_kinn
Accessible nameLog In
Markup
<a href="/account/login" onclick="" id="account_login_link_kinn" class="site-nav__link customer-accounts___login-link customer-accounts__login-link--mobile">
            <span class="flex align-center"><img decoding="async" width="26px" height="26px" alt="Log In" src="https://martie.com/cdn/shop/files/[email removed]?v=14619729783260994824">
              <span>Log In</span>
            </span>
          </a>
How to fixTo fix this issue, ensure that the element is removed from the tab order when it is not visible, or make the element visible when it receives focus. This can be achieved by setting the 'tabindex' attribute to '-1' or by adjusting the CSS to display the element when focused.
Affected pages/ /pages/contact /products/elbows-52 /products/ingredients /pages/sell-your-products
High

ARIA hidden element must not be focusable or contain focusable elements

WCAG 4.1.2 (A)5 instances5 affected pages
ComponentRef 40VXFZ

ARIA hidden element must not be focusable or contain focusable elements

Affected pagehttps://martie.com/
Element#cart-drawer
Accessible nameYour Cart
Markup
<div id="cart-drawer" class="cart-drawer" data-cart-drawer="" aria-hidden="true" data-empty-cart-image="//martie.com/cdn/shop/t/120/assets/empty-cart-image.png?v=171685666844473977861742452310">
How to fixEnsure that elements with aria-hidden=true do not contain interactive elements and are not focusable themselves. Remove or disable interactive elements within the hidden container, or remove the aria-hidden attribute if the element should be accessible.
Affected pages/ /pages/contact /products/elbows-52 /products/ingredients /pages/sell-your-products
High

Text has insufficient colour contrast

WCAG 1.4.3 (AA)387 instances3 affected pages
ComponentRef JK8E8U

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

Affected pagehttps://martie.com/
Element.product-card--medium-value[data-product-savings="1401"][data-product-id="9775226552565"] > .product-card__price > .product-card__compare-price
Accessible name$25.00
Markup
<span class="product-card__compare-price">
              $25.00
            </span>
How to fixIncrease the contrast between the text color and the background color by using a darker or lighter shade for either the text or the background, ensuring the contrast ratio meets the WCAG 2.1 guidelines for minimum contrast.
Affected pages/ /products/elbows-52 /products/ingredients
ComponentRef WOQ9TX

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

Affected pagehttps://martie.com/
Elementmartie-product-card[data-product-savings="10871"] > .product-card__price > .product-card__compare-price
Accessible name$145
Markup
<span class="product-card__compare-price">
              $145
            </span>
How to fixIncrease the contrast between the text color and background color of the product compare price by using a darker or lighter shade, or by adding a background overlay to improve readability.
Affected pages/ /products/elbows-52 /products/ingredients
ComponentRef NVL4IF

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

Affected pagehttps://martie.com/
Element.junip-review-carousel-item-clickable.junip-review-carousel-item[role="button"]:nth-child(4) > .junip-review-body.junip-mt-2 > span
Markup
<span>The Areaware toys were adorable.  They had great colors and craftsmanship. Check out and shipping were seamless. Communi... </span>
How to fixIncrease the contrast between the text color and the background color by using a color with a higher contrast ratio, such as using a darker or lighter shade, or adding a background image or texture to improve readability.
Affected pages/ /products/elbows-52 /products/ingredients
ComponentRef 8TVY7B

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

Affected pagehttps://martie.com/
Elementmartie-product-card[data-product-savings="10871"] > .product-card__click-area[data-ref-id="click-area"] > .product-card__sizing
Accessible name1 oz
Markup
<div class="product-card__sizing">1 oz

        </div>
How to fixIncrease the contrast between the text and background colors by using a darker or lighter background, or by changing the text color to a color with sufficient contrast.
Affected pages/ /products/elbows-52 /products/ingredients
ComponentRef WCA1F4

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

Affected pagehttps://martie.com/
Element.tracking-acknowledgement__message
Markup
<p class="tracking-acknowledgement__message">
How to fixIncrease the contrast between the text color and background color by using a color with a higher contrast ratio, such as black text on a white background or white text on a dark background.
Affected pages/ /products/elbows-52 /products/ingredients
ComponentRef B78YE4

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

Affected pagehttps://martie.com/products/elbows-52
Elementdiv[data-ref-id="percent-off-value"]
Accessible nameSoldOut
Markup
<div data-ref-id="percent-off-value">Sold<br>Out</div>
How to fixTo fix this issue, adjust the color of the text or its background to meet the minimum contrast ratio as defined by WCAG 2.1 SC 1.4.3. This can be achieved by using online color contrast analyzer tools to find suitable color combinations that meet the accessibility standards.
Affected pages/products/elbows-52 /products/ingredients
ComponentRef 649QJ6

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

Affected pagehttps://martie.com/
Element.product-card--medium-value[data-product-savings="1401"][data-product-id="9775226552565"] > .product-card__percent-off-star > div
Accessible nameOff
Markup
<div>Off</div>
How to fixIncrease the contrast between the text color and the background color by using a color with a higher contrast ratio, such as a darker or lighter shade.
ComponentRef 4I2Y1Q

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

Affected pagehttps://martie.com/
Element.product-card--medium-value[data-product-savings="1401"][data-product-id="9775226552565"] > .product-card__click-area[data-ref-id="click-area"] > .product-card__sizing
Accessible name1 oz
Markup
<div class="product-card__sizing">1 oz

        </div>
How to fixAdjust the color of the text or its background to ensure the contrast ratio meets the minimum threshold of 4.5:1 for normal text, as recommended by the Web Content Accessibility Guidelines (WCAG 2.1).
ComponentRef NSEQIE

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

Affected pagehttps://martie.com/
Elementmartie-product-card[data-product-savings="300"] > .product-card__percent-off-star
Markup
<div class="product-card__percent-off-star">See in<br>Cart</div>
How to fixIncrease the contrast between the text color and background color by using a color with sufficient difference in lightness and saturation, or add a background image or texture to improve readability.
ComponentRef ANW6EM

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

Affected pagehttps://martie.com/
Elementmartie-product-card[data-product-savings="10871"] > .product-card__percent-off-star > strong
Accessible name74%
Markup
<strong>74%</strong>
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.
ComponentRef 73BTKW

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

Affected pagehttps://martie.com/
Elementmartie-product-card[data-product-savings="10871"] > .product-card__percent-off-star > div
Accessible nameOff
Markup
<div>Off</div>
How to fixIncrease the contrast between the text and background colors by using a color with a higher contrast ratio, or add a background image or texture to improve readability.
ComponentRef MQ5TX2

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

Affected pagehttps://martie.com/
Element.product-card--low-value[data-product-savings="150"][data-product-id="7616996081909"] > .product-card__percent-off-star
Accessible nameSee inCart
Markup
<div class="product-card__percent-off-star">See in<br>Cart</div>
How to fixIncrease the contrast between the text color and background color of the 'See in Cart' element to meet the minimum contrast ratio thresholds.
ComponentRef 5919J0

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

Affected pagehttps://martie.com/
Element.product-card--medium-value[data-product-savings="1401"][data-product-id="9775226552565"] > .product-card__percent-off-star > strong
Accessible name56%
Markup
<strong>56%</strong>
How to fixIncrease the contrast between the text color and background color by using a color with a higher contrast ratio, or provide an alternative way for users to access the information.
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)12 instances2 affected pages
ComponentRef LD0IQK

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.

Affected pagehttps://martie.com/products/elbows-52
Elementdiv:nth-of-type(1) > martie-gallery > div:nth-of-type(1) > div:nth-of-type(1) > div:nth-of-type(1) > img
Rolebutton
Markup
<img srcset="//martie.com/cdn/shop/products/63afad66-196f-4fd3-bab8-1b89c393b99b-removebg-preview.png?height=520&amp;v=1644437114 520w, //martie.com/cdn/shop/products/63afad66-196f-4fd3-bab8-1b89c393b99b-removebg-preview.png?height=926&amp;v=1644437114 926w" src="//martie.com/cdn/shop/products/63afad66-196f-4fd3-bab8-1b89c393b99b-removebg-preview.png?height=926&amp;v=1644437114" sizes="(min-width: 768px) 926px, 520px" role="button" alt="Elbows No. 52 Pasta" style="aspect-ratio: 0.697324414715719" loading="eager" fetchpriority="high">
How to fixAdd a tabindex to the image button or replace it with a native button element to ensure it can receive keyboard focus.
Affected pages/products/elbows-52 /products/ingredients
ComponentRef 2OY6TX

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.

Affected pagehttps://martie.com/products/elbows-52
Elementdiv:nth-of-type(1) > div:nth-of-type(1) > martie-gallery > div:nth-of-type(2) > div > img:nth-of-type(1)
Rolebutton
Markup
<img data-ref-id="nav-image" src="//martie.com/cdn/shop/products/63afad66-196f-4fd3-bab8-1b89c393b99b-removebg-preview.png?height=48&amp;v=1644437114" height="48" role="button" alt="Elbows No. 52 Pasta" loading="lazy">
How to fixAdd focusable semantics or a tabindex to the interactive image element, ensuring it can receive keyboard focus. For example, consider adding a tabindex attribute or wrapping the image in a focusable element like a button or anchor tag.
Affected pages/products/elbows-52 /products/ingredients
Medium

No skip link to main content

WCAG 2.4.1 (A)5 instances5 affected pages
ComponentRef PCOMLB

The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.

Affected pagehttps://martie.com/
Elementbody#martie-com-save-up-to-80-on-your-favorite-brands
Accessible nameglobalThis.ab_test_segment = null; .site-header__logo-image { max-width: 160px; } .header-alt__header, .site-header { background: #dbbae7 } Seen on The New Yorker, Strategist & EATER Join for free Sign In Search and save Join for free Sign in My Account My Orders My Favorites JOIN FOR FREE SIGN IN Log In How it Works Just Landed My Favorites For You Shop All Pantry Crackers & Crisps Coffee & Tea Sweets Chips & Puffs Beverage Pasta & Grains Bars Jerky & Cured Meats Cans & Jars Energy & Wellness Meals & Sides Condiments Oils & Vinegars Seasonings Breakfast Nut Butters & Jams Dried Fruits & Nuts Milk & Creamer Broths Breads & Rolls Baking …[truncated by Evolize: exceeded D1 value limit]
Markup
<body id="martie-com-save-up-to-80-on-your-favorite-brands" class="template-index">
      <svg id="junipStarSymbols" style="display: none;"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
  <symbol id="junipOutlineStar" viewBox="0 0 16 16">
    <path d="m3.2 16.0001081c-.1687782 0-.33328968-.0531313-.47-.1521081-.24051968-.174488-.36451194-.4679107-.322-.762l.743-5.203-2.917-2.917c-.21191095-.21196521-.28756133-.52460199-.196-.81.09130759-.2851682.3345701-.49522345.63-.544l4.398-.734 2.218-4.435c.13744692-.27145241.41573373-.4426761.72-.443.3045618.00166772.58175678.1761261.715.45…
How to fixAdd a skip link at the top of the page that allows users to bypass the navigation and directly access the main content. This link should be visible to screen readers and keyboard users, and should be the first focusable element on the page.
Affected pages/ /pages/contact /products/elbows-52 /products/ingredients /pages/sell-your-products
Low

Content sits outside any landmark region

WCAG 1.3.1 (A)2 instances2 affected pages
ComponentRef G040HZ

Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.

Affected pagehttps://martie.com/products/elbows-52
Elementdiv#shopify-section-header > div > martie-announcement-bar > div > p
Accessible nameFREE SHIPPING always on all orders $50+
Markup
<p>FREE SHIPPING always on all orders $50+</p>
How to fixWrap the content in a suitable landmark element (e.g., <main>, <header>, <nav>, <footer>, <aside>) to ensure it is accessible via landmark navigation. For example, the given text could be wrapped in a <div role='main'> or another appropriate landmark container.
Affected pages/products/elbows-52 /products/ingredients
Low

Touch targets are too small

WCAG 2.5.8 (AA)4 instances2 affected pages
ComponentRef T20H3

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://martie.com/
Elementa[target="_blank"]:nth-child(3)
Accessible nameMartie on the Google Play Store
Markup
<a href="https://play.google.com/store/apps/details?id=com.martie.martie" target="_blank">
How to fixEnsure that all interactive elements, such as buttons and links, have a minimum size of 24x24px to make them easily accessible by touch.
Affected pages/ /pages/sell-your-products
ComponentRef WYXHPP

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Affected pagehttps://martie.com/
Element.martie-app-instructions > a[target="_blank"]:nth-child(2)
Accessible nameMartie on the Apple App Store
Markup
<a href="https://apps.apple.com/us/app/martie-discount-grocery/id1665264838" target="_blank">
How to fixIncrease the size of the interactive elements to at least 24x24px or ensure there is sufficient space around them to make them easily clickable.
Affected pages/ /pages/sell-your-products
Low

Low-quality alternative text

WCAG 1.1.1 (A)455 instances3 affected pages
ComponentRef HA787T

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

Affected pagehttps://martie.com/
Elementdiv > div:nth-of-type(5) > martie-product-card > a > div:nth-of-type(1) > img
Markup
<img src="//martie.com/cdn/shop/files/1786129316517-existing-image-cropped-no-bg.png?v=1786129321&amp;width=240" alt="existing-image-cropped-no-bg" srcset="//martie.com/cdn/shop/files/1786129316517-existing-image-cropped-no-bg.png?v=1786129321&amp;width=240 240w" width="240" height="240">
How to fixUpdate the alt text to provide a clear and concise description of the image content. Ensure that each image has unique and descriptive alt text that reflects its content.
Affected pages/ /products/elbows-52 /products/ingredients
ComponentRef JNPGAO

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

Affected pagehttps://martie.com/
Elementdiv:nth-of-type(1) > martie-product-card > martie-add-to-cart > div > button:nth-of-type(1) > img
Markup
<img class="add-to-cart__spinner" width="15" height="15" alt="Removing item..." src="https://cdn.shopify.com/s/files/1/0575/1829/3150/files/progress-pnb.png?v=1714590415">
How to fixUpdate the alt text to provide a clear and concise description of the image content. Ensure that each image has unique and descriptive alt text that reflects its purpose and context.
Affected pages/ /products/elbows-52 /products/ingredients
Low

Page has no level-one heading

WCAG 1.3.1 (A)1 instance1 affected page
ComponentRef NYK61S

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

Affected pagehttps://martie.com/
Elementbody#martie-com-save-up-to-80-on-your-favorite-brands
Accessible nameglobalThis.ab_test_segment = null; .site-header__logo-image { max-width: 160px; } .header-alt__header, .site-header { background: #dbbae7 } Seen on The New Yorker, Strategist & EATER Join for free Sign In Search and save Join for free Sign in My Account My Orders My Favorites JOIN FOR FREE SIGN IN Log In How it Works Just Landed My Favorites For You Shop All Pantry Crackers & Crisps Coffee & Tea Sweets Chips & Puffs Beverage Pasta & Grains Bars Jerky & Cured Meats Cans & Jars Energy & Wellness Meals & Sides Condiments Oils & Vinegars Seasonings Breakfast Nut Butters & Jams Dried Fruits & Nuts Milk & Creamer Broths Breads & Rolls Baking …[truncated by Evolize: exceeded D1 value limit]
Markup
<body id="martie-com-save-up-to-80-on-your-favorite-brands" class="template-index">
      <svg id="junipStarSymbols" style="display: none;"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16">
  <symbol id="junipOutlineStar" viewBox="0 0 16 16">
    <path d="m3.2 16.0001081c-.1687782 0-.33328968-.0531313-.47-.1521081-.24051968-.174488-.36451194-.4679107-.322-.762l.743-5.203-2.917-2.917c-.21191095-.21196521-.28756133-.52460199-.196-.81.09130759-.2851682.3345701-.49522345.63-.544l4.398-.734 2.218-4.435c.13744692-.27145241.41573373-.4426761.72-.443.3045618.00166772.58175678.1761261.715.45…
How to fixAdd a level-one heading (h1) to the page that accurately describes its main topic or purpose. Ensure this heading is the first heading on the page and is descriptive enough to provide context for users.

05 · Pages inspected

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.