Skip to content
https://farmgirlsfancyfrills.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
8
REVIEW
3
PASS
13
INFO
0
Checks
24
13 PASS 3 REVIEW 8 FIX
D
Mobile Keyboard & Autofill
Action
3/4 eligible field(s) missing autocomplete or inputmode
FIX
3/4 eligible field(s) missing autocomplete or inputmode
Warning::
3 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.
Got: <input type="search" name="q" id="Search">, <input type="email" name="contact[email]" id="Email-newsletter">, <input type="email" name="email" id="email_01M5EAPFCSJ6SYTMS49M86MZPB">
F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #61a0a1
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Alt Text Quality
Action
6 of 79 images have issues
REVIEW
6 of 79 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
46 decorative image(s) correctly marked
Info::
27 image(s) with good alt text
79 images 27 good alt text 46 decorative 6 missing
IssueCount
missing6 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

13 pass 7 fail WCAG AA 3 pass AA only
span No code needed. Final sale.
1.29:1
#000000
on
#251F1D
needs 4.5:1 (normal text)
16px · above the fold
span SHIPS FROM USA • FREE $99+
2.48:1
#000000
on
#72402B
needs 4.5:1 (normal text)
16px · above the fold
span ORDER BY 12 PM CST, SHIPS TODAY
2.71:1
#000000
on
#744830
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Easy 30-day Exchanges & Returns
4.02:1
#000000
on
#975E4B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Not quite right? Swap size or style, or …
2.05:1
#000000
on
#4E3D37
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Close menu
2.70:1
#000000
on
#5F503E
needs 4.5:1 (normal text)
16px · above the fold
a New Arrivals
4.42:1
#000000
on
#747277
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 New Arrivals19.95:13.0:1
#000000
#F9F9F9
Pass
h2 Spooky cute19.95:13.0:1
#000000
#F9F9F9
Pass
h2 REAL WOMEN. REAL REV…19.95:13.0:1
#000000
#F9F9F9
Pass
h2 SCAN TO GET THE APP …19.95:13.0:1
#000000
#F9F9F9
Pass
h3 Let customers speak …19.95:13.0:1
#000000
#F9F9F9
Pass
title Farm Girls Fancy Fri…6.64:14.5:1
#000000
#5E9B9C
Pass
a Skip to content6.63:14.5:1
#000000
#5D9B9B
Pass
span Pause slideshow13.08:14.5:1
#000000
#B8D1D1
Pass
span Play slideshow19.09:14.5:1
#000000
#F4F4F4
Pass
span Halloween Collectio…19.09:14.5:1
#000000
#F4F4F4
Pass
span No code needed. Fina…1.29:14.5:1
#000000
#251F1D
Fail
span SHIPS FROM USA • F…2.48:14.5:1
#000000
#72402B
Fail
span ORDER BY 12 PM CST, …2.71:14.5:1
#000000
#744830
Fail
span Easy 30-day Exchange…4.02:14.5:1
#000000
#975E4B
Fail
span Not quite right? Swa…2.05:14.5:1
#000000
#4E3D37
Fail
span Close menu2.70:14.5:1
#000000
#5F503E
Fail
a New5.70:14.5:1
#000000
#958270
Pass
a New Arrivals4.42:14.5:1
#000000
#747277
Fail
a Best Sellers18.93:14.5:1
#000000
#F3F3F3
Pass
a Halloween 🎃18.93:14.5:1
#000000
#F3F3F3
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" MAIN ASIDE "Mobile app download widget" CONTENTINFO footer
A
Heading Hierarchy
15 headings
PASS
15 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Farm Girls Fancy Frills
  • H2 New Arrivals
  • H2 Christmas Is Coming
  • H2 Halloween Collection Sale
  • H2 Farm Girl Originals
  • H2 Bargain Barn
  • H2 New Arrivals
  • H2 Spooky cute
  • H2 Necklaces
  • H2 Earrings
  • H2 Bracelets
  • H2 REAL WOMEN. REAL REVIEWS.
  • H3 Let customers speak for us
  • H2 SCAN TO GET THE APP & EXCLUSIVE DEALS
  • H1 15% OFF duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 3 all-caps heading(s)
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#SearchsearchSearchfor/id
#Email-newsletteremailEnter your emailfor/id
selectselectSort bynone
#email_01M5EAPFCSJ6SYTMS49M86MZPBemailEmailfor/id
A+
Form Input Types
4 form control(s) checked, no type mismatches
PASS
4 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://farmgirlsfancyfrills.com/web-pixels@49d3b31aw169a7c20pfc9cb2c9m68241e55…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Mobile-Readable Font Sizes
All 37 visible text node(s) render at >= 12 CSS pixels
PASS
All 37 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 28 passed
PASS
90

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
FALL & HOLIDAY NEW ARRIVALS NEW ARRIVALS div#Slideshow-template--28608343015718__slideshow > div.flickity-viewport > div.flickity-slider > div.slideshow__slide
CHRISTMAS IS COMING Get festive! Shop early for the best selection. SHOP CHRIST… div#Slideshow-template--28608343015718__slideshow > div.flickity-viewport > div.flickity-slider > div.slideshow__slide
HALLOWEEN COLLECTION SALE 30% OFF SHOP HALLOWEEN div#Slideshow-template--28608343015718__slideshow > div.flickity-viewport > div.flickity-slider > div.slideshow__slide
FARM GIRL ORIGINALS Handmade by us — unique pieces just for you. SHOP ORIGINALS div#Slideshow-template--28608343015718__slideshow > div.flickity-viewport > div.flickity-slider > div.slideshow__slide
div.flickity-viewport > div.flickity-slider > div.slideshow__slide > a.hero__slide-link div.flickity-viewport > div.flickity-slider > div.slideshow__slide > a.hero__slide-link
div > div#Slideshow-template--28608343015718__slideshow_e9HNQY > div.slideshow__slide > a.hero__slide-link div > div#Slideshow-template--28608343015718__slideshow_e9HNQY > div.slideshow__slide > a.hero__slide-link

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SHIPS FROM USA • FREE $99+ div.flickity-viewport > div.flickity-slider > div#AnnouncementSlide-announcement-0 > span.announcement-text
ORDER BY 12 PM CST, SHIPS TODAY div.flickity-viewport > div.flickity-slider > div#AnnouncementSlide-announcement-0 > span.announcement-link-text
New div.footer__collapsible > ul.no-bullets > li > a
Tops div.footer__collapsible > ul.no-bullets > li > a
Bottoms div.footer__collapsible > ul.no-bullets > li > a
Dresses div.footer__collapsible > ul.no-bullets > li > a
Rompers & Overalls div.footer__collapsible > ul.no-bullets > li > a
Accessories div.footer__collapsible > ul.no-bullets > li > a
Shop By Brand div.footer__collapsible > ul.no-bullets > li > a
Sale div.footer__collapsible > ul.no-bullets > li > a
About Us div.footer__collapsible > ul.no-bullets > li > a
Customer Reviews div.footer__collapsible > ul.no-bullets > li > a
FAQ div.footer__collapsible > ul.no-bullets > li > a
Rewards Program div.footer__collapsible > ul.no-bullets > li > a
Size Guide div.footer__collapsible > ul.no-bullets > li > a
Search div.footer__collapsible > ul.no-bullets > li > a
Contact Us div.footer__collapsible > ul.no-bullets > li > a
Privacy Policy div.footer__collapsible > ul.no-bullets > li > a
Refund Policy div.footer__collapsible > ul.no-bullets > li > a
Shipping & Store Pick-Up div.footer__collapsible > ul.no-bullets > li > a
Terms of Service div.footer__collapsible > ul.no-bullets > li > a
Your Privacy Choices div.footer__collapsible > ul.no-bullets > li > a
Be the first to know about our new arrivals, restocks and best sales. div > div.collapsible-content__inner > div.footer__collapsible > p
div.footer__collapsible > form#newsletter-footer > div.footer__newsletter > input#Email-newsletter div.footer__collapsible > form#newsletter-footer > div.footer__newsletter > input#Email-newsletter
Powered by Shopify footer.site-footer > div.page-width > p.footer__small-text > a

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close teaser div > div.needsclick > div.needsclick > button.needsclick

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback