Skip to content
https://castleware.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 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 <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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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.
B
Alt Text Quality
2 of 83 images have issues
REVIEW
2 of 83 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
15 image(s) with alt text over 125 characters
Info::
43 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
83 images 23 good alt text 43 decorative 2 missing
IssueCount
missing2 image(s)
too long15 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

C
Tap Target Adequacy
Action
9 tap target(s) too small or too close together
REVIEW
9 tap target(s) too small or too close together
Warning::
9 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
Mobile-Readable Font Sizes
Action
85% of visible text renders at >= 12 CSS px (8 below threshold)
REVIEW
85% of visible text renders at >= 12 CSS px (8 below threshold)
Warning::
8 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> 11.0px ("Previous"); <p> 11.0px ("Free shipping on orders over $75"); <span> 11.0px ("Next"); <span> 11.0px ("(4.8)"); <span> 11.0px ("(4.8)").
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 9 fail WCAG AA
REVIEW

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

11 pass 9 fail WCAG AA
h2 Shop the look
1.22:1
#000000
on
#1B1B1B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What Parents Are Saying
1.22:1
#000000
on
#1B1B1B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 @castleware
1.22:1
#000000
on
#1B1B1B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 From the blog
1.22:1
#000000
on
#1B1B1B
needs 3.0:1 (large text)
24px · bottom of viewport
title CastleWare | Heirloom-Quality USA-Made O…
1.48:1
#000000
on
#2B2B2B
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.82:1
#000000
on
#393939
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
span Previous
3.00:1
#000000
on
#595959
needs 4.5:1 (normal text)
16px · top of page (header area)
p 100% Organic Cotton • Made in USA …
3.00:1
#000000
on
#595959
needs 4.5:1 (normal text)
16px · top of page (header area)
p Free shipping on orders over $75
1.69:1
#000000
on
#343434
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 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 Shop the look1.22:13.0:1
#000000
#1B1B1B
Fail
h2 What Parents Are Say…1.22:13.0:1
#000000
#1B1B1B
Fail
h2 @castleware1.22:13.0:1
#000000
#1B1B1B
Fail
h2 From the blog1.22:13.0:1
#000000
#1B1B1B
Fail
title CastleWare | Heirloo…1.48:14.5:1
#000000
#2B2B2B
Fail
a Skip to content1.82:14.5:1
#000000
#393939
Fail
span Previous3.00:14.5:1
#000000
#595959
Fail
p 100% Organic Cotton …3.00:14.5:1
#000000
#595959
Fail
p Free shipping on ord…1.69:14.5:1
#000000
#343434
Fail
span Next21.00:14.5:1
#000000
#FFFFFF
Pass
span CastleWare21.00:14.5:1
#000000
#FFFFFF
Pass
span Navigation menu21.00:14.5:1
#000000
#FFFFFF
Pass
a Ready to Ship21.00:14.5:1
#000000
#FFFFFF
Pass
summary New & Featured21.00:14.5:1
#000000
#FFFFFF
Pass
a Newborn Collection21.00:14.5:1
#000000
#FFFFFF
Pass
a Natural (Undyed) Col…21.00:14.5:1
#000000
#FFFFFF
Pass
a Black Forest Collect…21.00:14.5:1
#000000
#FFFFFF
Pass
a Organic Cotton Fleec…21.00:14.5:1
#000000
#FFFFFF
Pass
a Organic Cotton Rib K…21.00:14.5:1
#000000
#FFFFFF
Pass
summary Sleeper Bags21.00:14.5:1
#000000
#FFFFFF
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 30 passed
REVIEW
89

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
$62.00 div.v-stack > price-list.price-list > sale-price.h6 > span.money
(4.8) product-card.product-card > div.product-card__info > span.rating-badge > span.smallcaps
$64.00 div.v-stack > price-list.price-list > sale-price.h6 > span.money
(4.8) product-card.product-card > div.product-card__info > span.rating-badge > span.smallcaps
$55.00 div.v-stack > price-list.price-list > sale-price.h6 > span.money
(5.0) product-card.product-card > div.product-card__info > span.rating-badge > span.smallcaps
$95.00 div.v-stack > price-list.price-list > sale-price.h6 > span.money
(5.0) product-card.product-card > div.product-card__info > span.rating-badge > span.smallcaps
CASTLEWARE div.color-scheme > div.container > div.prose > p.h1
Welcome to the cozy corner of CastleWare! As a mom, I understand the deep desir… div.container > div.prose > div > p
🇺🇸 Made in USA, Fiber to Finish 🌿 100% GOTS Certified Organic Cotton 🌎 No Harsh … div.prose > div > p > strong
CLEAN . HONEST . CRAFTSMANSHIP . div.section-spacing > marquee-text.scrolling-content > div.scrolling-content__item > p.scrolling-content__text
Our Company div.v-stack > ul.v-stack > li > a.link-faded
Our Fabrics div.v-stack > ul.v-stack > li > a.link-faded
Contact div.v-stack > ul.v-stack > li > a.link-faded
Buy a Gift Card div.v-stack > ul.v-stack > li > a.link-faded
FAQ div.v-stack > ul.v-stack > li > a.link-faded
Shipping and Handling div.v-stack > ul.v-stack > li > a.link-faded
Returns and Exchanges div.v-stack > ul.v-stack > li > a.link-faded
Terms of Use div.v-stack > ul.v-stack > li > a.link-faded
Privacy Policy div.v-stack > ul.v-stack > li > a.link-faded
Blog div.v-stack > ul.v-stack > li > a.link-faded
Loyalty Program div.v-stack > ul.v-stack > li > a.link-faded
Affiliate Program div.v-stack > ul.v-stack > li > a.link-faded
Sign up to our newsletter to receive exclusive offers. div.footer__block > div.v-stack > div.prose > p
© 2026 - CASTLEWARE div.container > div.footer__inner > div.footer__aside > p.heading
10/09/2026 div.scroll > div.stamped-drawer-product-reviews > div.stamped-ratings-wrapper > div.stamped-reviews-date
REVIEWS div#stamped-reviews-widget > div#stamped-widget-drawer > div.stamped-widget-button > div.vertical-text
CWB Rewards div.cp-launcher-btn > span.cp-launcher-label > span.editable-container > span.editable

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.lg-item > div.lg-video-cont > div.lg-video > iframe.lg-object div.lg-item > div.lg-video-cont > div.lg-video > iframe.lg-object

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GETTING STARTED IS EASY. EARN POINTS AND GET REWAREDED IN A FEW EASY STEPS. div.content > div.prose > div > h6

These are opportunities to improve keyboard navigation in your application.

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
Go to item 2 section#shopify-section-template--26492696822007__slideshow > slideshow-carousel#carousel-template--26492696822007__slideshow > carousel-navigation.page-dots > button.tap-area
Go to item 1 div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area
Go to item 2 div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area
Go to item 3 div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area
Go to item 4 div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area
Go to item 5 div.section-stack > div.testimonial-list > carousel-navigation.page-dots > button.tap-area
Go to item 1 images-with-text-scroll#section-carousel-template--26492696822007__images-with-text-scroll > div.images-with-text-scroll__container > carousel-navigation.page-dots > button.tap-area
Go to item 2 images-with-text-scroll#section-carousel-template--26492696822007__images-with-text-scroll > div.images-with-text-scroll__container > carousel-navigation.page-dots > button.tap-area
Go to item 3 images-with-text-scroll#section-carousel-template--26492696822007__images-with-text-scroll > div.images-with-text-scroll__container > carousel-navigation.page-dots > button.tap-area

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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●ARIA toggle fields have accessible names
●Document has a `<title>` element
●`<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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 `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
○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.
○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
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary navigation" MAIN ASIDE CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

A
Heading Hierarchy
12 headings, 1 skip(s)
PASS
12 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 CastleWare
  • H2 Shop the look
  • H2 💬 What Parents Are Saying
  • H2 @castleware
  • H2 From the blog
  • H6 Getting started is easy. Earn points and get rewareded in a few easy steps. skipped
  • H6 1. Join Us
  • H6 Earn points on every order.
  • H6 2. Start Earning
  • H6 Complete challenges like following us on Instagram to stack up points.
  • H6 3. Get Rewarded
  • H6 As you earn points, you can redeem them for discounts.

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Heading Text Quality
All 12 heading(s) have substantive, well-formed text
PASS
All 12 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearchSearcharia-label
#input--sections--26492697477367__footer--contactemailemailE-mailfor/id
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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
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://www.youtube.com/embed/uH4kE1kZhSk?playsinline=1&autoplay=1&controls=0&m…")
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
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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