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

Accessibility issues detected on rudysbarnyc.com

Evolize inspected 5 public pages on rudysbarnyc.com and detected 16 automatically identifiable accessibility findings.

16Findings detected
4WCAG criteria affected
5Pages inspected
8 Sep 2026Assessment date

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

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

Is rudysbarnyc.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 rudysbarnyc.com and detected 16 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 13 findings were detected. The assessment identified findings mapped to 4 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 · 20 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)AA755 / 5
2.4.3Focus OrderA555 / 5
1.3.1Info and RelationshipsA355 / 5
2.1.1KeyboardA111 / 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

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 1BC3TJ
Affected pagehttps://rudysbarnyc.com/
Elementul#MobileNav > li:nth-of-type(2) > a
Accessible nameShop
Markup
<a href="/collections/merchandise" class="mobile-nav__link">
                <span class="mobile-nav__label">Shop</span>
              </a>
Affected pages/ /pages/contact-us /products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat /cart
Component · Ref PYJS1W
Affected pagehttps://rudysbarnyc.com/
Elementdiv#SearchDrawer > div > div:nth-of-type(2) > button
Accessible nameClose search
Markup
<button type="button" class="btn--link search-bar__close js-drawer-close">
          <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon-close" viewBox="0 0 40 40"><path d="M23.868 20.015L39.117 4.78c1.11-1.108 1.11-2.77 0-3.877-1.109-1.108-2.773-1.108-3.882 0L19.986 16.137 4.737.904C3.628-.204 1.965-.204.856.904c-1.11 1.108-1.11 2.77 0 3.877l15.249 15.234L.855 35.248c-1.108 1.108-1.108 2.77 0 3.877.555.554 1.248.831 1.942.831s1.386-.277 1.94-.83l15.25-15.234 15.248 15.233c.555.554 1.248.831 1.941.831s1.387-.277 1.941-.83c1.11-1.109 1.11-2.77 0-3.878L23.868 20.015z" …
Affected pages/ /pages/contact-us /products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat /cart
Component · Ref UHT0BJ
Affected pagehttps://rudysbarnyc.com/products/hot-dog-hat
Elementhtml > body > div:nth-of-type(2) > div > div:nth-of-type(2) > button
Accessible nameContinue shopping
Markup
<button class="cart-popup__dismiss-button text-link text-link--accent" data-cart-popup-dismiss="">
        Continue shopping
      </button>
Affected pages/ /pages/contact-us /products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat /cart
Component · Ref 1QO5RE
Affected pagehttps://rudysbarnyc.com/collections/new-arrivals/products/hot-dog-hat
Elementhtml > body > div:nth-of-type(2) > div > button
Accessible nameClose
Markup
<button class="cart-popup__close" aria-label="Close" data-cart-popup-close=""><svg aria-hidden="true" focusable="false" role="presentation" class="icon icon-close" viewBox="0 0 40 40"><path d="M23.868 20.015L39.117 4.78c1.11-1.108 1.11-2.77 0-3.877-1.109-1.108-2.773-1.108-3.882 0L19.986 16.137 4.737.904C3.628-.204 1.965-.204.856.904c-1.11 1.108-1.11 2.77 0 3.877l15.249 15.234L.855 35.248c-1.108 1.108-1.108 2.77 0 3.877.555.554 1.248.831 1.942.831s1.386-.277 1.94-.83l15.25-15.234 15.248 15.233c.555.554 1.248.831 1.941.831s1.387-.277 1.941-.83c1.11-1.109 1.11-2.77 0-3.878L23.868 20.015z" class="…
Affected pages/ /pages/contact-us /products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat /cart
Component · Ref U1LZ7U
Affected pagehttps://rudysbarnyc.com/pages/contact-us
Elementdiv#SearchDrawer > div > div:nth-of-type(1) > form > button
Accessible nameSubmit
Markup
<button class="search-bar__submit search__submit btn--link" type="submit">
            <svg aria-hidden="true" focusable="false" role="presentation" class="icon icon-search" viewBox="0 0 37 40"><path d="M35.6 36l-9.8-9.8c4.1-5.4 3.6-13.2-1.3-18.1-5.4-5.4-14.2-5.4-19.7 0-5.4 5.4-5.4 14.2 0 19.7 2.6 2.6 6.1 4.1 9.8 4.1 3 0 5.9-1 8.3-2.8l9.8 9.8c.4.4.9.6 1.4.6s1-.2 1.4-.6c.9-.9.9-2.1.1-2.9zm-20.9-8.2c-2.6 0-5.1-1-7-2.9-3.9-3.9-3.9-10.1 0-14C9.6 9 12.2 8 14.7 8s5.1 1 7 2.9c3.9 3.9 3.9 10.1 0 14-1.9 1.9-4.4 2.9-7 2.9z"></path></svg>
            <span class="icon__fallback-text">Submit</span>
      …
Affected pages/ /pages/contact-us /products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat /cart
High

Interactive controls are not keyboard-accessible

WCAG 2.1.1 (A)1 instance1 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 1 affected element
Component · Ref DA7MID
Affected pagehttps://rudysbarnyc.com/cart
Elementdiv#dynamic-checkout-cart > shopify-accelerated-checkout-cart > div > ul > li > div
Rolebutton
Markup
<div class="wallet-cart-button wallet-cart-button__skeleton" role="button" disabled="" aria-hidden="true">&nbsp;</div>
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)39 instances5 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 39 affected elements
Component · Ref BGW8AX
Affected pagehttps://rudysbarnyc.com/
Element.search-header__input
Accessible nameSearch
Markup
<input class="search-header__input search__input" type="search" name="q" placeholder="Search" aria-label="Search">
Affected pages/ /pages/contact-us /products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat /cart
Component · Ref JJWETX
Affected pagehttps://rudysbarnyc.com/products/hot-dog-hat
Element.small--one-half.medium-up--one-quarter.grid__item:nth-child(3) > .grid-view-item.product-card[data-product-card-tracked="true"] > .grid-view-item__title.product-card__title.h4
Accessible nameRetro Pig Koozie – Rudy’s Bar & Grill Collapsible Can Cooler
Markup
<div class="h4 grid-view-item__title product-card__title" aria-hidden="true">Retro Pig Koozie – Rudy’s Bar &amp; Grill Collapsible Can Cooler</div>
Affected pages/products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat
Component · Ref 4R8WXS
Affected pagehttps://rudysbarnyc.com/products/hot-dog-hat
Element.small--one-half.medium-up--one-quarter.grid__item:nth-child(1) > .grid-view-item.product-card[data-product-card-tracked="true"] > dl > .price__regular > dd > .price-item--regular.price-item[data-regular-price=""]
Accessible name$58.00
Markup
<span class="price-item price-item--regular" data-regular-price="">
            $58.00
          </span>
Affected pages/products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat
Component · Ref 97PDGN
Affected pagehttps://rudysbarnyc.com/
Element.grid__item--featured-collections.small--one-half.medium-up--one-quarter:nth-child(2) > .grid-view-item.product-card[data-product-card-tracked="true"] > dl > .price__regular > dd > .price-item--regular.price-item[data-regular-price=""]
Accessible name$30.00
Markup
<span class="price-item price-item--regular" data-regular-price="">
            $30.00
          </span>
Component · Ref VGNWN7
Affected pagehttps://rudysbarnyc.com/
Element.grid__item--1633186976eba9e518.small--one-half.medium-up--one-quarter:nth-child(1) > .grid-view-item.product-card[data-product-card-tracked="true"] > .grid-view-item__title.product-card__title.h4
Accessible nameClassic Rudy’s Tee – Iconic NYC Dive Bar
Markup
<div class="h4 grid-view-item__title product-card__title" aria-hidden="true">Classic Rudy’s Tee – Iconic NYC Dive Bar</div>
Component · Ref DQRL8D
Affected pagehttps://rudysbarnyc.com/
Element.h1
Accessible nameHistoric Dive Bar in NYC Since 1933
Markup
<h2 class="h1 mega-title">Historic Dive Bar in NYC Since 1933</h2>
Component · Ref ACFHW8
Affected pagehttps://rudysbarnyc.com/
Element.mega-subtitle > p
Accessible nameCheap Beer and Free Hot Dogs with any purchase!
Markup
<p>Cheap Beer and Free Hot Dogs with any purchase!</p>
Medium

Content sits outside any landmark region

WCAG 1.3.1 (A)5 instances5 inspected pages

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 5 affected elements
Component · Ref VFRM99
Affected pagehttps://rudysbarnyc.com/
Elementdiv#shopify-section-header > div > a > p
Accessible nameShop the Summer 2026 Collection now. 🌭🇺🇸🍺
Markup
<p class="announcement-bar__message">Shop the Summer 2026 Collection now. 🌭🇺🇸🍺</p>
Affected pages/ /pages/contact-us /products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat /cart
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 0AAH46
Affected pagehttps://rudysbarnyc.com/products/hot-dog-hat
Elementnav#AccessibleNav
Accessible nameHome Shop History Photos Blog Contact Us
Rolenavigation
Markup
<nav class="grid__item medium-up--one-half small--hide" id="AccessibleNav" role="navigation">
          
<ul class="site-nav list--inline" id="SiteNav">
  



    
      <li>
        <a href="/" class="site-nav__link site-nav__link--main">
          <span class="site-nav__label">Home</span>
        </a>
      </li>
    
  



    
      <li>
        <a href="/collections/merchandise" class="site-nav__link site-nav__link--main">
          <span class="site-nav__label">Shop</span>
        </a>
      </li>
    
  



    
      <li>
        <a href="/pages/history" class="site-nav__link site-nav_…
Affected pages/ /pages/contact-us /products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat /cart
Component · Ref I372Q0
Affected pagehttps://rudysbarnyc.com/collections/new-arrivals/products/hot-dog-hat
Elementdiv#shopify-section-header > div > header > nav
Accessible nameHome Shop History Photos Blog Contact Us
Rolenavigation
Markup
<nav class="mobile-nav-wrapper medium-up--hide" role="navigation">
      <ul id="MobileNav" class="mobile-nav">
        
<li class="mobile-nav__item border-bottom">
            
              <a href="/" class="mobile-nav__link">
                <span class="mobile-nav__label">Home</span>
              </a>
            
          </li>
        
<li class="mobile-nav__item border-bottom">
            
              <a href="/collections/merchandise" class="mobile-nav__link">
                <span class="mobile-nav__label">Shop</span>
              </a>
            
          </li>
        
<li …
Affected pages/ /pages/contact-us /products/hot-dog-hat /collections/new-arrivals/products/hot-dog-hat /cart

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.