Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 6 REVIEW 6 FIX

Alt Text Quality

Action

3 of 13 images have issues

FIX

3 of 13 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

1 image(s) with alt text over 125 characters

4 decorative image(s) correctly marked

5 image(s) with good alt text

13 images 5 good alt text 4 decorative 3 missing

Issue	Count
missing	3 image(s)
too long	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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

12 issue(s) across 94 links and 7 buttons

FIX

12 issue(s) across 94 links and 7 buttons

5 link(s) with no accessible text

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

Got: /; /; /category/Homewares; /category/BAM-Sunglasses-Bamboo; /category/Reed-Diffusers

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /discover-passionfish ("Read More")

7 link(s) open in new tab without warning

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

Got: tel:02 4473 7714; tel:02 4473 7714; /product/Organic-Hemp-Massage-Oil; https://www.facebook.com/PassionfishCandles; https://www.instagram.com/passionfish_candles/; https://au.pinterest.com/tilbacandles/;

6 button(s) with no accessible text

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

Got: button.pswp__button (#704 on page); button.pswp__button (#705 on page); button.pswp__button (#706 on page); button.pswp__button (#707 on page); button.pswp__button (#714 on page); button.pswp__button (#715 on page)

81 link(s) with descriptive text

94 links

5 empty

1 generic text

7 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
tel:02 4473 7714	02 4473 7714	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
tel:02 4473 7714	Call us today!	new tab	Add '(opens in new tab)' to text
/category/Homewares	(empty)	empty	Add link text or aria-label
/category/BAM-Sunglasses-Bamboo	(empty)	empty	Add link text or aria-label
/category/Reed-Diffusers	(empty)	empty	Add link text or aria-label
/product/Organic-Hemp-Massage-Oil	Hemp seed oil massage oil Aust…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/PassionfishCand…	facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/passionfish_ca…	instagram	new tab	Add '(opens in new tab)' to text
https://au.pinterest.com/tilbacandles/	pinterest	new tab	Add '(opens in new tab)' to text
/discover-passionfish	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Discover Passionfish
	Call us today! 02 4473 7714	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
<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

82 links and buttons have descriptive text

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

/; /; /category/Homewares; /category/BAM-Sunglasses-Bamboo; /category/Reed-Diffusers

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

Generic link text like 'click here' doesn't describe the destination.

/discover-passionfish ("Read More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

tel:02 4473 7714; tel:02 4473 7714; /product/Organic-Hemp-Massage-Oil; https://www.facebook.com/PassionfishCandles; https://www.instagram.com/passionfish_candles/; https://au.pinterest.com/tilbacandles/;

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.pswp__button (#704 on page); button.pswp__button (#705 on page); button.pswp__button (#706 on page); button.pswp__button (#707 on page); button.pswp__button (#714 on page); button.pswp__button (#715 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

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

FIX

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

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

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No banner (header) landmark

No contentinfo (footer) landmark

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Passionfish Candles &. Gifts | Central Tilba NSW ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✗ Multiple Sizes Missing

Web Manifest

PWA-ready

REVIEW

PWA-ready

Meets PWA install criteria

Name present: Passion Fish Candles & Gifts

192x192 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Passion Fish Candles & Gifts ✓192×192 icon ✓512×512 icon ✗Start URL /?utm_source=homescreen ✓Display Mode standalone ✓

Name Passion Fish Candles & Gifts Display Mode standalone Icons 1 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h3 Tilba Collection

1.06:1

#000000

#060917

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ambient Alchemy Collection

1.06:1

#000000

#060917

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Essential Oil Collection

1.06:1

#000000

#060917

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Lolly Shop Collection

1.06:1

#000000

#060917

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Zodiac Collection

1.06:1

#000000

#060917

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Homewares

1.06:1

#000000

#060917

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Bam Sunglasses

1.06:1

#000000

#060917

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Reed Diffusers & Essential Oil

1.06:1

#000000

#060917

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Organic Hemp Massage Oil

1.06:1

#000000

#060917

needs 3.0:1 (large text)

19px · bottom of viewport

title Passionfish Candles | Handmade Soy Candl…

1.45:1

#000000

#382612

needs 4.5:1 (normal text)

16px · top of page (header area)

span Home

1.45:1

#000000

#382612

needs 4.5:1 (normal text)

16px · top of page (header area)

span Tilba Collection

1.45:1

#000000

#382612

needs 4.5:1 (normal text)

16px · top of page (header area)

span Passionfish Candles

1.45:1

#000000

#382612

needs 4.5:1 (normal text)

16px · top of page (header area)

span Soy Wax Melts

2.62:1

#000000

#275189

needs 4.5:1 (normal text)

16px · above the fold

span Votive Candles & Glasses

2.69:1

#000000

#28538A

needs 4.5:1 (normal text)

16px · above the fold

span Scented Tealights

2.75:1

#000000

#27558A

needs 4.5:1 (normal text)

16px · above the fold

span Reed Diffusers

2.84:1

#000000

#29578C

needs 4.5:1 (normal text)

16px · above the fold

span Room Sprays

2.37:1

#000000

#404A60

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span Zodiac Soy Candle

2.97:1

#000000

#6D5343

needs 4.5:1 (normal text)

16px · above the fold

span Lolly Shop Collection

1.30:1

#000000

#241F24

needs 4.5:1 (normal text)

16px · above the fold

1 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)

Element	Ratio	Required	FG	BG	Result
h3 Tilba Collection	1.06:1	3.0:1	#000000	#060917	Fail
h3 Ambient Alchemy Coll…	1.06:1	3.0:1	#000000	#060917	Fail
h3 Essential Oil Collec…	1.06:1	3.0:1	#000000	#060917	Fail
h3 Lolly Shop Collectio…	1.06:1	3.0:1	#000000	#060917	Fail
h3 Zodiac Collection	1.06:1	3.0:1	#000000	#060917	Fail
h3 Homewares	1.06:1	3.0:1	#000000	#060917	Fail
h3 Bam Sunglasses	1.06:1	3.0:1	#000000	#060917	Fail
h3 Reed Diffusers & Ess…	1.06:1	3.0:1	#000000	#060917	Fail
h3 Organic Hemp Massage…	1.06:1	3.0:1	#000000	#060917	Fail
title Passionfish Candles …	1.45:1	4.5:1	#000000	#382612	Fail
span Home	1.45:1	4.5:1	#000000	#382612	Fail
span Tilba Collection	1.45:1	4.5:1	#000000	#382612	Fail
span Passionfish Candles	1.45:1	4.5:1	#000000	#382612	Fail
span Soy Wax Melts	2.62:1	4.5:1	#000000	#275189	Fail
span Votive Candles & Gla…	2.69:1	4.5:1	#000000	#28538A	Fail
span Scented Tealights	2.75:1	4.5:1	#000000	#27558A	Fail
span Reed Diffusers	2.84:1	4.5:1	#000000	#29578C	Fail
span Room Sprays	2.37:1	4.5:1	#000000	#404A60	Fail
span Zodiac Soy Candle	2.97:1	4.5:1	#000000	#6D5343	Fail
span Lolly Shop Collectio…	1.30:1	4.5:1	#000000	#241F24	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.

Lighthouse Accessibility Audits

Score 81/100 — 4 failing, 18 passed

REVIEW

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
Candles, Melts & Diffusers `div#1000373385 > div#1946091669 > h3.m-size-22 > span.font-size-28`
Follow us on our socials! `div#1995625360 > div#1122389035 > h3.text-align-center > span`
Call us today! `div#1340225750 > div#1556640100 > a#1462304246 > span.text`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#1134560283 > div#1449735839 > a#1876166572 > img#1937417085 `div#1134560283 > div#1449735839 > a#1876166572 > img#1937417085`
div#1749795585 > div#1692599910 > div#1240574529 > img#1349991866 `div#1749795585 > div#1692599910 > div#1240574529 > img#1349991866`

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#1111482395 > div#1134560283 > div#1449735839 > a#1876166572 `div#1111482395 > div#1134560283 > div#1449735839 > a#1876166572`

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
Passionfish Candles `div#1944721186 > div#1977499632 > p.m-text-align-center > a`
Soy Wax Melts `div#1944721186 > div#1977499632 > p.m-text-align-center > a`
Votive Candles & Glasses `div#1944721186 > div#1977499632 > p.m-text-align-center > a`
Scented Tealights `div#1944721186 > div#1977499632 > p.m-text-align-center > a`
Whirly Gig Carousel `div#1224515896 > div#1471352034 > p.m-text-align-center > a`
Art Glass Tea Light Holders `div#1224515896 > div#1471352034 > p.m-text-align-center > a`
Minikin Tea Lights `div#1224515896 > div#1471352034 > p.m-text-align-center > a`
Oil Burners `div#1224515896 > div#1471352034 > p.m-text-align-center > a`
Face Vases `div#1224515896 > div#1471352034 > p.m-text-align-center > a`
Sunglasses `div#1224515896 > div#1471352034 > p.m-text-align-center > a`
Candleholders `div#1224515896 > div#1471352034 > p.m-text-align-center > a`
Fragrant Reed Diffusers `div#1034710347 > div#1134841826 > p.m-text-align-center > a`
Essential Oils 10ml `div#1034710347 > div#1134841826 > p.m-text-align-center > 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>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

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

●Document has a `<title>` element

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

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

●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

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

○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

○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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○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

○Select elements have associated label elements.

○Skip links are focusable.

○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

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

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

Heading Hierarchy

21 headings

PASS

21 headings

Multiple H1 headings (2 found)

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

H1 Passionfish
H1 Candles & Gifts duplicate H1
H2 Handmade in our Central Tilba Studio, South Coast of NSW
H3 Candles, Melts & Diffusers
H3 Tilba Collection
H3 Ambient Alchemy Collection
H3 Essential Oil Collection
H3 Lolly Shop Collection
H3 Zodiac Collection
H3 Homewares
H3 Bam Sunglasses
H3 Reed Diffusers & Essential Oil
H3 Organic Hemp Massage Oil
H3 Follow us on our socials!
H2 A celebration of the home
H3 Open 7 days 10am to 4pm
H4 Call into our retail shop at 25 Bate Street Central Tilba NSW Or call us about any product inquires on:
H5 Candles
H5 Homewares
H5 Reed Diffuser
H5 Discover Central Tilba

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

All 21 heading(s) have substantive, well-formed text

PASS

All 21 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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

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

PASS

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

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

All 73 visible text node(s) render at >= 12 CSS pixels

PASS

All 73 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

PWA Depth

3 PWA signal(s) surfaced

PASS

3 PWA signal(s) surfaced

Service worker registration detected

The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

Manifest is missing `theme_color`

Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.