Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 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 ✗

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Back to top ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 4 pass AA only

label Main Menu

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · top of page (header area)

a Fisheries

3.15:1

#000000

#515D6F

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Satellites

2.72:1

#000000

#495557

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Research

2.62:1

#000000

#515051

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Marine & Aviation

2.92:1

#000000

#5B574D

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 Customer Experience …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore NOAA //	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
title National Oceanic and…	17.46:1	4.5:1	#000000	#EAEAEA	Pass
a Skip to feedback	17.46:1	4.5:1	#000000	#EAEAEA	Pass
a Skip to main content	5.03:1	4.5:1	#000000	#7C7C7C	Pass
label Main Menu	1.66:1	4.5:1	#000000	#333333	Fail
a Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Weather	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Climate	5.47:1	4.5:1	#000000	#5284C5	Pass
a Ocean & Coasts	6.74:1	4.5:1	#000000	#5E95D5	Pass
a Fisheries	3.15:1	4.5:1	#000000	#515D6F	Fail
a Satellites	2.72:1	4.5:1	#000000	#495557	Fail
a Research	2.62:1	4.5:1	#000000	#515051	Fail
a Marine & Aviation	2.92:1	4.5:1	#000000	#5B574D	Fail
a Charting	4.79:1	4.5:1	#000000	#7F7869	Pass
a Sanctuaries	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Education	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a News and features	21.00:1	4.5: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.

A+

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

11 headings

PASS

11 headings

Multiple H1 headings (2 found)

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

H1 Another ocean drone joins NOAA’s growing fleet
H2 Explore NOAA //
H2 FISHERIES
H2 Fisheries
H2 WEATHER
H2 Weather
H2 NOAA RESEARCH
H2 Research
H1 Customer Experience Feedback 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

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

3 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

7 image(s) with good alt text

11 images 7 good alt text 1 decorative

Issue	Count
too long	3 image(s)

Form Accessibility

1 of 23 controls have issues

PASS

1 of 23 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit" name="edit-submit">

22 control(s) properly labeled

23 controls

22 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#edit-zip	text	Enter City, State or ZIP code	for/id
query	text	Enter Search Terms	aria-label
commit	submit	Search	aria-label
#question_option_46554	radio	👍 Yes	for/id
#question_option_46555	radio	👎 No	for/id
#question_option_46556	radio	Strongly Disagree	for/id
#question_option_46557	radio	Disagree	for/id
#question_option_46558	radio	Neutral	for/id
#question_option_46559	radio	Agree	for/id
#question_option_46560	radio	Strongly Agree	for/id
#question_option_51287	radio	Other	for/id
#question_43962_answer_02_other	text	Enter other text	for/id
#question_option_46561	radio	Strongly Disagree	for/id
#question_option_46562	radio	Disagree	for/id
#question_option_46563	radio	Neutral	for/id
#question_option_46564	radio	Agree	for/id
#question_option_47413	radio	Strongly Agree	for/id
#question_44340_answer_04	select	What is your primary reason for visiting this site today? *	for/id
#question_44341_answer_05	select	Which category best describes you? *	for/id
#question_44342_answer_06	text	Do you have suggestions about how we can improve our website? *	for/id
#question_44343_answer_07	text	To help us address your feedback, please share the web page link that you are referring to. If your feedback refers to a specific website page, enter the link here.	for/id
#question_45065_answer_08	text	Is there anything else you'd like to tell us?	for/id
edit-submit	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

Link & Button Quality

73 links, 6 buttons — all OK

PASS

73 links, 6 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://sites.google.com/noaa.gov/ohcs/current-event; https://twitter.com/NOAA; https://www.facebook.com/NOAA; https://www.youtube.com/noaa; https://touchpoints.digital.gov

68 link(s) with descriptive text

73 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://sites.google.com/noaa.gov/ohcs/c…	COVID-19 hub for NOAA personne…	new tab	Add '(opens in new tab)' to text
https://twitter.com/NOAA	NOAA on Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/NOAA	NOAA on Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/noaa	NOAA on YouTube	new tab	Add '(opens in new tab)' to text
https://touchpoints.digital.gov	Touchpoints	new tab	Add '(opens in new tab)' to text

74 links and buttons have descriptive text

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

https://sites.google.com/noaa.gov/ohcs/current-event; https://twitter.com/NOAA; https://www.facebook.com/NOAA; https://www.youtube.com/noaa; 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

A+

Lighthouse Accessibility Audits

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

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

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