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

Accessibility issues detected on alaskagearcompany.com

Evolize inspected 5 public pages on alaskagearcompany.com and detected 29 automatically identifiable accessibility findings.

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

Highest detected severity: Critical · 4 high-priority findings · 100% inspected-page coverage

Most widespread issueInteractive controls are not keyboard-accessibleDetected on 5 inspected pages
Most affected page/21 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)15 detected findings

Is alaskagearcompany.com your website?

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

ACTIVATE MONITORINGRUN A FREE ASSESSMENT
https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on alaskagearcompany.com and detected 29 accessibility findings. The most widespread issue was "Interactive controls are not keyboard-accessible", detected on 5 inspected pages. The most affected inspected page was "/", where 21 findings were detected. The assessment identified findings mapped to 5 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. Critical

    Embedded frames lack descriptive titles

    WCAG 4.1.2 (A) · 1 inspected page · 1 instance
    Why this matters

    An <iframe> has no title, so its purpose is not announced to assistive technology.

    Recommended action

    Add a concise title attribute that describes the frame's actual purpose — for example "Store locator" for a location search or "Promotional campaign" for a marketing embed. The affected frame loads https://forms.monday.com/forms/embed/c3e3d5fc4e2ff3e4aa7598aeb7f4ef0f?r=use1, which can help identify its purpose. Avoid generic values such as "Embedded content", "iframe", or "frame".

    View technical evidence →
  2. High

    Interactive controls are not keyboard-accessible

    WCAG 2.1.1 (A) · 5 inspected pages · 10 instances
    Why this 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 action

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

    View technical evidence →
  3. High

    Modal dialog does not trap keyboard focus

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

    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.

    Recommended action

    While a modal is open, confine focus to the dialog and mark the rest of the page inert (or aria-hidden). Restore focus on close.

    View technical evidence →
  4. High

    Interactive controls must not be nested

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

    Interactive controls must not be nested

    Recommended action

    Review the affected element and correct the reported accessibility issue.

    View technical evidence →
  5. Medium

    ARIA attributes have invalid values

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

    ARIA attributes reference ids that do not exist or hold invalid values, breaking the accessibility tree.

    Recommended action

    Correct ARIA attribute values and ensure referenced ids exist in the DOM.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA1544 / 5
2.4.3Focus OrderA755 / 5
4.1.2Name, Role, ValueA455 / 5
2.5.8Target Size (Minimum)AA255 / 5
2.1.1KeyboardA155 / 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.

ACTIVATE MONITORINGSEE PRICING

04 · All detected findings

Critical

Embedded frames lack descriptive titles

WCAG 4.1.2 (A)1 instance1 inspected page

An <iframe> has no title, so its purpose is not announced to assistive technology.

Why it matters

An <iframe> has no title, so its purpose is not announced to assistive technology.

Recommended correction

Add a concise title attribute that describes the frame's actual purpose — for example "Store locator" for a location search or "Promotional campaign" for a marketing embed. The affected frame loads https://forms.monday.com/forms/embed/c3e3d5fc4e2ff3e4aa7598aeb7f4ef0f?r=use1, which can help identify its purpose. Avoid generic values such as "Embedded content", "iframe", or "frame".

View 1 affected element
Component · Ref D75AIH
Affected pagehttps://alaskagearcompany.com/pages/partnership-inquiry-form
Elementiframe[width="650"]
Markup
<iframe src="https://forms.monday.com/forms/embed/c3e3d5fc4e2ff3e4aa7598aeb7f4ef0f?r=use1" width="650" height="500" style="border: 0; box-shadow: 5px 5px 56px 0px rgba(0,0,0,0.25);"></iframe>
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)10 instances5 inspected pages

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 10 affected elements
Component · Ref JYCODI
Affected pagehttps://alaskagearcompany.com/policies/contact-information
Elementli#annbar-localization-country-opt-0
Accessible nameUnited States (USD $)
Roleoption
Markup
<li class="custom-select__option flex items-center js-option" id="annbar-localization-country-opt-0" role="option" data-value="US" aria-selected="true">
          <span class="pointer-events-none">United States (USD&nbsp;$)</span>
          </li>
Affected pages/ /pages/contact /policies/contact-information /pages/partnership-inquiry-form /cart
High

Modal dialog does not trap keyboard focus

WCAG 2.4.3 (A)5 instances5 inspected pages

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.

Why it matters

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.

Recommended correction

While a modal is open, confine focus to the dialog and mark the rest of the page inert (or aria-hidden). Restore focus on close.

View 5 affected elements
Component · Ref 7UGVJO
Affected pagehttps://alaskagearcompany.com/cart
Elementhtml > body > div:nth-of-type(12) > div > div:nth-of-type(2)
Accessible namePOPUP Form
Roledialog
Markup
<div role="dialog" aria-modal="true" aria-label="POPUP Form" class="needsclick  kl-private-reset-css-Xuajs1" style="display: flex; z-index: 90000; position: fixed; left: 0px; top: 0px; width: 100%; height: 100%; justify-content: center; align-items: center; overflow: clip auto; background-color: rgba(20, 20, 20, 0.6); animation-timing-function: ease; animation-play-state: running; animation-iteration-count: 1; animation-fill-mode: forwards; animation-delay: 0s; animation-duration: 0.35s; animation-name: klaviyo-fadein;" data-kl-scroll-locking-modal="true"><div class="needsclick  kl-private-res…
Affected pages/ /pages/contact /policies/contact-information /pages/partnership-inquiry-form /cart
High

Interactive controls must not be nested

WCAG 4.1.2 (A)5 instances5 inspected pages

Interactive controls must not be nested

Why it matters

Interactive controls must not be nested

Recommended correction

Review the affected element and correct the reported accessibility issue.

View 5 affected elements
Component · Ref AYLDXY
Affected pagehttps://alaskagearcompany.com/
Element.HubLauncherButton-button-zMGOT
Accessible nameOpen chat
Markup
<button type="button" aria-label="Open chat" class="HubLauncherButton-bu..." style="--kl-local-widget-co...">
Affected pages/ /pages/contact /policies/contact-information /pages/partnership-inquiry-form /cart
Medium

ARIA attributes have invalid values

WCAG 4.1.2 (A)25 instances5 inspected pages

ARIA attributes reference ids that do not exist or hold invalid values, breaking the accessibility tree.

Why it matters

ARIA attributes reference ids that do not exist or hold invalid values, breaking the accessibility tree.

Recommended correction

Correct ARIA attribute values and ensure referenced ids exist in the DOM.

View 25 affected elements
Component · Ref Q2UPTI
Affected pagehttps://alaskagearcompany.com/policies/contact-information
Element#proxy-nav > .navigation__tier-1-container > .navigation__tier-1 > .navigation__item--with-mega-menu.navigation__item--with-children.navigation__item:nth-child(5) > a[aria-controls="NavigationTier2-5"][href$="sleds"][aria-haspopup="true"]
Accessible nameSleds
Markup
<a href="/collections/sleds" class="navigation__link" aria-haspopup="true" aria-expanded="false" aria-controls="NavigationTier2-5">Sleds</a>
Affected pages/ /pages/contact /policies/contact-information /pages/partnership-inquiry-form /cart
Medium

Touch targets are too small

WCAG 2.5.8 (AA)10 instances5 inspected pages

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

Why it matters

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

Recommended correction

Increase this <button>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper.

View 10 affected elements
Component · Ref D5VN5O
Affected pagehttps://alaskagearcompany.com/pages/partnership-inquiry-form
Element.HubLauncherButton-button-zMGOT
Accessible nameOpen chat
Markup
<button type="button" aria-label="Open chat" class="HubLauncherButton-bu..." style="--kl-local-widget-co...">
Affected pages/ /pages/contact /policies/contact-information /pages/partnership-inquiry-form /cart
Component · Ref YRU6CX
Affected pagehttps://alaskagearcompany.com/cart
Element.HubLauncherButton-messageContent-AfWf6
Accessible nameHi, I'm Denali, your Alaska Gear Company AI assistant. What can I help you with today?
Rolebutton
Markup
<div role="button" tabindex="0" class="HubLauncherButton-messageContent-AfWf6">
Affected pages/ /pages/contact /policies/contact-information /pages/partnership-inquiry-form /cart
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)23 instances4 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 23 affected elements
Component · Ref RX7EL8
Affected pagehttps://alaskagearcompany.com/
Element.article:nth-child(3) > .article__inner > .article__read-more-container > .small-feature-link[aria-hidden="true"]
Accessible nameRead more
Markup
<a class="small-feature-link" href="/blogs/field-journal/matt-williams-bush-pilot-profile" aria-hidden="true">Read more</a>
Component · Ref IDTE2I
Affected pagehttps://alaskagearcompany.com/policies/contact-information
Elementstrong
Accessible nameJoin the list for early access deals, Alaska stories, and $25 off your first order of $250 or more.
Markup
<strong style="font-weight: 700;">Join the list for early access deals, Alaska stories, and $25 off your first order of $250 or more.</strong>
Affected pages/policies/contact-information /cart
Component · Ref X9GE9M
Affected pagehttps://alaskagearcompany.com/policies/contact-information
Elementh1 > span > span
Accessible name$25 OFF YOUR FIRST ORDER
Markup
<span style="font-weight: 900;">$25 OFF YOUR FIRST ORDER</span>
Affected pages/policies/contact-information /cart
Component · Ref TMCVIN
Affected pagehttps://alaskagearcompany.com/
Element.image-overlay__image-link[href$="vbx-deck-boots"] > .text-overlay.text-overlay--v-bottom.text-overlay--h-left > .text-overlay__inner > .text-overlay__text > .text-overlay__title.h4
Accessible nameYour new Daily Driver
Markup
<h2 class="text-overlay__title h4">Your new Daily Driver</h2>
Component · Ref 9YVXGM
Affected pagehttps://alaskagearcompany.com/
Element.product-link[href$="bags"] > .image-overlay--edge-boxes.image-overlay.image-overlay--bg-full > .text-overlay--tight.text-overlay.text-overlay--v-bottom > .text-overlay__inner > .text-overlay__text > .text-overlay__title > .h4
Accessible nameBags
Markup
<h2 class="h4">Bags</h2>
Component · Ref 6A6FQX
Affected pagehttps://alaskagearcompany.com/
Element.image-overlay__image-link[href$="vbx-deck-boots"] > .text-overlay.text-overlay--v-bottom.text-overlay--h-left > .text-overlay__inner > .text-overlay__text > .text-overlay__subheading.subheading.subheading--over
Accessible nameAnkle Deck Boot VBX
Markup
<div class="text-overlay__subheading subheading subheading--over">Ankle Deck Boot VBX</div>
Component · Ref GXBA3Y
Affected pagehttps://alaskagearcompany.com/
Element.block-heading_N43LhF
Accessible nameNew Ankle Deck Boot VBX
Markup
<h2 class="text-overlay__title h1 block-heading_N43LhF">New Ankle Deck Boot VBX</h2>
Component · Ref YS7XUQ
Affected pagehttps://alaskagearcompany.com/pages/partnership-inquiry-form
Element.ai-hero-banner-heading-al2nlmvp1evdka3vwbaigenblock580a1a0m87wdb
Accessible namePartnership Inquiry Form
Markup
<h1 class="ai-hero-banner-heading-al2nlmvp1evdka3vwbaigenblock580a1a0m87wdb">Partnership Inquiry Form</h1>
Component · Ref DJFMOP
Affected pagehttps://alaskagearcompany.com/
Element.block-heading_dAjUWy
Accessible nameThe Alaska Camo Collection
Markup
<h2 class="text-overlay__title h1 block-heading_dAjUWy">The Alaska Camo Collection</h2>
Component · Ref 33ZMET
Affected pagehttps://alaskagearcompany.com/policies/contact-information
Element#rich-text-01KYTHBA46BAJV6MV05JQAAPJ7 > p > span
Accessible nameValid on first orders of $250 or more. Code will be sent to your inbox.
Markup
<span style="text-align: center; color: rgb(255, 255, 255);">Valid on first orders of $250 or more. Code will be sent to your inbox.</span>
Component · Ref QQJLA1
Affected pagehttps://alaskagearcompany.com/
Element.block-heading_pwcGxi
Accessible nameSerious Shelter for serious conditions
Markup
<h2 class="text-overlay__title h1 block-heading_pwcGxi">Serious Shelter for serious conditions</h2>
Component · Ref IVOKWB
Affected pagehttps://alaskagearcompany.com/
Elementa[href$="outdoor-gear"] > .image-overlay--edge-boxes.image-overlay.image-overlay--bg-full > .text-overlay--tight.text-overlay.text-overlay--v-bottom > .text-overlay__inner > .text-overlay__text > .text-overlay__title > .h4
Accessible nameCamp
Markup
<h2 class="h4">Camp</h2>
Component · Ref E5K6EO
Affected pagehttps://alaskagearcompany.com/
Element.block-heading_iWPkCd
Accessible nameGEAR. APPAREL. ACCESSORIES.
Markup
<h2 class="text-overlay__title h1 block-heading_iWPkCd">GEAR. APPAREL. ACCESSORIES.</h2>
Component · Ref 53VEWF
Affected pagehttps://alaskagearcompany.com/
Element.block-heading_K497aJ
Accessible nameWaterproof. Warm. Rugged.
Markup
<h2 class="text-overlay__title h1 block-heading_K497aJ">Waterproof. Warm. Rugged.</h2>
Component · Ref RI4QYB
Affected pagehttps://alaskagearcompany.com/
Element.block-heading_AUrCg8
Accessible nameNo Bad days
Markup
<h2 class="text-overlay__title h1 block-heading_AUrCg8">No Bad days</h2>
Medium

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)16 instances3 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 16 affected elements
Component · Ref 26IIOC
Affected pagehttps://alaskagearcompany.com/pages/contact
Elementdiv > div > location-switcher > div:nth-of-type(2) > div:nth-of-type(1) > button:nth-of-type(1)
Accessible nameAnchorage Store
Markup
<button type="button" class="btn btn--secondary map-section__location-btn is-active" data-location-btn="0" aria-pressed="true">Anchorage Store</button>
Affected pages/ /pages/contact
Component · Ref V3PB9X
Affected pagehttps://alaskagearcompany.com/
Elementlocation-switcher > div:nth-of-type(2) > div:nth-of-type(2) > div > p:nth-of-type(2) > a
Accessible name907-331-4847
Markup
<a href="tel:9073314847">907-331-4847</a>
Affected pages/ /pages/contact
Component · Ref 2T6XMN
Affected pagehttps://alaskagearcompany.com/
Elementdiv > div > div:nth-of-type(2) > div > div:nth-of-type(2) > a
Accessible nameRead more
Markup
<a class="small-feature-link" href="/blogs/field-journal/alaska-turkey-bomb" aria-hidden="true">Read more</a>
Affected pages/ /cart
Component · Ref 7330YJ
Affected pagehttps://alaskagearcompany.com/cart
Elementbutton#update-cart
Accessible nameCheckout
Markup
<button type="submit" class="btn btn--large" id="update-cart" name="checkout">Checkout</button>
Component · Ref VHTOF9
Affected pagehttps://alaskagearcompany.com/cart
Elementdiv:nth-of-type(2) > div > div:nth-of-type(2) > div > span > button
Accessible nameUpdate cart
Markup
<button type="submit" name="update">Update cart</button>
Component · Ref UFIHF0
Affected pagehttps://alaskagearcompany.com/cart
Elementtextarea#note
Markup
<textarea id="note" name="note"></textarea>
Medium

ARIA hidden element must not be focusable or contain focusable elements

WCAG 4.1.2 (A)3 instances1 inspected page

ARIA hidden element must not be focusable or contain focusable elements

Why it matters

ARIA hidden element must not be focusable or contain focusable elements

Recommended correction

Review the affected element and correct the reported accessibility issue.

View 3 affected elements
Component · Ref O8LGFM
Affected pagehttps://alaskagearcompany.com/
Element.article:nth-child(2) > .article__inner > .article__read-more-container > .small-feature-link[aria-hidden="true"]
Accessible nameRead more
Markup
<a class="small-feature-link" href="/blogs/field-journal/alaska-turkey-bomb" aria-hidden="true">Read more</a>

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.

ACTIVATE MONITORINGSEE PRICING

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