Skip to content
https://thelullabyclub.com.au

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
9
REVIEW
3
PASS
12
INFO
0
Checks
24
12 PASS 3 REVIEW 9 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 24 -1-on-focusable
FIX
0 positive, 24 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
Info::
tabindex="-1" on naturally-focusable <a>
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.)
D
Mobile-Readable Font Sizes
Action
65% of visible text renders at >= 12 CSS px (10 below threshold)
FIX
65% of visible text renders at >= 12 CSS px (10 below threshold)
Warning::
10 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("Facebook"); <span> 10.0px ("YouTube"); <span> 10.0px ("Instagram"); <span> 10.0px ("TikTok"); <label> 10.0px ("Country/Region").
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
2 icon(s) detected
FIX
2 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::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://thelullabyclub.com.au/web-pixels@49d3b31aw169a7c20pfc9cb2c9m68241e55/ap…")
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.
Warning::
<iframe> missing title attribute (src="")
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.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA
title The Lullaby Club | Functional Fashion fo…
1.21:1
#000000
on
#310F10
needs 4.5:1 (normal text)
16px · top of page (header area)
a Privacy Policy.
1.74:1
#000000
on
#71070D
needs 4.5:1 (normal text)
16px · top of page (header area)
span Manage preferences
1.80:1
#000000
on
#5B2B15
needs 4.5:1 (normal text)
16px · above the fold
button Accept
2.36:1
#000000
on
#6B3F22
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button Decline
2.65:1
#000000
on
#803F1C
needs 4.5:1 (normal text)
16px · above the fold
a Skip to content
3.08:1
#000000
on
#8C491C
needs 4.5:1 (normal text)
16px · above the fold
span Facebook
3.20:1
#000000
on
#8F4B20
needs 4.5:1 (normal text)
16px · above the fold
span YouTube
3.02:1
#000000
on
#884921
needs 4.5:1 (normal text)
16px · above the fold
span Instagram
2.96:1
#000000
on
#874723
needs 4.5:1 (normal text)
16px · above the fold
span TikTok
2.41:1
#000000
on
#763B1E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a join the club
3.26:1
#000000
on
#8C4F28
needs 4.5:1 (normal text)
16px · above the fold
div for 15% off
2.90:1
#000000
on
#84471E
needs 4.5:1 (normal text)
16px · mid-page
strong FREE EXPRESS
2.61:1
#000000
on
#7C4020
needs 3.0:1 (large text)
16px · mid-page · over background image/gradient
div Shipping on AU orders $200+
2.19:1
#000000
on
#6D3618
needs 4.5:1 (normal text)
16px · mid-page · 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 We value your privac…20.19:13.0:1
#000000
#FDFAF7
Pass
h2 New arrivals21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Real women. Real fit…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Up to 80% off21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Come see us21.00:13.0:1
#000000
#FFFFFF
Pass
title The Lullaby Club | F…1.21:14.5:1
#000000
#310F10
Fail
p We use cookies and o…8.34:14.5:1
#000000
#C39999
Pass
a Privacy Policy.1.74:14.5:1
#000000
#71070D
Fail
span Manage preferences1.80:14.5:1
#000000
#5B2B15
Fail
button Accept2.36:14.5:1
#000000
#6B3F22
Fail
button Decline2.65:14.5:1
#000000
#803F1C
Fail
a Skip to content3.08:14.5:1
#000000
#8C491C
Fail
span Facebook3.20:14.5:1
#000000
#8F4B20
Fail
span YouTube3.02:14.5:1
#000000
#884921
Fail
span Instagram2.96:14.5:1
#000000
#874723
Fail
span TikTok2.41:14.5:1
#000000
#763B1E
Fail
a join the club3.26:14.5:1
#000000
#8C4F28
Fail
div for 15% off2.90:14.5:1
#000000
#84471E
Fail
strong FREE EXPRESS2.61:13.0:1
#000000
#7C4020
Fail
div Shipping on AU order…2.19:14.5:1
#000000
#6D3618
Fail

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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 26 passed
REVIEW
85

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.

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
NEW div#tv2-template--27979341463625__mag_a > section.tv2-sec > div.tv2-tabs > button
DRESSES div#tv2-template--27979341463625__mag_a > section.tv2-sec > div.tv2-tabs > button
TOPS div#tv2-template--27979341463625__mag_a > section.tv2-sec > div.tv2-tabs > button
BESTSELLERS div#tv2-template--27979341463625__mag_a > section.tv2-sec > div.tv2-tabs > button
DAYS div.tv2-promo > div.tv2-promo__cd > span > i
HOURS div.tv2-promo > div.tv2-promo__cd > span > i
MINS div.tv2-promo > div.tv2-promo__cd > span > i
SECS div.tv2-promo > div.tv2-promo__cd > span > i
REDCLIFFE QLD section.tv2-sec > div.tv2-tiles > a.tv2-tile > p.tv2-eb
© 2026 THE LULLABY CLUB — ALL RIGHTS RESERVED. section#shopify-section-sections--27979343200329__tlc_footer_d3n83i > footer.tlc-footer--sections--27979343200329__tlc_footer_d3n83i > div.footer-bottom > p.footer-copyright
PRIVACY POLICY footer.tlc-footer--sections--27979343200329__tlc_footer_d3n83i > div.footer-bottom > div.footer-policy-links > a.footer-policy-link
TERMS OF SERVICE footer.tlc-footer--sections--27979343200329__tlc_footer_d3n83i > div.footer-bottom > div.footer-policy-links > a.footer-policy-link
SITEMAP footer.tlc-footer--sections--27979343200329__tlc_footer_d3n83i > div.footer-bottom > div.footer-policy-links > a.footer-policy-link
or 4 × with Afterpay div#tlc-qs-main > div.tlc-qs-header > div.tlc-qs-info > div.tlc-qs-afterpay

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Åland Islands (EUR €) Albania (ALL L) Andorra (EUR €) Armenia (AMD դր.) Austral… footer.tlc-footer--sections--27979343200329__tlc_footer_d3n83i > div.footer-localization > form.footer-country-form > select.footer-country-select

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.tv2-sec > div.tv2-story > div.tv2-story__imgs > a section.tv2-sec > div.tv2-story > div.tv2-story__imgs > a
section.tv2-sec > div.tv2-story > div.tv2-story__imgs > a section.tv2-sec > div.tv2-story > div.tv2-story__imgs > a
section.tv2-sec > div.tv2-story > div.tv2-story__imgs > a section.tv2-sec > div.tv2-story > div.tv2-story__imgs > a
section.tv2-sec > div.tv2-story > div.tv2-story__imgs > a section.tv2-sec > div.tv2-story > div.tv2-story__imgs > a
div.marquee > span.marquee-content > span.marquee-item > a div.marquee > span.marquee-content > span.marquee-item > a
div.marquee > span.marquee-content > span.marquee-item > a div.marquee > span.marquee-content > span.marquee-item > a
div.marquee > span.marquee-content > span.marquee-item > a div.marquee > span.marquee-content > span.marquee-item > a
div.marquee > span.marquee-content > span.marquee-item > a div.marquee > span.marquee-content > span.marquee-item > a
div.marquee > span.marquee-content > span.marquee-item > a div.marquee > span.marquee-content > span.marquee-item > a
div.marquee > span.marquee-content > span.marquee-item > a div.marquee > span.marquee-content > span.marquee-item > a
div.marquee > span.marquee-content > span.marquee-item > a div.marquee > span.marquee-content > span.marquee-item > a
div.marquee > span.marquee-content > span.marquee-item > a div.marquee > span.marquee-content > span.marquee-item > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
STEVIE PANTS › div.twl-template--27979341463625__worn > div.twl__grid > div.twl__item > a.twl__tile
KYLIE DRESS › div.twl-template--27979341463625__worn > div.twl__grid > div.twl__item > a.twl__tile
○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]`s are contained by their required parent element
●`[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
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○`<frame>` or `<iframe>` elements have a title
○`<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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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.
A+
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Primary" MAIN CONTENTINFO footer
A+
Heading Hierarchy
9 headings
PASS
9 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 We value your privacy
  • H1 (empty)
  • H2 Same gingham.Endless outfits.
  • H2 New arrivals
  • H2 Real women. Real fits.
  • H2 Dream alittle sweeter.
  • H2 Made forevery versionof you.
  • H3 Up to 80% off
  • H3 Come see us

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Heading Text Quality
All 9 heading(s) have substantive, well-formed text
PASS
All 9 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 248 images OK
PASS
All 248 images OK
Info::
129 decorative image(s) correctly marked
Info::
119 image(s) with good alt text
248 images 119 good alt text 129 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="country_code">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
qtextSearcharia-label
contact[email]emailEmail addressaria-label
country_codeselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="country_code">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
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+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
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::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback