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 4 REVIEW 4 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

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 ✗

Mobile-Readable Font Sizes

Action

88% of visible text renders at >= 12 CSS px (8 below threshold)

REVIEW

88% of visible text renders at >= 12 CSS px (8 below threshold)

8 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: <span> 11.0px ("Fredericksburg, VA"); <span> 11.0px ("spring"); <span> 11.0px ("36"); <span> 11.0px ("days"); <span> 11.0px ("left").

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Gone Native | Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

REVIEW

2 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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

title Gone Native | Where the wild things grow

1.80:1

#000000

#243E2C

needs 4.5:1 (normal text)

16px · top of page (header area)

span 36 days left

1.91:1

#000000

#284230

needs 4.5:1 (normal text)

16px · above the fold

span Moon

1.92:1

#000000

#294231

needs 4.5:1 (normal text)

16px · above the fold

span new

1.91:1

#000000

#284230

needs 4.5:1 (normal text)

16px · above the fold

span SAT · 16 MAY 2026

1.92:1

#000000

#294231

needs 4.5:1 (normal text)

16px · above the fold

a Journal

1.92:1

#000000

#294230

needs 4.5:1 (normal text)

16px · above the fold

a About

1.95:1

#000000

#2A4331

needs 4.5:1 (normal text)

16px · above the fold

a Events

1.92:1

#000000

#294231

needs 4.5:1 (normal text)

16px · above the fold

a Resources

1.92:1

#000000

#294230

needs 4.5:1 (normal text)

16px · above the fold

a Contact

1.92:1

#000000

#294230

needs 4.5:1 (normal text)

16px · above the fold

span Home

1.92:1

#000000

#294230

needs 4.5:1 (normal text)

16px · mid-page

span Journal

1.91:1

#000000

#284230

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Spring's Arrival	20.47:1	3.0:1	#000000	#FDFCF9	Pass
h2 Recent Writing	20.47:1	3.0:1	#000000	#FDFCF9	Pass
h2 Stay Rooted	20.47:1	3.0:1	#000000	#FDFCF9	Pass
h3 PFAS — A Problem f…	20.47:1	3.0:1	#000000	#FDFCF9	Pass
h3 Thinking About Garde…	20.47:1	3.0:1	#000000	#FDFCF9	Pass
title Gone Native \| Where …	1.80:1	4.5:1	#000000	#243E2C	Fail
a Skip to main content	20.47:1	4.5:1	#000000	#FDFCF9	Pass
span Fredericksburg, VA	20.47:1	4.5:1	#000000	#FDFCF9	Pass
span spring	9.61:1	4.5:1	#000000	#A8B2A9	Pass
span 36 days left	1.91:1	4.5:1	#000000	#284230	Fail
span Moon	1.92:1	4.5:1	#000000	#294231	Fail
span new	1.91:1	4.5:1	#000000	#284230	Fail
span SAT · 16 MAY 2026	1.92:1	4.5:1	#000000	#294231	Fail
a Journal	1.92:1	4.5:1	#000000	#294230	Fail
a About	1.95:1	4.5:1	#000000	#2A4331	Fail
a Events	1.92:1	4.5:1	#000000	#294231	Fail
a Resources	1.92:1	4.5:1	#000000	#294230	Fail
a Contact	1.92:1	4.5:1	#000000	#294230	Fail
span Home	1.92:1	4.5:1	#000000	#294230	Fail
span Journal	1.91:1	4.5:1	#000000	#284230	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

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

Skip navigation link present

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

A+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 GoneNative
H2 Spring's Arrival
H2 Recent Writing
H3 PFAS — A Problem for Native Plants and Their Habitats
H3 Thinking About Gardening in the Midst of Winter with "Garden Revolution" by Larry Weaner
H2 Stay Rooted

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

4 decorative image(s) correctly marked

3 image(s) with good alt text

7 images 3 good alt text 4 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

36 links, 1 buttons — all OK

PASS

36 links, 1 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://www.instagram.com/riverruth/; https://www.instagram.com/riverruth/; https://www.centralrappvnps.org/; https://bathysphereride.com/

32 link(s) with descriptive text

36 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	Gone Native — home	img no alt	Add alt attribute to the image
https://www.instagram.com/riverruth/	Follow on Instagram	new tab	Add '(opens in new tab)' to text
/	Gone Native — home	img no alt	Add alt attribute to the image
https://www.instagram.com/riverruth/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.centralrappvnps.org/	Central Rappahannock Chapter o…	new tab	Add '(opens in new tab)' to text
https://bathysphereride.com/	Prismatis Studio	new tab	Add '(opens in new tab)' to text

33 links and buttons have descriptive text

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

https://www.instagram.com/riverruth/; https://www.instagram.com/riverruth/; https://www.centralrappvnps.org/; https://bathysphereride.com/

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

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

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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+

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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 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.

○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

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

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

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

●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

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

○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

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

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