Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 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-r2ewtw

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://allaboutbirds.org/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://allaboutbirds.org/manifest.json

Manifest contains invalid JSON.

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 ✗

Form Accessibility

Action

3 of 6 controls have issues

REVIEW

3 of 6 controls have issues

3 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit">; <input type="submit">; <input type="submit">

3 control(s) properly labeled

6 controls

3 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
#masthead-search	search	Search for species name or keywords	for/id
#modal-search	search	Enter species name or keyword	for/id
#email-de085739-e692-431e-b987-0736c9c7e87a	email	Email Address*	for/id
input	submit	(none)	none
input	submit	(none)	none
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Favicon & Branding

4 icon(s) detected

REVIEW

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

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA 15 pass AA only

title Online bird guide, bird ID help, life hi…

1.36:1

#000000

#252423

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Skip to main content

1.98:1

#000000

#523B00

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to Content Area

1.25:1

#000000

#271C01

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Get Involved

2.63:1

#000000

#5A4E4D

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Get eNews

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

3 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
h1 All About Birds	3.66:1	3.0:1	#000000	#666666	Pass
h2 Featured Articles	3.66:1	3.0:1	#000000	#666666	Pass
h2 Bird ID Skills	3.66:1	3.0:1	#000000	#666666	Pass
h2 Feeding Birds	3.66:1	3.0:1	#000000	#666666	Pass
h2 FAQs & Common Proble…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Bird-Friendly Homes	3.66:1	3.0:1	#000000	#666666	Pass
h2 Try This	3.66:1	3.0:1	#000000	#666666	Pass
h2 Read Our Award-Winni…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Explore All About Bi…	3.66:1	3.0:1	#000000	#666666	Pass
h2 All About Birds	3.66:1	3.0:1	#000000	#666666	Pass
h2 is a free resource	3.66:1	3.0:1	#000000	#666666	Pass
h2 Follow Us	3.66:1	3.0:1	#000000	#666666	Pass
h2 Search species and a…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Don't miss a thing! …	3.66:1	3.0:1	#000000	#666666	Pass
h2 Try Birds of the Wor…	3.66:1	3.0:1	#000000	#666666	Pass
title Online bird guide, b…	1.36:1	4.5:1	#000000	#252423	Fail
a Skip to main content	1.98:1	4.5:1	#000000	#523B00	Fail
a Skip to Content Area	1.25:1	4.5:1	#000000	#271C01	Fail
a Get Involved	2.63:1	4.5:1	#000000	#5A4E4D	Fail
a Get eNews	3.66:1	4.5:1	#000000	#666666	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

18 landmarks

PASS

18 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

14 headings

PASS

14 headings

Single H1 present

H1 All About BirdsYour Online Guide To Birds And Birdwatching
H2 Featured Articles
H2 Bird ID Skills
H2 Feeding Birds
H2 FAQs & Common Problems
H2 Bird-Friendly Homes
H2 Try This
H2 Read Our Award-Winning Magazine
H2 Explore All About Birds Species
H2 All About Birdsis a free resource
H2 Follow Us
H2 Search species and articles
H2 Don't miss a thing! Join our email list
H2 Try Birds of the World for free!

A+

Alt Text Quality

All 33 images OK

PASS

All 33 images OK

2 image(s) with alt text over 125 characters

2 decorative image(s) correctly marked

29 image(s) with good alt text

33 images 29 good alt text 2 decorative

Issue	Count
too long	2 image(s)

A+

Link & Button Quality

127 links, 26 buttons — all OK

PASS

127 links, 26 buttons — all OK

127 link(s) with descriptive text

127 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

153 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 32 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

●Input buttons have discernible text.

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

●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

●`<frame>` or `<iframe>` elements have a title

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

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

●Links are distinguishable without relying on color.

●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

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

●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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

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