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

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

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ 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 ✗

Link & Button Quality

Action

10 issue(s) across 325 links and 20 buttons

REVIEW

10 issue(s) across 325 links and 20 buttons

1 link(s) with no accessible text

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

Got: a.navbar-toggle (#175 on page)

9 link(s) with generic text

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

Got: /refuge/bill-williams-river ("Learn More"); /fish-hatchery/dc-booth-historic ("Learn More"); /refuge/alligator-river ("Learn More"); /refuge/james-campbell ("Learn More"); /refuge/bill-williams-river ("Learn More"); /fish-hatchery/dc-booth-historic ("Learn More"); /refuge/alligator-river ("Learn More"); /refuge/james-campbell ("Learn More"); /refuge/bill-williams-river ("Learn More")

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/program/office-of-law-enforcement"]

1 link(s) open in new tab without warning

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

Got: https://touchpoints.digital.gov

313 link(s) with descriptive text

325 links

1 empty

9 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
/program/office-of-law-enforcement	Law Enforcement	img no alt	Add alt attribute to the image
/refuge/bill-williams-river	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Bill Williams River
/fish-hatchery/dc-booth-historic	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Dc Booth Historic
/refuge/alligator-river	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Alligator River
/refuge/james-campbell	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: James Campbell
/refuge/bill-williams-river	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Bill Williams River
/fish-hatchery/dc-booth-historic	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Dc Booth Historic
/refuge/alligator-river	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Alligator River
/refuge/james-campbell	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: James Campbell
/refuge/bill-williams-river	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Bill Williams River
https://touchpoints.digital.gov	Touchpoints	new tab	Add '(opens in new tab)' to text

333 links and buttons have descriptive text

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

a.navbar-toggle (#175 on page)

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

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

/refuge/bill-williams-river ("Learn More"); /fish-hatchery/dc-booth-historic ("Learn More"); /refuge/alligator-river ("Learn More"); /refuge/james-campbell ("Learn More"); /refuge/bill-williams-river ("Learn More"); /fish-hatchery/dc-booth-historic ("Learn More"); /refuge/alligator-river ("Learn More"); /refuge/james-campbell ("Learn More"); /refuge/bill-williams-river ("Learn 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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/program/office-of-law-enforcement"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://touchpoints.digital.gov

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 1 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 U.S. Fish and Wildli…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 User Experience on f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Utility (Top) naviga…	3.45:1	3.0:1	#000000	#4B6389	Pass
h2 Search	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What's going on at F…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our Focus	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What We Do For You	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Visit Us - Our Locat…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer Menu - Employ…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer Menu - Site L…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer Menu - Legal	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer Menu - Extern…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Success	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Error	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Pollinators	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 National Wildlife Re…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Protecting Wildlife	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Celebrating America'…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 National Fish Hatche…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Law Enforcement	21.00:1	3.0:1	#000000	#FFFFFF	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.

Landmark Structure

17 landmarks

PASS

17 landmarks

<main> landmark present

7 <nav> landmark(s) found

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

Heading Hierarchy

24 headings

PASS

24 headings

Multiple H1 headings (2 found)

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

H2 Utility (Top) navigation
H2 Search
H1 U.S. Fish and Wildlife Service
H2 What's going on at FWS
H2 Our Focus
H3 Pollinators
H3 National Wildlife Refuges
H3 Protecting Wildlife
H3 Celebrating America's 250 Anniversary
H3 National Fish Hatchery System
H3 Law Enforcement
H2 What We Do For You
H3 Our Services
H3 Partnerships
H3 Volunteering
H3 Education Programs
H2 Visit Us - Our Locations
H2 Footer Menu - Employment
H2 Footer Menu - Site Links
H2 Footer Menu - Legal
H2 Footer Menu - External Links
H1 User Experience on fws.gov duplicate H1
H2 Success
H2 Error

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

A+

Alt Text Quality

All 38 images OK

PASS

All 38 images OK

2 image(s) with alt text over 125 characters

6 decorative image(s) correctly marked

30 image(s) with good alt text

38 images 30 good alt text 6 decorative

Issue	Count
too long	2 image(s)

A+

Form Accessibility

All 38 controls labeled

PASS

All 38 controls labeled

38 control(s) properly labeled

38 controls

38 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-keys	search	Search	for/id
#question_option_13573	radio	Strongly Disagree	for/id
#question_option_13574	radio	Disagree	for/id
#question_option_13575	radio	Neutral	for/id
#question_option_13576	radio	Agree	for/id
#question_option_13577	radio	Strongly Agree	for/id
#question_option_13578	radio	Strongly Disagree	for/id
#question_option_13579	radio	Disagree	for/id
#question_option_13580	radio	Neutral	for/id
#question_option_13581	radio	Agree	for/id
#question_option_13582	radio	Strongly Agree	for/id
#question_31386_answer_08	textarea	Anything you want to tell us about your scores above? (free text)	for/id
#question_option_13583	radio	Strongly Disagree	for/id
#question_option_13584	radio	Disagree	for/id
#question_option_13585	radio	Neutral	for/id
#question_option_13586	radio	Agree	for/id
#question_option_13587	radio	Strongly Agree	for/id
#question_option_13588	radio	Strongly Disagree	for/id
#question_option_13589	radio	Disagree	for/id
#question_option_13590	radio	Neutral	for/id
#question_option_13591	radio	Agree	for/id
#question_option_13592	radio	Strongly Agree	for/id
#question_option_13593	radio	Strongly Disagree	for/id
#question_option_13594	radio	Disagree	for/id
#question_option_13595	radio	Neutral	for/id
#question_option_13596	radio	Agree	for/id
#question_option_13597	radio	Strongly Agree	for/id
#question_option_13598	radio	Strongly Disagree	for/id
#question_option_13599	radio	Disagree	for/id
#question_option_13600	radio	Neutral	for/id
#question_option_13601	radio	Agree	for/id
#question_option_13602	radio	Strongly Agree	for/id
#question_option_13603	radio	Strongly Disagree	for/id
#question_option_13604	radio	Disagree	for/id
#question_option_13605	radio	Neutral	for/id
#question_option_13606	radio	Agree	for/id
#question_option_13607	radio	Strongly Agree	for/id
#question_31392_answer_09	textarea	Anything else you'd like to share with us?	for/id

A+

Lighthouse Accessibility Audits

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

●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

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

●Elements with visible text labels have matching accessible names.

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

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

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