Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Alt Text Quality

Action

12 of 15 images have issues

FIX

12 of 15 images have issues

12 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

10 image-in-link without alt text

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

3 image(s) with good alt text

15 images 3 good alt text 12 missing

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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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: #2e2e2e

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 ✗

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Back-to-top link detected

1 navigation landmark(s) detected

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

Heading Hierarchy

6 headings, 1 skip(s)

REVIEW

6 headings, 1 skip(s)

Multiple H1 headings (4 found)

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

Heading level skipped: H1 → H4 (missing H2)

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

1 empty heading(s)

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

H1 WY
H1 Most Popular duplicate H1
H1 Most Recent duplicate H1
H4 Tags skipped
H4 Colors
H1 (empty)

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

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

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

Link & Button Quality

Action

3 issue(s) across 64 links and 4 buttons

REVIEW

3 issue(s) across 64 links and 4 buttons

1 link(s) with no accessible text

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

Got: /

7 link(s) open in new tab without warning

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

Got: https://fitprint.app/?utm_source=snazzymaps&utm_medium=display&utm_campaign=a…; http://creativecommons.org/publicdomain/zero/1.0/; https://snazzymaps.uservoice.com/forums/228743-general; https://adamkrogh.com; https://twitter.com/snazzymaps; https://www.facebook.com/SnazzyMaps; https://google.com/+SnazzyMaps

2 button(s) with no accessible text

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

Got: button.navbar-toggle (#63 on page); button.user-links-toggle (#93 on page)

56 link(s) with descriptive text

64 links

1 empty

0 generic text

7 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
/style/93/lost-in-the-desert	Lost in the desert …	img no alt	Add alt attribute to the image
/style/72543/assassins-creed-iv	Assassin's Creed IV …	img no alt	Add alt attribute to the image
https://fitprint.app/?utm_source=snazzym…	FitPrint - Know your size befo…	new tab	Add '(opens in new tab)' to text
/style/8097/wy	WY by StipeP …	img no alt	Add alt attribute to the image
/style/151/ultra-light-with-labels	Ultra Light with Labels …	img no alt	Add alt attribute to the image
/style/15/subtle-grayscale	Subtle Grayscale …	img no alt	Add alt attribute to the image
/style/1243/xxxxxxxxxxx	Interface map …	img no alt	Add alt attribute to the image
/style/661677/kane-map-style	Kane Map Style …	img no alt	Add alt attribute to the image
/style/639924/t22	T22 by Miren H…	img no alt	Add alt attribute to the image
/style/637212/bp-event-map-1	BP Event Map 1 …	img no alt	Add alt attribute to the image
/style/636571/mars-analog-atlas	Mars Analog Atlas …	img no alt	Add alt attribute to the image
/	(empty)	empty	Add link text or aria-label
http://creativecommons.org/publicdomain/…	creative commons	new tab	Add '(opens in new tab)' to text
https://snazzymaps.uservoice.com/forums/…	feedback	new tab	Add '(opens in new tab)' to text
https://adamkrogh.com	Adam Krogh	new tab	Add '(opens in new tab)' to text
https://twitter.com/snazzymaps	Follow us on Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/SnazzyMaps	Like us on Facebook	new tab	Add '(opens in new tab)' to text
https://google.com/+SnazzyMaps	Follow us on Google+	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

58 links and buttons have descriptive text

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

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://fitprint.app/?utm_source=snazzymaps&utm_medium=display&utm_campaign=a…; http://creativecommons.org/publicdomain/zero/1.0/; https://snazzymaps.uservoice.com/forums/228743-general; https://adamkrogh.com; https://twitter.com/snazzymaps; https://www.facebook.com/SnazzyMaps; https://google.com/+SnazzyMaps

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.navbar-toggle (#63 on page); button.user-links-toggle (#93 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

Favicon & Branding

20 icon(s) detected

REVIEW

20 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

title Snazzy Maps - Free Styles for Google Map…

1.74:1

#000000

#363636

needs 4.5:1 (normal text)

16px · top of page (header area)

a Explore styles

1.57:1

#000000

#2F2F2F

needs 4.5:1 (normal text)

16px · top of page (header area)

a Create a style

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · top of page (header area)

a Build a map

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · top of page (header area)

span NEW

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

a Plugins

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

a Help

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

a Press

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

a Register

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

a Log in

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

a Register

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

a Log in

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

div Featured Style

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · above the fold

em StipeP

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · mid-page

a Check it out

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · mid-page

a Check it out

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · mid-page

span Lost in the desert

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · mid-page

span by Anonymous

1.41:1

#000000

#272727

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Most Popular	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Most Recent	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Snazzy Maps - Free S…	1.74:1	4.5:1	#000000	#363636	Fail
a Explore styles	1.57:1	4.5:1	#000000	#2F2F2F	Fail
a Create a style	1.41:1	4.5:1	#000000	#272727	Fail
a Build a map	1.41:1	4.5:1	#000000	#272727	Fail
span NEW	1.41:1	4.5:1	#000000	#272727	Fail
a Plugins	1.41:1	4.5:1	#000000	#272727	Fail
a Help	1.41:1	4.5:1	#000000	#272727	Fail
a Press	1.41:1	4.5:1	#000000	#272727	Fail
a Register	1.41:1	4.5:1	#000000	#272727	Fail
a Log in	1.41:1	4.5:1	#000000	#272727	Fail
a Register	1.41:1	4.5:1	#000000	#272727	Fail
a Log in	1.41:1	4.5:1	#000000	#272727	Fail
div Featured Style	1.41:1	4.5:1	#000000	#272727	Fail
em StipeP	1.41:1	4.5:1	#000000	#272727	Fail
a Check it out	1.41:1	4.5:1	#000000	#272727	Fail
a Check it out	1.41:1	4.5:1	#000000	#272727	Fail
span Lost in the desert	1.41:1	4.5:1	#000000	#272727	Fail
span by Anonymous	1.41:1	4.5:1	#000000	#272727	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 80/100 — 5 failing, 22 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters