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

2 issue(s) across 117 links and 8 buttons

REVIEW

2 issue(s) across 117 links and 8 buttons

1 link(s) with no accessible text

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

Got: a#wcm-survey-target-id

7 link(s) open in new tab without warning

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

Got: https://www.facebook.com/readygov; https://twitter.com/readygov; https://www.youtube.com/user/FEMA; https://dhs.gov; https://dhs.gov; https://usa.gov; https://www.oig.dhs.gov/

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.usa-nav__close (#110 on page)

109 link(s) with descriptive text

117 links

1 empty

0 generic text

7 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/readygov	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/readygov	Twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/FEMA	YouTube	new tab	Add '(opens in new tab)' to text
https://dhs.gov	U.S. Department of Homeland Se…	new tab	Add '(opens in new tab)' to text
https://dhs.gov	DHS.gov	new tab	Add '(opens in new tab)' to text
https://usa.gov	USA.gov	new tab	Add '(opens in new tab)' to text
https://www.oig.dhs.gov/	Inspector General	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

116 links and buttons have descriptive text

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

a#wcm-survey-target-id

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

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

https://www.facebook.com/readygov; https://twitter.com/readygov; https://www.youtube.com/user/FEMA; https://dhs.gov; https://dhs.gov; https://usa.gov; https://www.oig.dhs.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

Icon-only buttons need an aria-label so screen readers can announce them.

button.usa-nav__close (#110 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title READY.gov | Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 2 pass AA only

p ) or

3.75:1

#000000

#477326

needs 4.5:1 (normal text)

16px · above the fold

span NOTICE: Due to the lapse in federal fund…

2.37:1

#000000

#3A4F41

needs 4.5:1 (normal text)

16px · mid-page

span Get more information

3.67:1

#000000

#77634B

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

1 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
title Plan Ahead for Disas…	13.95:1	4.5:1	#000000	#C4D5E1	Pass
a Skip to main content	16.58:1	4.5:1	#000000	#DCE6ED	Pass
p An official website …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Here’s how you kno…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Here’s how you kno…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Español	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong Official websites us…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
strong .gov	21.00:1	3.0:1	#000000	#FFFFFF	Pass
p website belongs to a…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong Secure .gov websites…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
strong lock	8.33:1	3.0:1	#000000	#91AB7D	Pass
p ) or	3.75:1	4.5:1	#000000	#477326	Fail
strong https://	16.30:1	3.0:1	#000000	#DAE4ED	Pass
p means you’ve safel…	5.36:1	4.5:1	#000000	#7B846C	Pass
span NOTICE: Due to the l…	2.37:1	4.5:1	#000000	#3A4F41	Fail
span Get more information	3.67:1	4.5:1	#000000	#77634B	Fail
button Menu	10.65:1	4.5:1	#000000	#ACBBC3	Pass
a Español	5.11:1	4.5:1	#000000	#6A827F	Pass
span Disasters and Emerge…	10.13:1	4.5:1	#000000	#9DB8C9	Pass
span All Hazards	10.38:1	4.5:1	#000000	#A4B9CB	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

10 landmarks

PASS

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

3 of 4 <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

9 headings

PASS

9 headings

Single H1 present

H1 Spring and Flood Safety
H2 Wildfires
H2 Thunderstorms & Lightning
H2 Tornadoes
H2 Power Outages
H2 Emergency Alerts
H2 Make a Plan Form
H2 Build a Kit
H2 FEMA Mobile App

A+

Alt Text Quality

1 of 21 images have issues

PASS

1 of 21 images have issues

1 image(s) with generic alt text

1 decorative image(s) correctly marked

19 image(s) with good alt text

21 images 19 good alt text 1 decorative 1 generic

Issue	Count
generic	1 image(s)

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 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="commit">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#mobile_query_0	search	Enter Search Term(s):	for/id
commit	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

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 26 passed

PASS

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.

Navigation

Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home `div.usa-navbar > div.region > div#logo > a.logo-img`

These are opportunities to improve keyboard navigation in your application.

○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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

○Skip links are focusable.

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