Public accessibility assessment

Accessibility issues detected on hawaiianhost.com

Evolize inspected 5 public pages on hawaiianhost.com and detected 27 automatically identifiable accessibility findings.

27Findings detected
6WCAG criteria affected
5Pages inspected
9 Sep 2026Assessment date

Highest detected severity: High · 8 high-priority findings · 100% inspected-page coverage

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

Is hawaiianhost.com your website?

Keep this assessment current and get notified when new accessibility issues are detected.

https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on hawaiianhost.com and detected 27 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 5 inspected pages. The most affected inspected page was "/", where 18 findings were detected. The assessment identified findings mapped to 6 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.

02 · Start here

These findings combine the highest severity and broadest reach detected during this assessment.

  1. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 15 instances
    Why this matters

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

    Recommended action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →
  2. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 10 instances
    Why this matters

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

    Recommended action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →
  3. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 10 instances
    Why this matters

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

    Recommended action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →
  4. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 5 instances
    Why this matters

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

    Recommended action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →
  5. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 5 instances
    Why this matters

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

    Recommended action

    Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA1333 / 5
2.4.3Focus OrderA655 / 5
1.3.1Info and RelationshipsA355 / 5
2.1.1KeyboardA311 / 5
1.1.1Non-text ContentA255 / 5
2.2.2Pause, Stop, HideA111 / 5

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

Continuous monitoring

A scan shows today's exposure. Monitoring shows what changes next.

Evolize continuously reassesses public website pages, detects newly introduced or recurring accessibility findings, and tracks remediation over time.

04 · All detected findings

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)50 instances5 inspected pages

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

Why it matters

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

Recommended correction

Keep this element out of the tab order while its containing region is hidden — remove it from focus (for example tabindex="-1"), or apply the inert attribute to the hidden container where supported. Restore normal focusability when the region becomes visible.

View 50 affected elements
Component · Ref FB1UJW
Affected pagehttps://hawaiianhost.com/cart
Elementdiv#NavDrawer > div > div:nth-of-type(1) > div > div:nth-of-type(2) > button
Accessible nameClose menu
Markup
<button type="button" class="drawer__close-button js-drawer-close">
            <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon-close" viewBox="0 0 64 64"><path d="M19 17.61l27.12 27.13m0-27.12L19 44.74"></path></svg>
            <span class="icon__fallback-text">Close menu</span>
          </button>
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
Component · Ref BS4E36
Affected pagehttps://hawaiianhost.com/account/login
Elementa#Label-pages-about-us1
Accessible nameAbout Us
Markup
<a href="/pages/about-us" class="mobile-nav__link mobile-nav__link--top-level" id="Label-pages-about-us1">
                    About Us
                  </a>
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
Component · Ref TALGZA
Affected pagehttps://hawaiianhost.com/pages/sign-up-for-email
Elementdiv#CartDrawer > form > div:nth-of-type(1) > div > div:nth-of-type(2) > button
Accessible nameClose cart
Markup
<button type="button" class="drawer__close-button js-drawer-close">
							<svg viewBox="0 0 10 10">
                <path d="M1.27519 9.59778L4.68001 6.15677L8.08483 9.59778L9.35945 8.30923L5.95463 4.86822L9.35945 1.42721L8.08483 0.138672L4.68001 3.57968L1.27519 0.138672L0 1.42721L3.40481 4.86822L0 8.30923L1.27519 9.59778Z"></path>
              </svg>
							<span class="icon__fallback-text">Close cart</span>
						</button>
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
Component · Ref F75JX7
Affected pagehttps://hawaiianhost.com/
Elementdiv:nth-of-type(2) > ul > li:nth-of-type(3) > div > div > a
Accessible nameLog in
Markup
<a href="/account" class="mobile-nav__link">
                    
                      Log in
                    
                  </a>
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
Component · Ref T75KTO
Affected pagehttps://hawaiianhost.com/products/choco-mango
Elementdiv#CartContainer > div:nth-of-type(1) > a
Accessible nameKeep Shopping
Markup
<a class="btn" href="/collections/all">Keep Shopping</a>
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
Component · Ref QJU4SS
Affected pagehttps://hawaiianhost.com/products/choco-mango
Elementform#HeaderSearchForm > button
Accessible nameSearch
Markup
<button type="submit" class="text-link site-header__search-btn site-header__search-btn--submit">
                  <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon-search" viewBox="0 0 64 64">
                    <path d="M47.16 28.58A18.58 18.58 0 1 1 28.58 10a18.58 18.58 0 0 1 18.58 18.58zM54 54L41.94 42"></path>
                  </svg>
                  <span class="icon__fallback-text">Search</span>
                </button>
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)5 instances1 inspected page

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Why it matters

A control that responds to clicks (a clickable element or an ARIA widget) cannot receive keyboard focus, so keyboard and switch users cannot operate it.

Recommended correction

Use a native <button>/<a>, or add tabindex="0" plus keyboard event handlers (Enter/Space) to custom controls.

View 5 affected elements
Component · Ref 0XLFZU
Affected pagehttps://hawaiianhost.com/products/choco-mango
Elementdiv#ProductPhotos-15194142310771 > div > div > div:nth-of-type(2)
Accessible nameChoco Mango
Roleoption
Markup
<div class="secondary-slide slick-slide" data-index="1" data-slick-index="1" aria-hidden="true" tabindex="-1" role="option" style="width: 649px; position: relative; left: -649px; top: 0px; z-index: 998; opacity: 1;">

  
<div class="product-image-main product-image-main--15194142310771"><div class="image-wrap" style="height: 0; padding-bottom: 100.0%;"><img class=" " style="opacity:1" data-photoswipe-src="//hawaiianhost.com/cdn/shop/files/DSC9077_1800x1800.webp?v=1760053026" data-photoswipe-width="1250" data-photoswipe-height="1250" data-index="2" src="//hawaiianhost.com/cdn/shop/files/DSC9077…
Component · Ref 3UNX33
Affected pagehttps://hawaiianhost.com/products/choco-mango
Elementdiv#ProductPhotos-15194142310771 > div > div > div:nth-of-type(1)
Accessible nameChoco Mango
Roleoption
Markup
<div class="starting-slide slick-slide slick-current slick-active" data-index="0" data-slick-index="0" aria-hidden="true" tabindex="-1" role="option" style="width: 649px; position: relative; left: 0px; top: 0px; z-index: 999; opacity: 1;">

  
<div class="product-image-main product-image-main--15194142310771"><div class="image-wrap" style="height: 0; padding-bottom: 100.0%;"><img class=" " style="opacity:1" data-photoswipe-src="//hawaiianhost.com/cdn/shop/files/DSC9062_1800x1800.webp?v=1760053026" data-photoswipe-width="1250" data-photoswipe-height="1250" data-index="1" src="//hawaiianhost.com…
Medium

Navigation regions are not distinguishable

WCAG 1.3.1 (A)10 instances5 inspected pages

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

Why it matters

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

Recommended correction

Give each navigation region a distinct aria-label (e.g. "Primary", "Footer") when more than one is present.

View 10 affected elements
Component · Ref 4N01UZ
Affected pagehttps://hawaiianhost.com/products/choco-mango
Elementdiv#shopify-section-header > div:nth-of-type(3) > div:nth-of-type(1) > nav
Accessible nameHawaiian Host Group Logo
Markup
<nav class="hh-topbar--logos">
		<menu>
			<li class="topbar-logo--hhg">
				<a href="https://www.hawaiianhostgroup.com/" aria-label="Go to Hawaiian Host Group website" target="_blank">
					<img src="//hawaiianhost.com/cdn/shop/t/503/assets/hawaiian-host-group-logo-large-white.png?v=175744422423742401759882437" alt="Hawaiian Host Group Logo" height="" width="">
				</a>
			</li>

			<li class="topbar-logo--ml">
				<a href="https://hawaiianhost.com/pages/maunaloa" aria-label="Go to Mauna Loa Store website">
					<img src="//hawaiianhost.com/cdn/shop/t/503/assets/mauna-loa-logo-white.png?v=123…
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
Component · Ref 6D13DN
Affected pagehttps://hawaiianhost.com/cart
Elementdiv > header > div:nth-of-type(1) > div > div:nth-of-type(3) > div
Accessible nameLog in Cart Search Site navigation
Rolenavigation
Markup
<div class="site-nav" role="navigation">
  <div class="site-nav__icons">
    
      <a class="site-nav__link site-nav__link--icon small--hide" href="/account">
        <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon-user" viewBox="0 0 64 64"><path d="M35 39.84v-2.53c3.3-1.91 6-6.66 6-11.41 0-7.63 0-13.82-9-13.82s-9 6.19-9 13.82c0 4.75 2.7 9.51 6 11.41v2.53c-10.18.85-18 6-18 12.16h42c0-6.19-7.82-11.31-18-12.16z"></path></svg>
        <span class="icon__fallback-text">
          
            Log in
          
        </span>
      </a>
    
<a href="/cart" class="s…
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)19 instances3 inspected pages

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

Why it matters

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

Recommended correction

Increase the contrast ratio to at least 4.5:1 for normal text and 3:1 for large text.

View 19 affected elements
Component · Ref YM6OSZ
Affected pagehttps://hawaiianhost.com/
Element.ai-blog-collection__article-awvfrmenfa1nou0z4zaigenblock53fceebcxxtuk:nth-child(2) > .ai-blog-collection__article-content-awvfrmenfa1nou0z4zaigenblock53fceebcxxtuk > .ai-blog-collection__article-date-awvfrmenfa1nou0z4zaigenblock53fceebcxxtuk
Accessible nameSeptember 08, 2026
Markup
<div class="ai-blog-collection__article-date-awvfrmenfa1nou0z4zaigenblock53fceebcxxtuk">
                  September 08, 2026
                </div>
Component · Ref 3ZEDD3
Affected pagehttps://hawaiianhost.com/
Element.ai-blog-spotlight-card-aqxditct3zlpdqzh6naigenblock1d96c72fwxr3q:nth-child(2) > .ai-blog-spotlight-content-aqxditct3zlpdqzh6naigenblock1d96c72fwxr3q > .ai-blog-spotlight-meta-aqxditct3zlpdqzh6naigenblock1d96c72fwxr3q > time
Accessible nameSeptember 08, 2025
Markup
<time class="ai-blog-spotlight-date-aqxditct3zlpdqzh6naigenblock1d96c72fwxr3q" datetime="2025-09-08">
                  September 08, 2025
                </time>
Component · Ref UCB3T9
Affected pagehttps://hawaiianhost.com/
Element.ai-blog-spotlight-card-aqxditct3zlpdqzh6naigenblock1d96c72fwxr3q:nth-child(2) > .ai-blog-spotlight-content-aqxditct3zlpdqzh6naigenblock1d96c72fwxr3q > .ai-blog-spotlight-meta-aqxditct3zlpdqzh6naigenblock1d96c72fwxr3q > .ai-blog-spotlight-author-aqxditct3zlpdqzh6naigenblock1d96c72fwxr3q
Accessible nameBy Kaci Yamato
Markup
<span class="ai-blog-spotlight-author-aqxditct3zlpdqzh6naigenblock1d96c72fwxr3q">
                    By Kaci Yamato
                  </span>
Component · Ref FL2ZRL
Affected pagehttps://hawaiianhost.com/
Element.ai-new-arrival-callout-ab3fycev4bw1qzfzuqaigenblock566ff32dxzqej--1 > .ai-new-arrival-callout-number-ab3fycev4bw1qzfzuqaigenblock566ff32dxzqej
Accessible name1
Markup
<span class="ai-new-arrival-callout-number-ab3fycev4bw1qzfzuqaigenblock566ff32dxzqej">1</span>
Component · Ref V5CY3M
Affected pagehttps://hawaiianhost.com/
Element.ai-new-arrival-feature-ab3fycev4bw1qzfzuqaigenblock566ff32dxzqej:nth-child(1) > .ai-new-arrival-feature-number-ab3fycev4bw1qzfzuqaigenblock566ff32dxzqej
Accessible name1
Markup
<div class="ai-new-arrival-feature-number-ab3fycev4bw1qzfzuqaigenblock566ff32dxzqej">1</div>
Component · Ref 23OQBC
Affected pagehttps://hawaiianhost.com/products/choco-mango
Element.klaviyo-bis-trigger
Accessible nameNotify Me When Available
Markup
<a class="btn klaviyo-bis-trigger" href="#" style="text-align: center; margin: 0px; width: auto;">Notify Me When Available</a>
Component · Ref RBMQNX
Affected pagehttps://hawaiianhost.com/products/choco-mango
Element.product-single__description > p
Accessible nameThis irresistible island-inspired treat pairs juicy, sun-ripened dried mango with a rich coating of premium dark chocolatey goodness. Each bite delivers the perfect balance of sweet, tangy fruitiness and smooth, decadent chocolatey, creating a unique fusion of flavors that’s both refreshing and indulgent.
Markup
<p>
Component · Ref 5VZX4Q
Affected pagehttps://hawaiianhost.com/products/choco-mango
Elementa[title="Back to the frontpage"]
Accessible nameHome
Markup
<a href="/" title="Back to the frontpage">Home</a>
Component · Ref 6URI29
Affected pagehttps://hawaiianhost.com/account/login
Element.btn--full
Accessible nameSign In
Markup
<button type="submit" class="btn btn--full">
                            Sign In
                        </button>
Component · Ref 6ANBG9
Affected pagehttps://hawaiianhost.com/products/choco-mango
Elementlabel[for="Quantity-15194142310771"]
Accessible nameQty
Markup
<label for="Quantity-15194142310771">Qty</label>
Component · Ref 9N3466
Affected pagehttps://hawaiianhost.com/
Elementa[aria-label="Learn More Image"]
Accessible nameLearn More Image
Markup
<a aria-label="Learn More Image" href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fvimeo.com%2f1076145506%2fbdd7227c6a%3fshare%3dcopy&c=E,1,vSxmjYfnmgy0v_tMIySH-owpoNcYkwtrttmKrmxD1pnPpbOlNKzegIDcJAIsTA_phHp1yC_e_FRgncNp0atp6qqG7PlKGTpLWW8BQ_91ZoCHUf4ZHj3UnKzP8pQU&typo=1" class="btn">
Component · Ref KC986Z
Affected pagehttps://hawaiianhost.com/products/choco-mango
Element#ProductPrice-15194142310771
Accessible name$3.50
Markup
<span id="ProductPrice-15194142310771" class="product__price">
              $3.50
            </span>
Component · Ref DCWW9O
Affected pagehttps://hawaiianhost.com/
Element.buttons-container > .btn
Accessible nameFind in Store
Markup
<a href="/blogs/news/ube-white-chocolate-now-available-across-hawai-i-and-the-west-coast" class="btn">
						Find in Store
					</a>
Low

Low-quality alternative text

WCAG 1.1.1 (A)28 instances5 inspected pages

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

Why it matters

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

Recommended correction

Replace placeholder or filename alt text with a concise description of what the image conveys.

View 28 affected elements
Component · Ref ZFH3NV
Affected pagehttps://hawaiianhost.com/products/choco-mango
Elementdiv:nth-of-type(1) > nav > menu > li:nth-of-type(3) > a > img:nth-of-type(1)
Markup
<img class="logo-alert" src="//hawaiianhost.com/cdn/shop/t/503/assets/hawaiian-host-logo-dark.png?v=30214439549601832641759882439" alt="Hawaiian Host Logo" width="" height="" loading="lazy">
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
Component · Ref F7OM53
Affected pagehttps://hawaiianhost.com/
Elementdiv:nth-of-type(6) > div:nth-of-type(1) > div:nth-of-type(1) > div:nth-of-type(2) > a > img
Markup
<img class="yotpo-lightbox-product-main-image" data-src="https://cdn-yotpo-images-production.yotpo.com/Product/236005436/169034048/original.png?1758132102" alt="Image link to product page">
Affected pages/ /account/login /products/choco-mango /pages/sign-up-for-email /cart
Low

Content sits outside any landmark region

WCAG 1.3.1 (A)1 instance1 inspected page

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

Why it matters

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

Recommended correction

Wrap primary content in <main> and other regions in appropriate landmark elements.

View 1 affected element
Component · Ref XE4AFL
Affected pagehttps://hawaiianhost.com/
Elementdiv:nth-of-type(1) > div > div > div > a > h2
Accessible nameParadise Collection Honey Milk Chocolate Bag
Markup
<h2 class="yotpo-lightbox-product-name">Paradise Collection Honey Milk Chocolate Bag  </h2>

05 · Most affected inspected pages

06 · About this assessment

Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.

  • Publicly accessible surfaces only — no credentials, private systems, or source-code access.
  • Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
  • Results reflect the site at the scan date and may have changed since.

Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment

07 · Continuous monitoring

This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.

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