https://www.mossandmolt.com/pages/aquarium-sim

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 5 REVIEW 3 FIX

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: rgb(1 26 49)

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 ✗

Link & Button Quality

Action

4 issue(s) across 103 links and 61 buttons

REVIEW

4 issue(s) across 103 links and 61 buttons

3 link(s) with generic text

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

Got: /pages/contact ("More"); /pages/contact ("More"); /pages/contact ("More")

3 link(s) open in new tab without warning

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

Got: https://www.facebook.com/profile.php?id=61595282821803; https://www.instagram.com/moss.and.molt; https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

1 button(s) with no accessible text

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

Got: button#sbadge

97 link(s) with descriptive text

103 links

0 empty

3 generic text

3 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/pages/contact	More	generic text	Replace with descriptive text
Before: More Suggested: Contact
/pages/contact	More	generic text	Replace with descriptive text
Before: More Suggested: Contact
/pages/contact	More	generic text	Replace with descriptive text
Before: More Suggested: Contact
https://www.facebook.com/profile.php?id=…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/moss.and.molt	Instagram	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

157 links and buttons have descriptive text

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

/pages/contact ("More"); /pages/contact ("More"); /pages/contact ("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.

https://www.facebook.com/profile.php?id=61595282821803; https://www.instagram.com/moss.and.molt; https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…

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#sbadge

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – Moss & Molt ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

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

h2 Join our email list

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Shop

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Shipping & help

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Policies

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contact

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your cart is empty

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Search

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Oops!

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

h2 5% off your

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

h2 first order

1.10:1

#000000

#011020

needs 3.0:1 (large text)

24px · bottom of viewport

title Aquarium Simulator for Shrimp Tanks (Fre…

1.07:1

#000000

#040C17

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.07:1

#000000

#040C17

needs 4.5:1 (normal text)

16px · top of page (header area)

p In test mode due to BIG updates. Sign up…

1.07:1

#000000

#010C1A

needs 4.5:1 (normal text)

16px · top of page (header area)

span Home

1.14:1

#000000

#0C1420

needs 4.5:1 (normal text)

16px · top of page (header area)

span Shop

1.22:1

#000000

#0D1C2C

needs 4.5:1 (normal text)

16px · above the fold

span Shop All

1.07:1

#000000

#020C19

needs 4.5:1 (normal text)

16px · above the fold

span Shrimp

1.27:1

#000000

#0E2031

needs 4.5:1 (normal text)

16px · above the fold

span Plants

1.08:1

#000000

#020D1F

needs 4.5:1 (normal text)

16px · above the fold

span Hardscape

1.08:1

#000000

#010E1C

needs 4.5:1 (normal text)

16px · above the fold

span Equipment

1.07:1

#000000

#010D1B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Join our email list	1.10:1	3.0:1	#000000	#011020	Fail
h2 Shop	1.10:1	3.0:1	#000000	#011020	Fail
h2 Shipping & help	1.10:1	3.0:1	#000000	#011020	Fail
h2 Policies	1.10:1	3.0:1	#000000	#011020	Fail
h2 Contact	1.10:1	3.0:1	#000000	#011020	Fail
h2 Your cart is empty	1.10:1	3.0:1	#000000	#011020	Fail
h2 Search	1.10:1	3.0:1	#000000	#011020	Fail
h2 Oops!	1.10:1	3.0:1	#000000	#011020	Fail
h2 5% off your	1.10:1	3.0:1	#000000	#011020	Fail
h2 first order	1.10:1	3.0:1	#000000	#011020	Fail
title Aquarium Simulator f…	1.07:1	4.5:1	#000000	#040C17	Fail
a Skip to content	1.07:1	4.5:1	#000000	#040C17	Fail
p In test mode due to …	1.07:1	4.5:1	#000000	#010C1A	Fail
span Home	1.14:1	4.5:1	#000000	#0C1420	Fail
span Shop	1.22:1	4.5:1	#000000	#0D1C2C	Fail
span Shop All	1.07:1	4.5:1	#000000	#020C19	Fail
span Shrimp	1.27:1	4.5:1	#000000	#0E2031	Fail
span Plants	1.08:1	4.5:1	#000000	#020D1F	Fail
span Hardscape	1.08:1	4.5:1	#000000	#010E1C	Fail
span Equipment	1.07:1	4.5:1	#000000	#010D1B	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.

A+

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

Heading Hierarchy

13 headings, 1 skip(s)

PASS

13 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Aquarium Sim
H2 Make it real
H2 Join our email list
H2 Shop
H2 Shipping & help
H2 Policies
H2 Contact
H2 Your cart is empty
H2 Your cart is empty
H2 Search
H4 Products skipped
H2 Oops!
H2 5% off yourfirst order

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 13 heading(s) have substantive, well-formed text

PASS

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

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

Alt Text Quality

All 27 images OK

PASS

All 27 images OK

3 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

23 image(s) with good alt text

27 images 23 good alt text 1 decorative

Issue	Count
too long	3 image(s)

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#EmailInput-ATmw1N2FDQ0xRb0lac__email_signup_crihX7	email	Email	for/id
input	input	Your question	aria-label
contact[body]	textarea	What went wrong?	none
contact[email]	email	Your email	none
#cmdk-input	search	Search	for/id

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

5 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

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

PASS

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

No tabindex anti-patterns detected

Iframe Accessibility

1/2 iframe(s) missing title; 0 placeholder(s)

PASS

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

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

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

PASS

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

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

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

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

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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 23 passed

PASS

100

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Water 97 Equip 85 Plants 97 Live 97 `div.app > section.stage > div#lock > button#mstrip`

○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

●Image elements have `[alt]` attributes

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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.

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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