Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 4 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-4pv0gh

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ 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

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.

Link & Button Quality

3 issue(s) across 59 links and 3 buttons

REVIEW

3 issue(s) across 59 links and 3 buttons

3 link(s) with no accessible text

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

Got: /characters/walter-the-stone-whale; /characters/emma-louise-carter; /characters/riley-the-raccoon

56 link(s) with descriptive text

59 links

3 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/characters/walter-the-stone-whale	(empty)	empty	Add link text or aria-label
/characters/emma-louise-carter	(empty)	empty	Add link text or aria-label
/characters/riley-the-raccoon	(empty)	empty	Add link text or aria-label

59 links and buttons have descriptive text

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

/characters/walter-the-stone-whale; /characters/emma-louise-carter; /characters/riley-the-raccoon

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

Mobile Keyboard & Autofill

Action

1/2 eligible field(s) missing autocomplete or inputmode

REVIEW

1/2 eligible field(s) missing autocomplete or inputmode

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" id="footer-email">

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 8 pass AA only

title Lake Stillwater Books™ — One Lake. O…

2.32:1

#000000

#0F4D71

needs 4.5:1 (normal text)

16px · top of page (header area)

span Nymeria Rose

2.32:1

#000000

#0F4D71

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Lake Stillwater Book…	7.31:1	3.0:1	#000000	#7E9CB5	Pass
h2 The Lake Stillwater …	7.31:1	3.0:1	#000000	#7E9CB5	Pass
h2 Meet the Characters	7.31:1	3.0:1	#000000	#7E9CB5	Pass
h2 Guides, discussion q…	7.31:1	3.0:1	#000000	#7E9CB5	Pass
h3 Emma's First Adventu…	7.31:1	3.0:1	#000000	#7E9CB5	Pass
h3 Walter's Lake Advent…	7.31:1	3.0:1	#000000	#7E9CB5	Pass
h3 Lake Stillwater Earl…	7.31:1	3.0:1	#000000	#7E9CB5	Pass
h3 Emma & Walter's Shor…	7.31:1	3.0:1	#000000	#7E9CB5	Pass
h3 Growing Up Lake Stil…	7.31:1	3.0:1	#000000	#7E9CB5	Pass
h3 The Lake Stillwater …	7.31:1	3.0:1	#000000	#7E9CB5	Pass
title Lake Stillwater Book…	2.32:1	4.5:1	#000000	#0F4D71	Fail
span Nymeria Rose	2.32:1	4.5:1	#000000	#0F4D71	Fail
a Home	5.74:1	4.5:1	#000000	#5B8BAD	Pass
a About	5.82:1	4.5:1	#000000	#5D8CAD	Pass
button Books	5.92:1	4.5:1	#000000	#608DAE	Pass
a All Books	6.06:1	4.5:1	#000000	#628FAE	Pass
a Emma's First Adventu…	6.15:1	4.5:1	#000000	#6490AF	Pass
a Walter's Lake Advent…	6.24:1	4.5:1	#000000	#6691B0	Pass
a Lake Stillwater Earl…	6.34:1	4.5:1	#000000	#6892B1	Pass
a Emma & Walter's Shor…	6.41:1	4.5:1	#000000	#6993B1	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 84/100 — 5 failing, 25 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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home About All Books Emma's First Adventures™ (0–3) Walter's Lake Adventures™ (… `header.fixed > nav.max-w-6xl > div.lg:hidden > div.absolute`

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home `div.absolute > ul.p-2 > li > a.block`
About `div.absolute > ul.p-2 > li > a.block`
All Books `div.absolute > ul.p-2 > li > a.block`
Emma's First Adventures™ (0–3) `div.absolute > ul.p-2 > li > a.block`
Walter's Lake Adventures™ (3–6) `div.absolute > ul.p-2 > li > a.block`
Lake Stillwater Early Learning™ (6–8) `div.absolute > ul.p-2 > li > a.block`
Emma & Walter's Shoreline Adventures™ (8–12) `div.absolute > ul.p-2 > li > a.block`
Growing Up Lake Stillwater™ (12–YA) `div.absolute > ul.p-2 > li > a.block`
The Lake Stillwater Chronicles™ (Adult) `div.absolute > ul.p-2 > li > a.block`
Characters `div.absolute > ul.p-2 > li > a.block`
Downloads `div.absolute > ul.p-2 > li > a.block`
Games `div.absolute > ul.p-2 > li > a.block`
Parents & Educators `div.absolute > ul.p-2 > li > a.block`
Contact `div.absolute > ul.p-2 > li > a.block`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Explore the Books `div.max-w-6xl > div.text-lake-100 > div.flex > a.px-7`
ONE WORLD, EVERY READER `main > section.max-w-6xl > div.text-center > p.font-sans`
Learn more → `div.relative > div.relative > div.flex > a.inline-block`
Walter's books → `div.relative > div.relative > div.flex > a.inline-block`
Learn more → `div.relative > div.relative > div.flex > a.inline-block`
Learn more → `div.relative > div.relative > div.flex > a.inline-block`
Learn more → `div.relative > div.relative > div.flex > a.inline-block`
Adult fiction → `div.relative > div.relative > div.flex > a.inline-block`
Parents & Educators page → `div.max-w-4xl > div.bg-white > div.flex-1 > a.inline-block`
nymeriarosebooks@outlook.com `div.max-w-6xl > div.grid > div > a.text-xs`
EXPLORE `div.max-w-6xl > div.grid > nav > p.font-sans`
STAY IN THE LOOP `div.max-w-6xl > div.grid > div > p.font-sans`
Notify me `div > form.mt-2 > div.flex > button.px-5`
© 2026 Nymeria Rose. All rights reserved. `footer.bg-lake-900 > div.max-w-6xl > div.mt-12 > p`
Privacy Policy `div.max-w-6xl > div.mt-12 > div.flex > a.hover:text-lake-200`
Parents & Educators `div.max-w-6xl > div.mt-12 > div.flex > a.hover:text-lake-200`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home About All Books Emma's First Adventures™ (0–3) Walter's Lake Adventures™ (… `nav.max-w-6xl > div.lg:hidden > div.absolute > ul.p-2`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Nymeria Rose `div.min-h-screen > header.fixed > nav.max-w-6xl > a.flex`
Oliver, the Otter™ Oliver, the Otter™ The Mischief Maker He didn’t mean to c… `section.relative > div.relative > div.grid > div.relative`
Emma Louise Emma Louise The Curious Explorer Six years old and asking questi… `section.relative > div.relative > div.grid > div.relative`
Riley the Raccoon™ Riley the Raccoon™ The Clever Collector If it’s shiny, Ri… `section.relative > div.relative > div.grid > div.relative`

○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

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

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

●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

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Skip links are focusable.

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

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

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

A+

Heading Hierarchy

10 headings

PASS

10 headings

Single H1 present

H1 Lake Stillwater Books™
H2 The Lake Stillwater Community™
H3 Emma's First Adventures™
H3 Walter's Lake Adventures™
H3 Lake Stillwater Early Learning™
H3 Emma & Walter's Shoreline Adventures™
H3 Growing Up Lake Stillwater™
H3 The Lake Stillwater Chronicles™
H2 Meet the Characters
H2 Guides, discussion questions, and classroom tips

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

3 decorative image(s) correctly marked

5 image(s) with good alt text

8 images 5 good alt text 3 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#footer-email	email	Your email address	for/id

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

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

tabindex="-1" on naturally-focusable <a>

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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 121 visible text node(s) render at >= 12 CSS pixels

PASS

All 121 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

1 mobile-depth signal(s) detected

PASS

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

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