EVOLIZEDIGITAL RISK INTELLIGENCE
RUN FREE ASSESSMENT
RUN FREE ASSESSMENT
Public accessibility assessment

Accessibility issues detected on hypeandvice.com

Evolize inspected 5 publicly accessible pages on hypeandvice.com and detected 37 automatically identifiable accessibility findings. 21 findings were classified as critical or high priority. The findings map to 6 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, text has insufficient colour contrast.

37findings detected
21critical + high
5pages inspected
12 Aug 2026assessed

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

MONITOR THIS WEBSITERUN A FREE ASSESSMENT
https://

01 · Accessibility summary

Evolize inspected 5 publicly accessible pages on hypeandvice.com and detected 37 automatically identifiable accessibility findings. 21 findings were classified as critical or high priority. The findings map to 6 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, text has insufficient colour contrast.

02 · Priority findings

03 · WCAG criteria affected

CriterionNameLevelFindingsPages
1.4.3Contrast (Minimum)AA125
2.4.4Link Purpose (In Context)A125
2.4.3Focus OrderA65
2.1.1KeyboardA41
1.3.1Info and RelationshipsA25
1.4.4Resize TextAA15

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.

MONITOR HYPEANDVICE.COMSEE PRICING

04 · All detected findings

Critical

Links lack accessible text

WCAG 2.4.4 (A)12 instances5 affected pages
ComponentRef 0Y89DH

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

Affected pagehttps://www.hypeandvice.com/pages/contact-us
Element.swym-wishlist
Markup
<a href="/pages/swym-wishlist" class="swym-wishlist">
How to fixAdd text to the link, even if it's hidden visually, to help screen readers announce the link's purpose.
ComponentRef USL6Q5

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

Affected pagehttps://www.hypeandvice.com/pages/contact-us
Elementa[rel="nofollow"]
Markup
<a class="link--faded" target="_blank" rel="nofollow" href="https://www.shopify.com?utm_campaign=poweredby&amp;utm_medium=shopify&amp;utm_source=onlinestore"> </a>
How to fixAdd text to the link, such as 'Powered by Shopify', to provide a clear indication of its destination.
ComponentRef WBMY2D

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

Affected pagehttps://www.hypeandvice.com/
Element.shop-all-text[href$="hypeandvice.com/"]
Markup
<a href="https://www.hypeandvice.com/" class="shop-all-text"></a>
How to fixAdd text to the link, such as 'Shop All', or provide an alternative text using the 'aria-label' attribute, so screen readers can announce the link's purpose.
ComponentRef E0605L

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

Affected pagehttps://www.hypeandvice.com/cart
Element.swym-wishlist
Markup
<a href="/pages/swym-wishlist" class="swym-wishlist">
How to fixAdd text to the link, even if it's hidden visually, to help screen readers announce the link's purpose.
ComponentRef JYRC9H

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

Affected pagehttps://www.hypeandvice.com/
Elementa[rel="nofollow"]
Markup
<a class="link--faded" target="_blank" rel="nofollow" href="https://www.shopify.com?utm_campaign=poweredby&amp;utm_medium=shopify&amp;utm_source=onlinestore"> </a>
How to fixAdd text to the link, such as 'Powered by Shopify', to provide a clear indication of its destination.
ComponentRef M1Z8QD

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

Affected pagehttps://www.hypeandvice.com/products/cal-intarsia
Elementa[rel="nofollow"]
Markup
<a class="link--faded" target="_blank" rel="nofollow" href="https://www.shopify.com?utm_campaign=poweredby&amp;utm_medium=shopify&amp;utm_source=onlinestore"> </a>
How to fixAdd text to the link, such as 'Powered by Shopify', to provide a clear indication of its destination.
ComponentRef S7CKVF

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

Affected pagehttps://www.hypeandvice.com/policies/terms-of-service
Elementa[rel="nofollow"]
Markup
<a class="link--faded" target="_blank" rel="nofollow" href="https://www.shopify.com?utm_campaign=poweredby&amp;utm_medium=shopify&amp;utm_source=onlinestore"> </a>
How to fixAdd text to the link, such as 'Powered by Shopify', to provide a clear indication of its destination.
ComponentRef USFGGA

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

Affected pagehttps://www.hypeandvice.com/
Element.section--flush > div > a[href$="sale-1"]
Markup
<a href="/collections/sale-1">
How to fixAdd text to the link, or use an aria-label attribute to provide a text description of the link's purpose.
ComponentRef PH40KT

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

Affected pagehttps://www.hypeandvice.com/
Element.swym-wishlist
Markup
<a href="/pages/swym-wishlist" class="swym-wishlist">
How to fixAdd text to the link, even if it's hidden visually, to help screen readers announce the link's purpose.
ComponentRef XJF3O3

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

Affected pagehttps://www.hypeandvice.com/policies/terms-of-service
Element.swym-wishlist
Markup
<a href="/pages/swym-wishlist" class="swym-wishlist">
How to fixAdd text to the link, even if it's hidden visually, to help screen readers announce the link's purpose.
ComponentRef KBAEGH

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

Affected pagehttps://www.hypeandvice.com/cart
Elementa[rel="nofollow"]
Markup
<a class="link--faded" target="_blank" rel="nofollow" href="https://www.shopify.com?utm_campaign=poweredby&amp;utm_medium=shopify&amp;utm_source=onlinestore"> </a>
How to fixAdd text to the link, such as 'Powered by Shopify', to provide a clear indication of its destination.
ComponentRef RPT3M5

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

Affected pagehttps://www.hypeandvice.com/products/cal-intarsia
Element.swym-wishlist
Markup
<a href="/pages/swym-wishlist" class="swym-wishlist">
How to fixAdd text to the link, even if it's hidden visually, to help screen readers announce the link's purpose.
High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)50 instances5 affected pages
ComponentRef LYPC6S

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://www.hypeandvice.com/
Elementa#notepad-anchor-title
Accessible nameMy Wishlist
Markup
<a href="#swym-wishlist" class="swym-background-color" id="notepad-anchor-title" aria-label="My Wishlist" data-swym-loaded="true"><i class="swym-icon swym-notepad-white"></i>My Wishlist</a>
How to fixEnsure that all focusable elements are visible to sighted users, or remove them from the tab order if they are not meant to be interacted with. For the element with the id 'notepad-anchor-title', consider setting 'display: none' or 'visibility: hidden' to remove it from the tab order, or make it visible when focused.
Affected pages/ /products/cal-intarsia /pages/contact-us /policies/terms-of-service /cart
ComponentRef HS121K

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://www.hypeandvice.com/cart
Elementdiv#productDescription-1 > li:nth-of-type(1) > a
Accessible nameFAQs
Markup
<a href="/pages/faq" class="link--faded">FAQs</a>
How to fixRemove the link from the tab order by setting 'tabindex=-1' or make the link visible when it receives focus, for example by adding a visible focus style.
Affected pages/products/cal-intarsia /pages/contact-us /policies/terms-of-service /cart
ComponentRef FQ7PYM

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://www.hypeandvice.com/cart
Elementbutton#Toggle-1
Accessible nameSupport
Markup
<button id="Toggle-1" class="description-toggle">
                       Support
                      <svg id="downArrow-1" width="22" height="14" viewBox="0 0 22 14" fill="none" xmlns="http://www.w3.org/2000/svg" style="margin-left: 10px; display: inline;">
                        <path d="M19 3L11 11L3 3" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path>
                      </svg>
                      <svg id="upArrow-1" width="22" height="14" viewBox="0 0 22 14" fill="none" xmlns="http://www.w3.org/2000/svg" style="margin-left: 10px; display: …
How to fixRemove the element from the tab order by setting the 'tabindex' attribute to '-1' or by hiding it from screen readers using 'display: none' or 'visibility: hidden' in CSS, if it is not intended to be interacted with. Alternatively, make the element visible when it receives focus.
Affected pages/products/cal-intarsia /pages/contact-us /policies/terms-of-service /cart
ComponentRef KE53BE

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://www.hypeandvice.com/
Elementdiv > div:nth-of-type(2) > div:nth-of-type(1) > div > div > a
Accessible nameSHOP COLLEGE ESSENTIALS
Markup
<a href="/collections/ncaa-new-arrivals" class="button button--primary button-image_TaWgGW">SHOP COLLEGE ESSENTIALS</a>
How to fixTo fix this issue, ensure that all focusable elements are visible when they receive focus, or remove them from the tab order if they are not meant to be interacted with. This can be achieved by setting the 'display' or 'visibility' CSS property to 'none', or by using the 'tabindex' attribute to remove the element from the tab order.
ComponentRef C53L3J

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://www.hypeandvice.com/products/cal-intarsia
Elementdiv#product-4819412811881-tabs > div > tabs-nav > div > button:nth-of-type(1)
Accessible namePrevious
Markup
<button class="tabs-nav__arrow-item">
            <span class="visually-hidden">Previous</span><svg focusable="false" width="6" height="9" class="icon icon--product-tab-left  icon--direction-aware " viewBox="0 0 6 9">
        <path fill-rule="evenodd" clip-rule="evenodd" d="M2.554 4.5L6 1.054 4.946 0l-4.5 4.5 4.5 4.5L6 7.946 2.554 4.5z" fill="currentColor"></path>
      </svg></button>
How to fixTo fix this issue, remove the element from the tab order by setting the 'tabindex' attribute to '-1' or by using 'display: none' or 'visibility: hidden' to ensure it's not focusable when not visible.
ComponentRef KXLZFV

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://www.hypeandvice.com/
Elementdiv#fs-post-188332-261638766
Accessible nameopen detail modal for instagram post by hypeandvice on 04 AUGUST 2026
Rolebutton
Markup
<div tabindex="0" role="button" aria-label="open detail modal for instagram post by hypeandvice on 04 AUGUST 2026" aria-haspopup="dialog" id="fs-post-188332-261638766" class="fs-timeline-entry  fs-loading" style="cursor: pointer;">      <div class="fs-text-container">     <div class="fs-service-icon">       <i class="fs-icon fs-fa-instagram"></i>     </div>              <div class="fs-timeline-text">              <div class="fs-entry-title">counting down the days until football season.</div>            </div>     <div class="fs-entry-date">04 AUGUST 2026</div>           <div class="fs-hover-pr…
How to fixEnsure that all interactive elements are visible when they receive focus, or remove them from the tab order if they are not meant 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 keeping it visible for screen readers.
High

Text has insufficient colour contrast

WCAG 1.4.3 (AA)17 instances5 affected pages
ComponentRef WR634W

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

Affected pagehttps://www.hypeandvice.com/
Elementa[aria-controls="desktop-menu-6"]
Accessible nameSale
Markup
<a class="header__linklist-link " href="/collections/sale-1" style="color: red; font-weight: bold;" aria-controls="desktop-menu-6" aria-expanded="false">Sale</a>
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 a minimum contrast ratio of 4.5:1 for normal text.
Affected pages/ /products/cal-intarsia /pages/contact-us /policies/terms-of-service /cart
ComponentRef QK140O

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

Affected pagehttps://www.hypeandvice.com/
Element.shop-all-text[href$="all"]
Accessible nameSEE MORE
Markup
<a href="/collections/all" class="shop-all-text">SEE MORE</a>
How to fixIncrease the contrast between the text color and background color to meet the minimum contrast ratio thresholds, such as using a darker or lighter background, or a more vibrant text color.
ComponentRef MA50DU

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

Affected pagehttps://www.hypeandvice.com/
Element#shopify-section-template--22082214232169__categories_yBHGEC > section > .section__color-wrapper > div > .new-left-design.section__header > .heading-category-container > .shop-all-text
Accessible nameSHOP ALL
Markup
<a href="/collections/best-selling-collection" class="shop-all-text">SHOP ALL</a>
How to fixIncrease the contrast between the text color and its background by adjusting the CSS styles for the '.shop-all-text' class to meet the WCAG 2.1 minimum contrast ratio requirements.
ComponentRef 8MQGSQ

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

Affected pagehttps://www.hypeandvice.com/products/cal-intarsia
Element.breadcrumb__link[href="/"]
Accessible nameHome
Markup
<a class="breadcrumb__link" href="/">Home</a>
How to fixIncrease the contrast between the text color and background color of the link, ensuring a minimum contrast ratio of 4.5:1 for normal text.
ComponentRef 1RRJ9P

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

Affected pagehttps://www.hypeandvice.com/
Element.h3
Accessible nameJUST IN
Markup
<h3 class="heading h3 custom-template--22082214232169__product_list_PmJkHF">JUST IN</h3>
How to fixAdjust the color of the text or its background to ensure the contrast ratio meets the minimum requirements. This can be achieved by using online tools to calculate the contrast ratio and selecting colors that provide sufficient contrast.
Affected pages/ /products/cal-intarsia
ComponentRef XHFKTF

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

Affected pagehttps://www.hypeandvice.com/
Element.slideshow__text-wrapper--middle.slideshow__text-wrapper.vertical-breather:nth-child(2) > .font-color-mobile-image_hXWDaX.content-box.content-box--medium > .slideshow-heading-image_hXWDaX.heading--large > split-lines
Accessible namemost loved styles
Markup
<split-lines>most loved styles</split-lines>
How to fixIncrease the contrast between the text color and its background by adjusting either the text color or the background color to meet the minimum contrast ratio as defined by WCAG 2.1 SC 1.4.3.
ComponentRef JQ8T52

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

Affected pagehttps://www.hypeandvice.com/
Element.slideshow__text-wrapper--middle.slideshow__text-wrapper.vertical-breather > .font-color-mobile-image_TaWgGW.content-box.content-box--medium > .slideshow-heading-image_TaWgGW.heading--large > split-lines
Accessible nameGET MOVE IN READY.
Markup
<split-lines>GET MOVE IN READY.</split-lines>
How to fixAdjust the color of the text or its background to ensure the contrast ratio meets the minimum requirements. A contrast ratio of at least 4.5:1 for normal text is recommended.
ComponentRef I337BU

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

Affected pagehttps://www.hypeandvice.com/
Element.custom-html-subheading-template--22082214232169__164923770607431a63
Accessible nameTag us in your pics to be featured & a chance to win a $100 HV gift-card.
Markup
<h2 class="heading heading--small custom-html-subheading-template--22082214232169__164923770607431a63">Tag us in your pics to be featured &amp; a chance to win a $100 HV gift-card.</h2>
How to fixIncrease the contrast between the text color and the background color by using a darker or lighter shade, or add a background image or texture that provides sufficient contrast. Consider using a color contrast analyzer tool to determine the optimal colors.
ComponentRef 7SBJ4

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

Affected pagehttps://www.hypeandvice.com/products/cal-intarsia
Elementp:nth-child(6) > span:nth-child(2)
Accessible name♡
Markup
<span style="font-weight: 400;">♡</span>
How to fixIncrease the contrast between the text color and background color by using a color with a higher contrast ratio, or add a background or outline to the text to make it more readable.
ComponentRef 7J0PAY

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

Affected pagehttps://www.hypeandvice.com/
Element.logo-list-custom-template--22082214232169__165065396872bf5f8b
Accessible nameSHOP BY LEAGUE
Markup
<h3 class="heading h2 logo-list-custom-template--22082214232169__165065396872bf5f8b">SHOP BY LEAGUE</h3>
How to fixAdjust the colors of the text or background to ensure the contrast ratio meets the WCAG 2.1 guidelines for minimum contrast, which is 4.5:1 for normal text.
ComponentRef VCSV5H

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

Affected pagehttps://www.hypeandvice.com/
Element.slideshow__text-wrapper--middle.slideshow__text-wrapper.vertical-breather:nth-child(2) > .font-color-mobile-image_ic988f.content-box.content-box--medium > .slideshow-heading-image_ic988f.heading--large > split-lines
Accessible nameGO NY GO NY GO
Markup
<split-lines>GO NY GO NY GO</split-lines>
How to fixIncrease the contrast between the text and background colors by using a darker or lighter shade, or add an outline to the text to improve readability.
ComponentRef B9R631

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

Affected pagehttps://www.hypeandvice.com/
Element.category-heading
Accessible nameSHOP BY CATEGORY
Markup
<h3 class="heading h2 category-heading">SHOP BY CATEGORY</h3>
How to fixAdjust the color of the text or its background to achieve a contrast ratio of at least 4.5:1 for normal text, as recommended by the Web Content Accessibility Guidelines (WCAG 2.1).
High

Zooming and scaling must not be disabled

WCAG 1.4.4 (AA)5 instances5 affected pages
ComponentRef 6D9MZR

Zooming and scaling must not be disabled

Affected pagehttps://www.hypeandvice.com/
Elementmeta[name="viewport"]
Markup
<meta name="viewport" content="width=device-width, initial-scale=1.0, height=device-height, minimum-scale=1.0, maximum-scale=1.0">
How to fixRemove or adjust the minimum-scale and maximum-scale attributes in the meta viewport tag to allow zooming and scaling, for example: <meta name='viewport' content='width=device-width, initial-scale=1.0'>
Affected pages/ /products/cal-intarsia /pages/contact-us /policies/terms-of-service /cart
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)12 instances1 affected page
ComponentRef 2UFCJH

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://www.hypeandvice.com/products/cal-intarsia
Elementdiv > product-variants > div > div:nth-of-type(2) > div:nth-of-type(1) > label
Accessible nameXS
Markup
<label class="block-swatch__item custom-swatch-name" for="option-template--22082214920297__main--4819412811881-1" onclick="updateVariantId('32893416538217', 'X-Small')" style="display: block; pointer-events: none !important;"> XS </label>
How to fixAdd a tabindex attribute or use an interactive HTML element that can receive keyboard focus, such as a button or anchor tag, and ensure it is not disabled by pointer-events or other styling.
ComponentRef 4PTJ2T

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://www.hypeandvice.com/products/cal-intarsia
Elementimg#gallery-1
Markup
<img src="//www.hypeandvice.com/cdn/shop/files/HVWS24CAL1-1_e27e2fdb-d49d-43a6-99ff-4cb80d9c5f33.png?v=1783643596_800x.jpg" id="gallery-1" alt="" onclick="clickEvent(0)">
How to fixAdd focusable semantics or a tabindex to the interactive control, ensuring it can receive keyboard focus. Consider using a button element or adding appropriate ARIA attributes to enable keyboard accessibility.
High

Scrollable region must have keyboard access

WCAG 2.1.1 (A)2 instances1 affected page
ComponentRef PLKJY1

Scrollable region must have keyboard access

Affected pagehttps://www.hypeandvice.com/products/cal-intarsia
Element.gallery-responsive
Markup
<ul class="slider-container gallery-responsive" style="cursor: pointer;">
How to fixEnsure that the scrollable region can be accessed and controlled using a keyboard by adding appropriate keyboard event handlers or using a library that provides keyboard navigation out of the box.
ComponentRef CHP2VP

Scrollable region must have keyboard access

Affected pagehttps://www.hypeandvice.com/products/cal-intarsia
Element#pgallery > .slider-container
Markup
<ul class="slider-container">
How to fixEnsure that all scrollable regions can be accessed and controlled using a keyboard. This can typically be achieved by adding appropriate tabindex attributes or using ARIA attributes to manage focus, and ensuring that keyboard navigation is properly implemented.
Medium

Content sits outside any landmark region

WCAG 1.3.1 (A)5 instances5 affected pages
ComponentRef U4RP13

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://www.hypeandvice.com/
Elementdiv > div:nth-of-type(1) > div:nth-of-type(4) > div > div:nth-of-type(1) > p
Accessible nameSpend $100.00 more and get free shipping!
Markup
<p><span style="color: rgb(40,40,40);background-color: rgb(255,255,255);font-size: 15px;font-family: Armata, sans-serif;">Spend</span> $100.00 <span style="color: rgb(40,40,40);background-color: rgb(255,255,255);font-size: 15px;font-family: Armata, sans-serif;">more and get free shipping!</span>&nbsp;</p>
How to fixWrap the content in a landmark element (e.g., <main>, <header>, <nav>, <footer>, <aside>) to ensure it is reachable via landmark navigation. For example, the content could be wrapped in a <main> element: <main><p>Spend $100.00 more and get free shipping!</p></main>.
Affected pages/ /products/cal-intarsia /pages/contact-us /policies/terms-of-service /cart
Low

Navigation regions are not distinguishable

WCAG 1.3.1 (A)2 instances2 affected pages
ComponentRef GVGIOD

The page has multiple navigation landmarks but they lack accessible names, so screen reader users cannot tell them apart.

Affected pagehttps://www.hypeandvice.com/pages/contact-us
Elementdiv#shopify-section-header > store-header > div > div > nav
Accessible name.header__linklist.hidden-lap .header__linklist-link { display: flex; align-items: center; gap: 3px; font-family: 'Quantico-Bold'; letter-spacing: 0.5px; padding: 0 8px; text-transform: uppercase; } img.league-tab-image.NBA-logo { max-height: 35px; } img.league-tab-image.MLS-logo { max-height: 30px; } College SHOW ALL SCHOOLS .header__linklist.hidden-lap .header__linklist-link { display: flex; align-items: center; gap: 3px; font-family: 'Quantico-Bold'; letter-spacing: 0.5px; padding: 0 8px; text-transform: uppercase; } img.league-tab-image.NBA-logo { max-height: 35px; } img.league-tab-image.MLS-logo { max-height: 30px; } NBA .header__linklist.hidden-lap .header__linklist-link { display: flex; align-items: center; gap: 3px; font-family: 'Quantico-Bold'; letter-spacing: 0.5px; padding: 0 8px; text-transform: uppercase; } img.league-tab-image.NBA-logo { max-height: 35px; } img.league-tab-image.MLS-logo { max-height: 30px; } MLS …[truncated by Evolize: exceeded D1 value limit]
Rolenavigation
Markup
<nav class="header__inline-navigation" role="navigation"><desktop-navigation>
  <ul class="header__linklist list--unstyled hidden-pocket hidden-lap" role="list"><style>
        .header__linklist.hidden-lap .header__linklist-link {
          display: flex;
          align-items: center;
          gap: 3px;
          font-family: 'Quantico-Bold';
          letter-spacing: 0.5px;
          padding: 0 8px;
          text-transform: uppercase;
        }
        img.league-tab-image.NBA-logo {
          max-height: 35px;
        }
        img.league-tab-image.MLS-logo {
          max-height: 30px;
 …
How to fixAdd a unique and descriptive accessible name to each navigation landmark using the 'aria-label' or 'aria-labelledby' attribute.
Affected pages/products/cal-intarsia /pages/contact-us

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.

MONITOR THIS WEBSITESEE PRICING

Is information in this report inaccurate or outdated? Request a correction or removal.