Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 2 REVIEW 7 FIX

Link & Button Quality

Action

11 issue(s) across 302 links and 31 buttons

FIX

11 issue(s) across 302 links and 31 buttons

8 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; /collections/royal-icing/products/royal-icing-gingerbread-men; /collections/royal-icing/products/royal-icing-gingerbread-men-36ct; /collections/royal-icing/products/royal-icing-assorted-poinsettias-12ct; /collections/royal-icing/products/royal-icing-santas-snacks-12-ct; /collections/royal-icing/products/easter-egg-assortment-royal-icing-decs-set-…; /collections/royal-icing/products/royal-icing-deck-the-halls12-ct; /collections/royal-icing/products/royal-icing-graduation-balloon-assortment-36ct

15 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.instagram.com/sprinklepop.shop/; https://www.facebook.com/sprinklepop.shop; https://www.youtube.com/channel/UCdjQz6FEU6bP2kZYSGnHnIw; https://twitter.com/sprinklepopshop?lang=en; https://www.pinterest.com/sprinklepopshop/pins/; https://www.tiktok.com/@sprinklepop?lang=en; https://www.linkedin.com/company/27094369/admin/; https://www.instagram.com/sprinklepop.shop/; https://www.facebook.com/sprinklepop.shop; https://www.youtube.com/channel/UCdjQz6FEU6bP2kZYSGnHnIw (+5 more)

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.collapsible-trigger (#139 on page); button.collapsible-trigger (#165 on page); button.btn (#1749 on page)

279 link(s) with descriptive text

302 links

8 empty

0 generic text

15 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://www.instagram.com/sprinklepop.sh…	instagram Instag…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/sprinklepop.sho…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCdjQz6F…	YouTube	new tab	Add '(opens in new tab)' to text
https://twitter.com/sprinklepopshop?lang…	twitter Twitter	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/sprinklepopsho…	Pinterest	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@sprinklepop?lang…	TikTok	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/2709436…	LinkedIn	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
/collections/royal-icing/products/royal-…	(empty)	empty	Add link text or aria-label
/collections/royal-icing/products/royal-…	(empty)	empty	Add link text or aria-label
/collections/royal-icing/products/royal-…	(empty)	empty	Add link text or aria-label
/collections/royal-icing/products/royal-…	(empty)	empty	Add link text or aria-label
/collections/royal-icing/products/easter…	(empty)	empty	Add link text or aria-label
/collections/royal-icing/products/royal-…	(empty)	empty	Add link text or aria-label
/collections/royal-icing/products/royal-…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/sprinklepop.sh…	instagram Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/sprinklepop.sho…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCdjQz6F…	YouTube	new tab	Add '(opens in new tab)' to text
https://twitter.com/sprinklepopshop?lang…	twitter Twitter	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/sprinklepopsho…	Pinterest	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@sprinklepop?lang…	TikTok	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/2709436…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.shopify.com?utm_campaign=pow…	Powered by Shopify	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

307 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; /collections/royal-icing/products/royal-icing-gingerbread-men; /collections/royal-icing/products/royal-icing-gingerbread-men-36ct; /collections/royal-icing/products/royal-icing-assorted-poinsettias-12ct; /collections/royal-icing/products/royal-icing-santas-snacks-12-ct; /collections/royal-icing/products/easter-egg-assortment-royal-icing-decs-set-…; /collections/royal-icing/products/royal-icing-deck-the-halls12-ct; /collections/royal-icing/products/royal-icing-graduation-balloon-assortment-36ct

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.instagram.com/sprinklepop.shop/; https://www.facebook.com/sprinklepop.shop; https://www.youtube.com/channel/UCdjQz6FEU6bP2kZYSGnHnIw; https://twitter.com/sprinklepopshop?lang=en; https://www.pinterest.com/sprinklepopshop/pins/; https://www.tiktok.com/@sprinklepop?lang=en; https://www.linkedin.com/company/27094369/admin/; https://www.instagram.com/sprinklepop.shop/; https://www.facebook.com/sprinklepop.shop; https://www.youtube.com/channel/UCdjQz6FEU6bP2kZYSGnHnIw (+5 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.collapsible-trigger (#139 on page); button.collapsible-trigger (#165 on page); button.btn (#1749 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Tap Target Adequacy

Action

11 tap target(s) too small or too close together

FIX

11 tap target(s) too small or too close together

11 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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #ff69b4

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Iframe Accessibility

3/3 iframe(s) missing title; 0 placeholder(s)

REVIEW

3/3 iframe(s) missing title; 0 placeholder(s)

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.

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.

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.

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (2 below threshold)

2 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: <label> 10.2px ("Enter your email"); <label> 10.2px ("Subscribe").

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 Sprinkle Pop
H2 Over 100 Mixes To Choose From!
H3 Made in the USA
H3 Always Free Shipping
H3 EXCLUSIVE COLORS
H2 Currency

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: 1 all-caps heading(s)

Alt Text Quality

1 of 26 images have issues

PASS

1 of 26 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

23 decorative image(s) correctly marked

2 image(s) with good alt text

26 images 2 good alt text 23 decorative 1 missing

Issue	Count
missing	1 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

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#CartNoteDrawer	textarea	Order note	for/id
#Search	search	Search	for/id
#Email-footer2	email	Enter your email	for/id

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

7 explicit tabindex attribute(s) checked, no anti-patterns

PASS

7 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title icon-X ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Over 100 Mixes To Ch…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Currency	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Made in the USA	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Always Free Shipping	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 EXCLUSIVE COLORS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Sprinkle Pop \| Trend…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Close menu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Shop	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Sprinkles	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cupcake Toppers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Icing Decorations	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Gel Colors & Dusts	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Molds & Pans	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Seasonal & New!	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a St. Patrick's Day	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Easter	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Sale	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Recipes	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Wholesale	21.00:1	4.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.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 21 passed

PASS

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.

Names and labels

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
div.header-layout > div.header-item > h1.site-header__logo > a.site-header__logo-link `div.header-layout > div.header-item > h1.site-header__logo > a.site-header__logo-link`
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link `div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link`
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link `div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link`
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link `div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link`
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link `div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link`
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link `div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link`
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link `div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link`
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link `div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link`
div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link `div.grid__item > div.grid-product__content > div.grid__item-image-wrapper > a.grid-product__link`

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

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
Sprinkle Points `div.footer__collapsible > ul.no-bullets > li > a`
Home `div.footer__collapsible > ul.no-bullets > li > a`
Wholesale `div.footer__collapsible > ul.no-bullets > li > a`
FAQ `div.footer__collapsible > ul.no-bullets > li > a`
About `div.footer__collapsible > ul.no-bullets > li > a`
Contact `div.footer__collapsible > ul.no-bullets > li > a`
Policies `div.footer__collapsible > ul.no-bullets > li > a`
Shipping Policy `div.footer__collapsible > ul.no-bullets > li > a`
Return Policy `div.footer__collapsible > ul.no-bullets > li > a`
Privacy Policy `div.footer__collapsible > ul.no-bullets > li > a`
Terms of Service `div.footer__collapsible > ul.no-bullets > li > a`

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

●`[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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

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

○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

○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.

○No element has a `[tabindex]` value greater than 0

○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.

○Elements with visible text labels have matching accessible names.

○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.