Public accessibility assessment

Accessibility issues detected on brokenarrowranch.com

Evolize inspected 4 public pages on brokenarrowranch.com and detected 21 automatically identifiable accessibility findings.

21Findings detected

5WCAG criteria affected

4Pages inspected

8 Sep 2026Assessment date

Highest detected severity: Critical · 6 high-priority findings · 80% inspected-page coverage

Most widespread issueHidden elements can still receive keyboard focusDetected on 4 inspected pages

Most affected page/account/login15 findings detected

Most represented WCAG criterionWCAG 1.3.1 — Info and Relationships10 detected findings

Is brokenarrowranch.com your website?

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

ACTIVATE MONITORING RUN A FREE ASSESSMENT

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 4 public pages on brokenarrowranch.com and detected 21 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 4 inspected pages. The most affected inspected page was "/account/login", where 15 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.

Critical
Form fields are missing labels
WCAG 1.3.1 (A) · 1 inspected page · 1 instance
Why this matters
Form inputs have no programmatically associated label, so assistive technology cannot announce what to enter.
Recommended action
Associate a <label> with each field via for/id, or use aria-label / aria-labelledby. Placeholder text is not a label.
View technical evidence →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 4 inspected pages · 12 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 →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 4 inspected pages · 12 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 →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 4 inspected pages · 8 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 →
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A) · 4 inspected pages · 4 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

Criterion	Name	Level	Findings	Pages	Reach
1.3.1	Info and Relationships	A	10	4	4 / 4
1.4.3	Contrast (Minimum)	AA	5	3	3 / 4
2.4.3	Focus Order	A	5	4	4 / 4
3.3.2	Labels or Instructions	A	2	1	1 / 4
4.1.2	Name, Role, Value	A	2	4	4 / 4

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

04 · All detected findings

Critical

Form fields are missing labels

WCAG 1.3.1 (A)1 instance1 inspected page

Form inputs have no programmatically associated label, so assistive technology cannot announce what to enter.

Why it matters

Form inputs have no programmatically associated label, so assistive technology cannot announce what to enter.

Recommended correction

Associate a <label> with each field via for/id, or use aria-label / aria-labelledby. Placeholder text is not a label.

View 1 affected element

Component · Ref UWWFDD

Affected pagehttps://brokenarrowranch.com/account/login

Elementinput[type="password"]

Markup

<input type="password" name="customer[password]" class="field">

High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)40 instances4 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 40 affected elements

Component · Ref IF5K18

Affected pagehttps://brokenarrowranch.com/cart

Elementdiv > div:nth-of-type(2) > div > div:nth-of-type(2) > div > a

Accessible nameView cart (0)

Markup

<a class="" href="/cart">
          <span class="main-header--tools-icon">
          
            


















































<svg class="svg-icon icon-bag " xmlns="http://www.w3.org/2000/svg" width="14" height="14" viewBox="0 0 14 14" aria-hidden="true">
  
  
  <path fill="currentColor" fill-rule="evenodd" d="M.86 3.92H13.1c.56 0 .92.45.8 1l-1.63 7.64c-.12.55-.67 1-1.22 1H2.5c-.56 0-1.1-.46-1.18-1L.02 4.9c-.1-.55.28-1 .84-1zm3.22-.57l.02-.1c0-.08.03-.18.06-.3.1-.3.2-.6.37-.88C5 1.27 5.73.8 6.8.85c1.08.04 1.8.5 2.26 1.24.17.22.3.53.38.83l.07.28.07.1.83-.1c0-.1-.05-.27-.…

Affected pages/ /account/login /pages/contact /cart

Component · Ref FYY3L7

Affected pagehttps://brokenarrowranch.com/account/login

Elementul#header-dropdown-buy-meats > li:nth-of-type(1) > a

Accessible nameWild Venison

Markup

<a href="/collections/wild-venison">
                  <span class="label">Wild Venison</span>
                  
                </a>

Affected pages/ /account/login /pages/contact /cart

Component · Ref FSSHIS

Affected pagehttps://brokenarrowranch.com/pages/contact

Elementsection > div > div:nth-of-type(2) > div > div:nth-of-type(1) > button

Accessible nameSearch

Markup

<button class="search" style="border: 0; background: none;">
        <span class="main-header--tools-icon">












































<svg aria-hidden="true" class="svg-icon icon-search " xmlns="http://www.w3.org/2000/svg" width="1229" height="1230" viewBox="0 0 1229 1230">
  
  
  <path fill="currentColor" d="M0 461c0-83.3 20.7-160.3 62-231s97.3-126.7 168-168S377.7 0 461 0s160.3 20.7 231 62 126.7 97.3 168 168 62 147.7 62 231c0 97.3-28 186-84 266l364 365c16.7 18 25.7 38 27 60v5c0 20-7 37.3-21 52-14 14-31.3 21-52 21h-5c-22.7-1.3-42.3-10.7-59-28L727 838c-80 56-168.7 84-266 84-8…

Affected pages/ /account/login /pages/contact /cart

Component · Ref W93YKJ

Affected pagehttps://brokenarrowranch.com/account/login

Elementsection > nav:nth-of-type(1) > div > ul > li:nth-of-type(2) > button

Accessible nameBuy Meats Menu

Markup

<button aria-haspopup="dialog" aria-expanded="false" aria-controls="header-mobile-dropdown-buy-meats" aria-label="Buy Meats Menu" class="menu-button icon" style="border: 0; background: none;">&lt;</button>

Affected pages/ /account/login /pages/contact /cart

Component · Ref N7I475

Affected pagehttps://brokenarrowranch.com/

Elementinput#search-input

Markup

<input id="search-input" class="search-input" name="q" type="text" placeholder="Search" value="">

Affected pages/ /account/login /pages/contact /cart

Medium

ARIA attributes have invalid values

WCAG 4.1.2 (A)4 instances4 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 4 affected elements

Component · Ref OYP7LP

Affected pagehttps://brokenarrowranch.com/cart

Elementli[aria-haspopup="true"]

Accessible nameMain menu

Markup

<li class="nav-item dropdown first" aria-haspopup="true" aria-controls="main-header--mobile-nav" aria-expanded="false" aria-label="Main menu">

Affected pages/ /account/login /pages/contact /cart

Medium

Navigation regions are not distinguishable

WCAG 1.3.1 (A)16 instances4 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 16 affected elements

Component · Ref EIPA2R

Affected pagehttps://brokenarrowranch.com/

Elementfooter#main-footer > div > nav

Accessible nameTwitter Facebook Instagram

Markup

<nav class="social">
        <aside class="social-links">
  <a href="http://www.twitter.com/brokenarrowrnch" class="social-link twitter" target="_blank">






















<svg class="svg-icon icon-twitter " xmlns="http://www.w3.org/2000/svg" width="32" height="32" viewBox="0 0 32 32">
  
  <title>Twitter</title>
  <path fill="currentColor" fill-rule="evenodd" d="M32 7c-1.2.6-2.4 1-3.8 1 1.4-.7 2.4-2 3-3.5-1.4.7-2.8 1.3-4.3 1.6-2-1-3-2-5-2-4 0-7 3-7 7v2c-5 0-10-3-13.6-7-.4 1-1 2-1 3.4 0 2 1.5 4 3 5.4-1 0-2-.3-3-1v.3c0 3 2.4 6 5.5 6l-1.8.6c-.4 0-.8 0-1.2-.2C4 23 6.7 25 9.4 25c-2 1.8-5 2.8-8…

Affected pages/ /account/login /pages/contact /cart

Component · Ref AK56W6

Affected pagehttps://brokenarrowranch.com/pages/contact

Elementdiv#shopify-section-static-header > header > section > nav:nth-of-type(1)

Accessible nameHome Buy Meats < Wild Venison Wild Boar Texas Quail Wild Game Sausages Farmed Venison Combination Packages Pet Products Expedited Shipping Gift Cards About < We Believe Our Story Our Process Recipes < Venison Wild Boar Quail Offal Sauces Stocks Rubs All Recipes Cooking Tips & Info Articles & Info < Resources Press Answers For Restaurants < Wholesale Product List Request Wholesale Price List Restaurant Waiter Guides Serving Ideas For Land Owners

Markup

<nav class="full bordered">
  
    <div class="content-area">
  

  
  

  <ul class="main-header--nav-links"><li class="
          nav-item
          first
          
          
          
        ">
        
        <a class="label" href="/">
          Home
        </a>
        <!-----Sana Kapasi Comment Start----->
          
        <!-----Sana Kapasi Comment End----->

        
        
        

      </li><li class="
          nav-item
          
          
          dropdown
          
        ">
        
          <span class="border"></span>
        
        <a class="label" href="/c…

Affected pages/ /account/login /pages/contact /cart

Component · Ref Y5N4AL

Affected pagehttps://brokenarrowranch.com/cart

Elementdiv#shopify-section-static-cart > section > nav

Markup

<nav class="breadcrumb-navigation">
  
</nav>

Affected pages/account/login /cart

Component · Ref 4IWMXK

Affected pagehttps://brokenarrowranch.com/pages/contact

Elementdiv#shopify-section-static-page-contact > div > main > nav

Accessible nameHome / Contact Us

Markup

<nav class="breadcrumb-navigation">
  
  <ol>
    <li><a href="/">Home</a></li>
    
      <li><span aria-hidden="true" class="sep">/</span> Contact Us</li>
    
  </ol>
  
</nav>

Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)8 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 8 affected elements

Component · Ref TS80GO

Affected pagehttps://brokenarrowranch.com/

Elementcsm-cookie-consent,#isense-cc-cookie-bar-text

Markup

<span id="isense-cc-cookie-bar-text" tabindex="-1" data-csm-description="true" class="a48BBEL2Cpzl0dxNZ7ji">This website uses cookies to ensure you get the best experience on our website.</span>

Affected pages/ /pages/contact /cart

Component · Ref FBOSHZ

Affected pagehttps://brokenarrowranch.com/

Elementp:nth-child(3) > a[href$="recipe"]

Accessible namehow to cook it

Markup

<a href="/blogs/recipes/tagged/recipe">how to cook it</a>

Component · Ref 6X4N30

Affected pagehttps://brokenarrowranch.com/

Element.call-to-action

Accessible nameStart Shopping

Markup

<a class="call-to-action" href="/collections">
                  Start Shopping
                </a>

Component · Ref IMO1PU

Affected pagehttps://brokenarrowranch.com/

Element.content > p:nth-child(3)

Accessible nameLearn more about your protein and how to cook it.

Markup

<p><a href="/pages/we-believe">Learn more</a> about your protein and <a href="/blogs/recipes/tagged/recipe">how to cook it</a>.</p>

Component · Ref AW1554

Affected pagehttps://brokenarrowranch.com/

Elementh1

Accessible namePure, Wild Meat to Your Table

Markup

<h1 class="title">Pure, Wild Meat to Your Table</h1>

Medium

Page has no main landmark

WCAG 1.3.1 (A)2 instances2 inspected pages

No <main> or role=main region is present, so screen reader users cannot jump to primary content.

Why it matters

No <main> or role=main region is present, so screen reader users cannot jump to primary content.

Recommended correction

Wrap the primary content in a single <main> element or role=main region.

View 2 affected elements

Component · Ref KLPZW1

Affected pagehttps://brokenarrowranch.com/account/login

Elementhtml > body

Accessible name(function(d, s, id) { var js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=187795038002910"; fjs.parentNode.insertBefore(js, fjs); }(document, 'script', 'facebook-jssdk')); Skip to content Search Search: View cart (0) Login Home Buy Meats < Wild Venison Wild Boar Texas Quail Wild Game Sausages Farmed Venison Combination Packages Pet Products Expedited Shipping Gift Cards About < We Believe Our Story Our Process Recipes < Venison Wild Boar Quail Offal Sauces Stocks Rubs All Recipes Cooking Tips & Info Articles & Info < Resources Press Answers For Restaurants < Wholesale Product List Request Wholesale Price List Restaurant Waiter Guides Serving Ideas For Land Owners …[truncated by Evolize: exceeded D1 value limit]

Markup

<body class="
    template-login
    product-grid-default
  ">
  <div id="fb-root" class=" fb_reset"><div style="position: absolute; top: -10000px; width: 0px; height: 0px;"><div></div></div></div>
  <script>(function(d, s, id) {
    var js, fjs = d.getElementsByTagName(s)[0];
    if (d.getElementById(id)) return;
    js = d.createElement(s); js.id = id;
    js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=187795038002910";
    fjs.parentNode.insertBefore(js, fjs);
  }(document, 'script', 'facebook-jssdk'));</script>

  



<section class="quickshop" data-quickshop="" data-quickshop…

Affected pages/account/login /cart

Medium

Form fields use placeholder text as the only label

WCAG 1.3.1 (A)2 instances1 inspected page

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Why it matters

Fields rely on placeholder text instead of a real label. The placeholder disappears once the user types, and it is not exposed as a programmatic label.

Recommended correction

Add a persistent <label> associated with each field. Keep the placeholder for example text only, not as the label.

View 2 affected elements

Component · Ref 36USB3

Affected pagehttps://brokenarrowranch.com/account/login

Elementdiv#recover-password > form > div > input

Markup

<input type="text" placeholder="[email removed]" value="" name="email" class="field">

Component · Ref 80P2J9

Affected pagehttps://brokenarrowranch.com/account/login

Elementform#customer_login > div:nth-of-type(1) > input

Markup

<input type="text" placeholder="[email removed]" value="" name="customer[email]" class="field">

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 7DSGEP

Affected pagehttps://brokenarrowranch.com/account/login

Elementdiv#customer-login

Accessible nameEmail Password Forgot your password? New customer? Sign up for an account

Markup

<div id="customer-login" class="account-form">
    <form method="post" action="/account/login" id="customer_login" accept-charset="UTF-8" data-login-with-shop-sign-in="true"><input type="hidden" name="form_type" value="customer_login"><input type="hidden" name="utf8" value="✓">

      

      <div class="field-wrap email">
        <label>Email</label>
        <input type="text" placeholder="[email removed]" value="" name="customer[email]" class="field">
      </div>

      <div class="field-wrap password">
        <label>Password</label>
        <input type="password" name="customer[password]" …

Low

Page has no level-one heading

WCAG 1.3.1 (A)1 instance1 inspected page

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

Why it matters

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

Recommended correction

Add a single descriptive <h1> that names the page's primary purpose.

View 1 affected element

Component · Ref G9VK52

Affected pagehttps://brokenarrowranch.com/account/login

Elementhtml > body

Markup

<body class="
    template-login
    product-grid-default
  ">
  <div id="fb-root" class=" fb_reset"><div style="position: absolute; top: -10000px; width: 0px; height: 0px;"><div></div></div></div>
  <script>(function(d, s, id) {
    var js, fjs = d.getElementsByTagName(s)[0];
    if (d.getElementById(id)) return;
    js = d.createElement(s); js.id = id;
    js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=187795038002910";
    fjs.parentNode.insertBefore(js, fjs);
  }(document, 'script', 'facebook-jssdk'));</script>

  



<section class="quickshop" data-quickshop="" data-quickshop…

05 · Most affected inspected pages

/account/login
Critical
21 findings
- Critical Form fields are missing labels
- High Hidden elements can still receive keyboard focus
- Medium ARIA attributes have invalid values
- Medium Form fields use placeholder text as the only label
- Medium Navigation regions are not distinguishable
- Medium Page has no main landmark
- Low Content sits outside any landmark region
- Low Page has no level-one heading
/
High
14 findings
- High Hidden elements can still receive keyboard focus
- Medium ARIA attributes have invalid values
- Medium Navigation regions are not distinguishable
- Medium Text has insufficient colour contrast
/cart
High
14 findings
- High Hidden elements can still receive keyboard focus
- Medium ARIA attributes have invalid values
- Medium Navigation regions are not distinguishable
- Medium Page has no main landmark
- Medium Text has insufficient colour contrast
/pages/contact
High
11 findings
- High Hidden elements can still receive keyboard focus
- Medium ARIA attributes have invalid values
- Medium Navigation regions are not distinguishable
- Medium Text has insufficient colour contrast

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 MONITORING SEE PRICING

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

Accessibility issues detected on brokenarrowranch.com

Is brokenarrowranch.com your website?

01 · Accessibility summary

02 · Start here

Form fields are missing labels

Hidden elements can still receive keyboard focus

Hidden elements can still receive keyboard focus

Hidden elements can still receive keyboard focus

Hidden elements can still receive keyboard focus

03 · WCAG criteria affected

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

04 · All detected findings

Form fields are missing labels

Hidden elements can still receive keyboard focus

ARIA attributes have invalid values

Navigation regions are not distinguishable

Text has insufficient colour contrast

Page has no main landmark

Form fields use placeholder text as the only label

Content sits outside any landmark region

Page has no level-one heading

05 · Most affected inspected pages

06 · About this assessment

07 · Continuous monitoring

Reports with similar accessibility findings