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 4 REVIEW 4 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

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

Heading Hierarchy

24 headings, 1 skip(s)

REVIEW

24 headings, 1 skip(s)

Multiple H1 headings (14 found)

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

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H3 notice
H1 FIXING DISASTER RESPONSE
H1 MAKING AMERICA SAFE AGAIN duplicate H1
H1 ARRESTING AND REMOVING THE WORST OF THE WORST duplicate H1
H1 MOST SECURE BORDER IN AMERICAN HISTORY duplicate H1
H1 USHERING IN THE GOLDEN AGE OF TRAVEL duplicate H1
H1 SECURING THE HIGH SEAS AND SAVING LIVES duplicate H1
H1 FIXING DISASTER RESPONSE duplicate H1
H1 MAKING AMERICA SAFE AGAIN duplicate H1
H1 ARRESTING AND REMOVING THE WORST OF THE WORST duplicate H1
H1 MOST SECURE BORDER IN AMERICAN HISTORY duplicate H1
H1 USHERING IN THE GOLDEN AGE OF TRAVEL duplicate H1
H1 SECURING THE HIGH SEAS AND SAVING LIVES duplicate H1
H1 FIXING DISASTER RESPONSE duplicate H1
H3 NOTICE: CBP Home Stipend Increase skipped
H2 News & Updates
H2 News & Updates
H3 ICE Arrests Pedophiles, Rapists, and Drug Dealers
H3 More Third World Violence: ICE Requests Texas Not Release Illegal Alien Who Murdered His Co-Worker with a Sledgehammer
H3 HSI Arrests Convicted Murderer Who Sent Threats to ICE Director, Saying ICE Law Enforcement Officers Should Have “Two F**king Bullets to the Back of Their Nazi Maggot Heads”
H3 Over the Weekend, ICE Arrests Human Traffickers, Pedophiles, Rapists, Kidnappers, and Other Depraved Criminal Illegal Aliens
H3 ICE Lodges Detainer for Illegal Alien Who Killed Two Boys in DUI Crash in South Carolina
H1 Trump Administration Delivers 11 Straight Months of Zero Releases at the Border duplicate H1
H2 Subscribe

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

Action

2 issue(s) across 90 links and 18 buttons

REVIEW

2 issue(s) across 90 links and 18 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

4 link(s) open in new tab without warning

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

Got: https://www.ice.gov/join; https://join.justice.gov/; https://www.uscis.gov/join; https://public.govdelivery.com/accounts/USDHS/subscriber/new

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 (#188 on page)

85 link(s) with descriptive text

90 links

1 empty

0 generic text

4 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.ice.gov/join	Image	new tab	Add '(opens in new tab)' to text
https://join.justice.gov/	Image	new tab	Add '(opens in new tab)' to text
https://www.uscis.gov/join	Image	new tab	Add '(opens in new tab)' to text
https://public.govdelivery.com/accounts/…	Email	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

102 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.ice.gov/join; https://join.justice.gov/; https://www.uscis.gov/join; https://public.govdelivery.com/accounts/USDHS/subscriber/new

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 (#188 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 Lock ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA 1 pass AA only

h2 News & Updates

2.56:1

#000000

#005288

needs 3.0:1 (large text)

24px · bottom of viewport

h2 News & Updates

2.56:1

#000000

#005288

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Subscribe

2.56:1

#000000

#005288

needs 3.0:1 (large text)

24px · bottom of viewport

title Home | Homeland Security

1.44:1

#000000

#002B47

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.55:1

#000000

#0C2F53

needs 4.5:1 (normal text)

16px · top of page (header area)

p An official website of the United States…

1.73:1

#000000

#1F3464

needs 4.5:1 (normal text)

16px · top of page (header area)

p Here’s how you know

1.62:1

#000000

#1A3251

needs 4.5:1 (normal text)

16px · top of page (header area)

span Here’s how you know

1.56:1

#000000

#173145

needs 4.5:1 (normal text)

16px · above the fold

strong Official websites use .gov

1.56:1

#000000

#173145

needs 3.0:1 (large text)

16px · above the fold

strong .gov

1.56:1

#000000

#173145

needs 3.0:1 (large text)

16px · above the fold

p website belongs to an official governmen…

1.56:1

#000000

#173145

needs 4.5:1 (normal text)

16px · above the fold

strong Secure .gov websites use HTTPS

2.56:1

#000000

#005288

needs 3.0:1 (large text)

16px · above the fold

strong lock

2.56:1

#000000

#005288

needs 3.0:1 (large text)

16px · above the fold

p means you’ve safely connected to the .…

4.03:1

#000000

#6A6C79

needs 4.5:1 (normal text)

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

div Countdown to America's 250th Anniversary…

3.10:1

#000000

#5B5B5D

needs 4.5:1 (normal text)

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

div Days

2.32:1

#000000

#444A47

needs 4.5:1 (normal text)

16px · mid-page

div Hours

4.21:1

#000000

#67726F

needs 4.5:1 (normal text)

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

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
h2 News & Updates	2.56:1	3.0:1	#000000	#005288	Fail
h2 News & Updates	2.56:1	3.0:1	#000000	#005288	Fail
h2 Subscribe	2.56:1	3.0:1	#000000	#005288	Fail
h3 notice	3.25:1	3.0:1	#000000	#276486	Pass
title Home \| Homeland Secu…	1.44:1	4.5:1	#000000	#002B47	Fail
a Skip to main content	1.55:1	4.5:1	#000000	#0C2F53	Fail
p An official website …	1.73:1	4.5:1	#000000	#1F3464	Fail
p Here’s how you kno…	1.62:1	4.5:1	#000000	#1A3251	Fail
span Here’s how you kno…	1.56:1	4.5:1	#000000	#173145	Fail
strong Official websites us…	1.56:1	3.0:1	#000000	#173145	Fail
strong .gov	1.56:1	3.0:1	#000000	#173145	Fail
p website belongs to a…	1.56:1	4.5:1	#000000	#173145	Fail
strong Secure .gov websites…	2.56:1	3.0:1	#000000	#005288	Fail
strong lock	2.56:1	3.0:1	#000000	#005288	Fail
p ) or	7.55:1	4.5:1	#000000	#6CA0CD	Pass
strong https://	14.99:1	3.0:1	#000000	#C0DDFC	Pass
p means you’ve safel…	4.03:1	4.5:1	#000000	#6A6C79	Fail
div Countdown to America…	3.10:1	4.5:1	#000000	#5B5B5D	Fail
div Days	2.32:1	4.5:1	#000000	#444A47	Fail
div Hours	4.21:1	4.5:1	#000000	#67726F	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

11 landmarks

PASS

11 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

Alt Text Quality

2 of 35 images have issues

PASS

2 of 35 images have issues

2 image(s) with generic alt text

4 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

28 image(s) with good alt text

35 images 28 good alt text 1 decorative 2 generic

Issue	Count
generic	2 image(s)
too long	4 image(s)

Form Accessibility

1 of 3 controls have issues

PASS

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

2 control(s) properly labeled

3 controls

2 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#gsc-i-id1	search	search	aria-label
#email	email	Email Address	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+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /profiles/dhsd8_gov/themes/custom/dhs_uswds_subtheme/assets/css/print.css?tduyn8

Print Stylesheet ✓ Print Optimized

Print stylesheet /profiles/dhsd8_gov/themes/custom/dhs_uswds_subtheme/assets/css/print.css?tduyn8 ✓Inline @media print Not detected ✗

Lighthouse Accessibility Audits

Score 93/100 — 4 failing, 29 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.

ARIA

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PRESS ENTER TO SEARCH `nav.usa-nav > div.region > div.footer > div#search-block-wrap-1`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Get direct updates from DHS in your inbox. `div.subscribe-inner > form#GD-snippet-form > div.inner > div.form-text`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NOTICE: CBP Home Stipend Increase `div.field__item > div.paragraph > div.usa-alert__body > h3.usa-alert__heading`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Countdown to America's 250th Anniversary! 73 Days 4 Hours 33 Minutes `div.layout > div.layout__region > div.clearfix > a.dhs-250-header__link`

○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

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

●`[accesskey]` values are unique

●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

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

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

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

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

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