Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

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

Link & Button Quality

Action

3 issue(s) across 235 links and 17 buttons

REVIEW

3 issue(s) across 235 links and 17 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/CBPgov; https://twitter.com/cbp; https://www.youtube.com/channel/UCVRj-aUsXBrlM8elk3zmLvw; https://www.flickr.com/photos/cbpphotos; https://www.instagram.com/cbpgov; https://www.linkedin.com/company/customs-and-border-protection?trk=tyah; https://public.govdelivery.com/accounts/USDHSCBP/subscriber/new

2 button(s) with no accessible text

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

Got: button.usa-nav__close (#122 on page); button#search-button

227 link(s) with descriptive text

235 links

1 empty

0 generic text

7 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/CBPgov	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/cbp	X	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCVRj-aU…	YouTube	new tab	Add '(opens in new tab)' to text
https://www.flickr.com/photos/cbpphotos	Flickr	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/cbpgov	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/customs…	Linkedin	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
<button>	(empty)	empty	Add button text or aria-label

242 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/CBPgov; https://twitter.com/cbp; https://www.youtube.com/channel/UCVRj-aUsXBrlM8elk3zmLvw; https://www.flickr.com/photos/cbpphotos; https://www.instagram.com/cbpgov; https://www.linkedin.com/company/customs-and-border-protection?trk=tyah; https://public.govdelivery.com/accounts/USDHSCBP/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 (#122 on page); button#search-button

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA 2 pass AA only

p An official website of the United States…

4.30:1

#000000

#0078AE

needs 4.5:1 (normal text)

16px · top of page (header area)

p Here’s how you know

3.29:1

#000000

#076786

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Here’s how you know

3.23:1

#000000

#01677B

needs 4.5:1 (normal text)

16px · above the fold

strong Official websites use .gov

2.37:1

#000000

#21505C

needs 3.0:1 (large text)

16px · above the fold

strong .gov

2.23:1

#000000

#2F4A54

needs 3.0:1 (large text)

16px · above the fold

p website belongs to an official governmen…

3.80:1

#000000

#496F72

needs 4.5:1 (normal text)

16px · above the fold

p ) or

2.05:1

#000000

#1C4173

needs 4.5:1 (normal text)

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

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)

Element	Ratio	Required	FG	BG	Result
h2 News & Updates	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Travel	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Trade	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Border Security	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Newsroom	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About CBP	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Careers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Employee Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title U.S. Customs and Bor…	18.07:1	4.5:1	#000000	#EDEEEE	Pass
a Skip to main content	18.07:1	4.5:1	#000000	#EDEEEE	Pass
p An official website …	4.30:1	4.5:1	#000000	#0078AE	Fail
p Here’s how you kno…	3.29:1	4.5:1	#000000	#076786	Fail
span Here’s how you kno…	3.23:1	4.5:1	#000000	#01677B	Fail
strong Official websites us…	2.37:1	3.0:1	#000000	#21505C	Fail
strong .gov	2.23:1	3.0:1	#000000	#2F4A54	Fail
p website belongs to a…	3.80:1	4.5:1	#000000	#496F72	Fail
strong Secure .gov websites…	4.41:1	3.0:1	#000000	#6C7478	Pass
strong lock	6.07:1	3.0:1	#000000	#A78270	Pass
p ) or	2.05:1	4.5:1	#000000	#1C4173	Fail
strong https://	4.20:1	3.0:1	#000000	#697266	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

22 landmarks

PASS

22 landmarks

<main> landmark present

3 <nav> landmark(s) found

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

Heading Hierarchy

17 headings

PASS

17 headings

Multiple H1 headings (7 found)

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

H3 Travel
H3 Trade
H3 Border Security
H3 Newsroom
H3 About CBP
H3 Careers
H3 Employee Resources
H1 Join CBP: Your Skills and Dedication are Rewarded
H1 New IEEPA Duty Refunds Webpage duplicate H1
H1 CBP Welcomes You to FIFA World Cup 2026™ duplicate H1
H1 Join CBP: Your Skills and Dedication are Rewarded duplicate H1
H1 New IEEPA Duty Refunds Webpage duplicate H1
H1 CBP Welcomes You to FIFA World Cup 2026™ duplicate H1
H1 Join CBP: Your Skills and Dedication are Rewarded duplicate H1
H2 News & Updates
H3 Smart Wall Map
H3 Stats and Summaries Dashboards

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

A+

Alt Text Quality

1 of 29 images have issues

PASS

1 of 29 images have issues

1 image(s) with generic alt text

3 decorative image(s) correctly marked

25 image(s) with good alt text

29 images 25 good alt text 3 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#gsc-i-id1	text	pesquisar	aria-label
#header-search-bar1	search	Enter Search Term	for/id

404 Error Page

HTTP 404, custom page

PASS

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

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

External print stylesheet detected

Got: /sites/default/files/css/css_W8ioCtgXDnT1SoCnmAyICpCOZ3sSty2X1KosCiiyFXM.css?delta=2&language=en&theme=cbpd8_gov_theme&include=eJxlT1lywyAMvZAGfnsbRiDFphbLILDjnL4ep06b9udJbxkt6IWr4M7N4qsFL_jYrRSkmCcIvtKHm8rq-syJ7cHdr_Bfe5LiUSAsTLGX5jCE0iiWbF-dubWSO2eCIKi628SqOLHCEWBLbVQUg594fwq5tIQSHwx87xLzckW-KVRsODWss17Oj2JGrsNL1JkJVGJY7IkmqL7xhPG4bIhskfr8Zp2fge7aOVmPyjB0o2sZrJE3tSeaVGgIwxaSy4XY3ZjJ4zHpn3JmdLSVd_ssX3I_mtY

Print Stylesheet ✓ Print Optimized

Print stylesheet /sites/default/files/css/css_W8ioCtgXDnT1SoCnmAyICpCOZ3sSty2X1KosCiiyFXM.css?delta=2&language=en&theme=cbpd8_gov_theme&include=eJxlT1lywyAMvZAGfnsbRiDFphbLILDjnL4ep06b9udJbxkt6IWr4M7N4qsFL_jYrRSkmCcIvtKHm8rq-syJ7cHdr_Bfe5LiUSAsTLGX5jCE0iiWbF-dubWSO2eCIKi628SqOLHCEWBLbVQUg594fwq5tIQSHwx87xLzckW-KVRsODWss17Oj2JGrsNL1JkJVGJY7IkmqL7xhPG4bIhskfr8Zp2fge7aOVmPyjB0o2sZrJE3tSeaVGgIwxaSy4XY3ZjJ4zHpn3JmdLSVd_ssX3I_mtY ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

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

●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

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

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