Skip to content
https://weather.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 67/100 — 5 failing, 11 passed
FIX
67

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.

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
div.one-sixth-first > div#forecast-lookup > form#getForecast > input#inputstring div.one-sixth-first > div#forecast-lookup > form#getForecast > input#inputstring

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.div-full > div#wwamap > div.USMap > img#us div.div-full > div#wwamap > div.USMap > img#us
div.div-full > div#wwamap > div.USMap > img#alaska div.div-full > div#wwamap > div.USMap > img#alaska
div.div-full > div#wwamap > div.USMap > img#hawaii div.div-full > div#wwamap > div.USMap > img#hawaii

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Location Help div#forecast-lookup > form#getForecast > div#txtHelp > a
div#myfcst > form#myfcst-form > div.myfcst-footer > input#myfcst-submit div#myfcst > form#myfcst-form > div.myfcst-footer > input#myfcst-submit
Privacy Policy form#myfcst-form > div.myfcst-footer > p.myfcst-policy > a
Flash Flood Warning div#wwaleft > ul > li > a
Winter Storm Warning div#wwaleft > ul > li > a
High Wind Warning div#wwaleft > ul > li > a
Flood Warning div#wwaleft > ul > li > a
Gale Warning div#wwaleft > ul > li > a
Red Flag Warning div#wwaleft > ul > li > a
Winter Weather Advisory div#wwacenter_l > ul > li > a
Flood Advisory div#wwacenter_l > ul > li > a
Coastal Flood Advisory div#wwacenter_l > ul > li > a
High Surf Advisory div#wwacenter_l > ul > li > a
Small Craft Advisory div#wwacenter_l > ul > li > a
Brisk Wind Advisory div#wwacenter_l > ul > li > a
Hazardous Seas Warning div#wwacenter_r > ul > li > a
Lake Wind Advisory div#wwacenter_r > ul > li > a
Wind Advisory div#wwacenter_r > ul > li > a
Winter Storm Watch div#wwacenter_r > ul > li > a
Rip Current Statement div#wwacenter_r > ul > li > a
Flood Watch div#wwacenter_r > ul > li > a
High Wind Watch div#wwaright > ul > li > a
Freeze Watch div#wwaright > ul > li > a
Fire Weather Watch div#wwaright > ul > li > a
Special Weather Statement div#wwaright > ul > li > a
Marine Weather Statement div#wwaright > ul > li > a
Air Quality Alert div#wwaright > ul > li > a
US Dept of Commerce div.footer-legal-content > div#footer_legal_info > p > a
National Oceanic and Atmospheric Administration div.footer-legal-content > div#footer_legal_info > p > a
National Weather Service div.footer-legal-content > div#footer_legal_info > p > a
Disclaimer div.footer-legal-content > div#footer_required_links > div.div-half > a
Information Quality div.footer-legal-content > div#footer_required_links > div.div-half > a
Help div.footer-legal-content > div#footer_required_links > div.div-half > a
Glossary div.footer-legal-content > div#footer_required_links > div.div-half > a
Privacy Policy div.footer-legal-content > div#footer_required_links > div.div-half > a
About Us div.footer-legal-content > div#footer_required_links > div.div-half > a
Career Opportunities div.footer-legal-content > div#footer_required_links > div.div-half > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`
●Input buttons have discernible text.
●Form elements have associated labels
●Document has a `<title>` element
●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
●Heading elements appear in a sequentially-descending order
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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 a valid value for its `[lang]` attribute
○`<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">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<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
○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.
C
Alt Text Quality
Action
4 of 14 images have issues
REVIEW
4 of 14 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
10 image(s) with good alt text
14 images 10 good alt text 4 missing
IssueCount
missing4 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C
Form Accessibility
Action
4 of 10 controls have issues
REVIEW
4 of 10 controls have issues
Critical::
4 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" name="btnSearch" id="btnSearch">; <input type="button" id="btnCloseError">; <input type="submit" id="myfcst-submit">
Info::
6 control(s) properly labeled
10 controls
6 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#querytextSearch Forfor/id
#nwsradioNWSfor/id
#noaaradioAll NOAAfor/id
#inputstringtextLocal forecast by "City, St" or ZIP codefor/id
#myfcst-location-inputtextEnter Your City, ST or ZIP Codefor/id
#myfcst-remembercheckboxRemember Mefor/id
#btnCloseErrorbutton(none)none
inputsubmit(none)none
#btnSearchsubmit(none)none
#myfcst-submitsubmit(none)none

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

<input type="submit">; <input type="submit" name="btnSearch" id="btnSearch">; <input type="button" id="btnCloseError">; <input type="submit" id="myfcst-submit">

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

B
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)
ElementRatioRequiredFGBGResult
h1 Critical Fire Weathe…21.00:13.0:1
#000000
#FFFFFF
Pass
title National Weather Ser…6.25:14.5:1
#000000
#8C8C8C
Pass
a HOME21.00:14.5:1
#000000
#FFFFFF
Pass
a FORECAST13.40:14.5:1
#000000
#C4D0DC
Pass
a Local16.71:14.5:1
#000000
#D4E8F9
Pass
a Graphical21.00:14.5:1
#000000
#FFFFFF
Pass
a Aviation21.00:14.5:1
#000000
#FFFFFF
Pass
a Marine21.00:14.5:1
#000000
#FFFFFF
Pass
a Rivers and Lakes15.13:14.5:1
#000000
#CCDDED
Pass
a Hurricanes21.00:14.5:1
#000000
#FFFFFF
Pass
a Severe Weather13.08:14.5:1
#000000
#CCCCCC
Pass
a Fire Weather13.08:14.5:1
#000000
#CCCCCC
Pass
a Sunrise/Sunset21.00:14.5:1
#000000
#FFFFFF
Pass
a Long Range Forecasts21.00:14.5:1
#000000
#FFFFFF
Pass
a Climate Prediction17.78:14.5:1
#000000
#ECECEC
Pass
a Space Weather12.35:14.5:1
#000000
#D6C4AC
Pass
a PAST WEATHER11.10:14.5:1
#000000
#D1B998
Pass
a Past Weather15.26:14.5:1
#000000
#E1DBD2
Pass
a Astronomical Data11.38:14.5:1
#000000
#CFBCA3
Pass
a Certified Weather Da…16.06:14.5:1
#000000
#E1E1E1
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+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 Critical Fire Weather Conditions Continue; Pacific Storm to Bring Heavy Snow to the Sierra-Nevada
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback