Skip to content
https://ice.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ 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.

B
Landmark Structure
25 landmarks
REVIEW
25 landmarks
Info::
<main> landmark present
Info::
12 <nav> landmark(s) found
Warning::
7 of 12 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN CONTENTINFO footer

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

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

C
Heading Hierarchy
Action
92 headings, 2 skip(s)
REVIEW
92 headings, 2 skip(s)
Warning::
Multiple H1 headings (13 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Main Navigation
  • H3 About Us
  • H4 Mission
  • H4 Who We Are
  • H4 Leadership
  • H4 History
  • H4 Information Library
  • H4 Career Opportunities
  • H4 ICE Fallen Officers
  • H4 Fact Sheets
  • H3 Enforcement and Removal Operations
  • H4 Identify and Arrest
  • H5 Criminal Alien Program
  • H5 Fugitive Operations
  • H5 Law Enforcement Partnerships 287g Program
  • H5 Immigration Fraud Prosecutions
  • H4 Detain
  • H5 Immigration Detainers
  • H5 Detention Facilities
  • H5 Health Service Corps
  • H5 Detention Management
  • H5 Facility Inspections
  • H5 Family Residential Standards
  • H4 Remove
  • H5 Removal
  • H5 Recalcitrant Countries
  • H5 Self-Deportation
  • H4 Immigration Enforcement Frequently Asked Questions
  • H4 ERO Statistics Dashboard
  • H4 How ICE Enforces Immigration Laws
  • H4 ICE Check-in
  • H4 ERO eFile
  • H3 Homeland Security Investigations
  • H4 Homeland Security Investigations
  • H5 Operational Priorities
  • H5 Investigations
  • H5 HSI Operations and Initiatives
  • H5 Outreach Programs
  • H5 Partnerships
  • H5 Centers & Labs
  • H5 Recognize & Report Crime
  • H5 HSI Careers
  • H4 Securing the Homeland
  • H3 Newsroom
  • H4 News Releases and Statements
  • H4 Latest High-Profile Arrests
  • H4 Feature Stories
  • H4 Multimedia
  • H4 Social Media
  • H4 Speeches and Testimonies
  • H4 ERO Statistics Dashboard
  • H4 2024 Year in Review
  • H2 Breadcrumb
  • H1 How Do You “Self-Deport"?
  • H1 Victims Of Immigration Crime Engagement (VOICE) Office duplicate H1
  • H1 Partner With ICE Through the 287(g) Program duplicate H1
  • H1 Immigration Enforcement Frequently Asked Questions duplicate H1
  • H1 Worst of the Worst duplicate H1
  • H3 Ever wonder who ICE officers and agents are arresting in your community? skipped
  • H1 America Needs You duplicate H1
  • H1 How Do You “Self-Deport"? duplicate H1
  • H1 Victims Of Immigration Crime Engagement (VOICE) Office duplicate H1
  • H1 Partner With ICE Through the 287(g) Program duplicate H1
  • H1 Immigration Enforcement Frequently Asked Questions duplicate H1
  • H1 Worst of the Worst duplicate H1
  • H3 Ever wonder who ICE officers and agents are arresting in your community? skipped
  • H1 America Needs You duplicate H1
  • H1 How Do You “Self-Deport"? duplicate H1
  • H2 Resources
  • H2 Most Wanted
  • H3 Vega, Ricardo
  • H3 Cuen-Lugo, Omar Guillerm…
  • H3 Archaga Carías, Yulan An…
  • H3 Guerero Flores, Hector R…
  • H3 Guaman-Paredes, Antonio…
  • H3 Zhang, Zhi Dong
  • H3 Vega, Ricardo
  • H3 Cuen-Lugo, Omar Guillerm…
  • H3 Archaga Carías, Yulan An…
  • H3 Guerero Flores, Hector R…
  • H3 Guaman-Paredes, Antonio…
  • H3 Zhang, Zhi Dong
  • H3 Vega, Ricardo
  • H3 Cuen-Lugo, Omar Guillerm…
  • H3 Archaga Carías, Yulan An…
  • H2 Local Footer Navigation
  • H3 Address
  • H3 Related Information
  • H3 Contact Us
  • H2 ICE USWDS Footer Links
  • H2 Mobile Menu Bar
  • H2 Main Navigation on Mobile Devices

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

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

B
Form Accessibility
2 of 6 controls have issues
REVIEW
2 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="search" name="query" id="mobile-extended-search-field-small">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="query" id="extended-search-field-small">
Info::
4 control(s) properly labeled
6 controls
4 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#emailtextEnter your email addressfor/id
#commit-sevissubmitSubmitfor/id
#a2a_copy_link_texttextCopy linkfor/id
#a2apage_findtextFind any servicefor/id
#extended-search-field-smallsearch(Search)placeholder only
#mobile-extended-search-field-smallsearch(none)none

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

<input type="search" name="query" id="mobile-extended-search-field-small">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="search" name="query" id="extended-search-field-small">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Breadcrumb navigation detected
Got: aria-label
Info::
Search functionality detected
Got: role-search
Info::
12 navigation landmark(s) detected
Breadcrumbs aria-label navigation
Search role='search' landmark
Skip Link
Labeled Navigation 12 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Main Navigation
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Breadcrumb
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most Wanted
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Local Footer Navigation
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ICE USWDS Footer Links
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mobile Menu Bar
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Main Navigation on Mobile Devices
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
24px · bottom of viewport
h3 About Us
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enforcement and Removal Operations
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Homeland Security Investigations
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Newsroom
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ever wonder who ICE officers and agents …
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Ever wonder who ICE officers and agents …
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Vega, Ricardo
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cuen-Lugo, Omar Guillerm…
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Archaga Carías, Yulan An…
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Guerero Flores, Hector R…
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Guaman-Paredes, Antonio…
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Zhang, Zhi Dong
1.32:1
#000000
on
#222222
needs 3.0:1 (large text)
19px · bottom of viewport

2 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)
ElementRatioRequiredFGBGResult
h2 Main Navigation1.32:13.0:1
#000000
#222222
Fail
h2 Breadcrumb1.32:13.0:1
#000000
#222222
Fail
h2 Resources1.32:13.0:1
#000000
#222222
Fail
h2 Most Wanted1.32:13.0:1
#000000
#222222
Fail
h2 Local Footer Navigat…1.32:13.0:1
#000000
#222222
Fail
h2 ICE USWDS Footer Lin…1.32:13.0:1
#000000
#222222
Fail
h2 Mobile Menu Bar1.32:13.0:1
#000000
#222222
Fail
h2 Main Navigation on M…1.32:13.0:1
#000000
#222222
Fail
h3 About Us1.32:13.0:1
#000000
#222222
Fail
h3 Enforcement and Remo…1.32:13.0:1
#000000
#222222
Fail
h3 Homeland Security In…1.32:13.0:1
#000000
#222222
Fail
h3 Newsroom1.32:13.0:1
#000000
#222222
Fail
h3 Ever wonder who ICE …1.32:13.0:1
#000000
#222222
Fail
h3 Ever wonder who ICE …1.32:13.0:1
#000000
#222222
Fail
h3 Vega, Ricardo1.32:13.0:1
#000000
#222222
Fail
h3 Cuen-Lugo, Omar Guil…1.32:13.0:1
#000000
#222222
Fail
h3 Archaga Carías, Yul…1.32:13.0:1
#000000
#222222
Fail
h3 Guerero Flores, Hect…1.32:13.0:1
#000000
#222222
Fail
h3 Guaman-Paredes, Anto…1.32:13.0:1
#000000
#222222
Fail
h3 Zhang, Zhi Dong1.32:13.0:1
#000000
#222222
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
Alt Text Quality
2 of 56 images have issues
PASS
2 of 56 images have issues
Warning::
2 image(s) with generic alt text
Info::
20 decorative image(s) correctly marked
Info::
34 image(s) with good alt text
56 images 34 good alt text 20 decorative 2 generic
IssueCount
generic2 image(s)
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
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 ✓
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_2Utogce852uWQ9_2mqPn8_HRuwpppuTeZEQAgJU3Tgg.css?delta=7&language=en&theme=uswds_iced8_gov_theme&include=eJyFkkluwzAMRS9Ei90UyL5HyAEM2qJtNRoMUbLsnL4eYiQtAnRD_f80fkKkdQrkF6SHUF0MPgF54yiZ4AWf8j1Vh-Sv6xUaS_cFbSBtfA9tsCE2YUbNHWWbVhAZdcwjWUXfNAPPyRp_O9nDnrhex0h4us-PC3Tr46iwBMf4olXhZrPy7wIlg3EwUqQ-0jjIefWTqOzH3FgjA2uILOOa0UxcO_YZ_3jltgpiTXvDvapW5Jd3ZLw6G_A6kQZ2_EqOuHLsWNvGumophixsQRZJ7LAhYchStNSmZX2p-zDV-0H4lsJkuAjuVbmgs2Uoraslx4kXPAYoW5ie9oBdiG5tVrWBaiPV_iHY6x-08djW
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/default/files/css/css_2Utogce852uWQ9_2mqPn8_HRuwpppuTeZEQAgJU3Tgg.css?delta=7&language=en&theme=uswds_iced8_gov_theme&include=eJyFkkluwzAMRS9Ei90UyL5HyAEM2qJtNRoMUbLsnL4eYiQtAnRD_f80fkKkdQrkF6SHUF0MPgF54yiZ4AWf8j1Vh-Sv6xUaS_cFbSBtfA9tsCE2YUbNHWWbVhAZdcwjWUXfNAPPyRp_O9nDnrhex0h4us-PC3Tr46iwBMf4olXhZrPy7wIlg3EwUqQ-0jjIefWTqOzH3FgjA2uILOOa0UxcO_YZ_3jltgpiTXvDvapW5Jd3ZLw6G_A6kQZ2_EqOuHLsWNvGumophixsQRZJ7LAhYchStNSmZX2p-zDV-0H4lsJkuAjuVbmgs2Uoraslx4kXPAYoW5ie9oBdiG5tVrWBaiPV_iHY6x-08djW ✓Inline @media print Not detected ✗
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 33 passed
PASS
97

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Guerero Flores, Hector R… Wanted for: RICO div#slick-66727030eb1 > div.slick-list > div.slick-track > li.slick__slide

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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
●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>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`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
○`<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.
○`<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.
○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.

Send Feedback