Accessibility

F

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-0x1sfo

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://usdoj.gov/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://usdoj.gov/manifest.json

Manifest contains invalid JSON.

D

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.

D

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 ✗

D

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Skip navigation link detected

Back-to-top link detected

2 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 2 <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.

B

Heading Hierarchy

3 headings

REVIEW

3 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 Utilities
H2 Our Values
H2 From Our Most Wanted Files

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C

Link & Button Quality

Action

3 issue(s) across 107 links and 14 buttons

REVIEW

3 issue(s) across 107 links and 14 buttons

1 link(s) with no accessible text

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

Got: a#main-content

10 link(s) open in new tab without warning

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

Got: https://www.fcc.gov/consumers/guides/711-telecommunications-relay-service; https://www.fcc.gov/trs; https://public.govdelivery.com/accounts/USDOJ/subscriber/new; https://x.com/TheJusticeDept; https://www.facebook.com/DOJ; http://www.youtube.com/TheJusticeDepartment; https://www.instagram.com/thejusticedept/; https://www.linkedin.com/company/usdoj/mycompany/; https://vote.gov/; https://www.usa.gov/

2 button(s) with no accessible text

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

Got: button.usa-button (#106 on page); button.usa-button (#273 on page)

96 link(s) with descriptive text

107 links

1 empty

0 generic text

10 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://www.fcc.gov/consumers/guides/711…	TTY: 711Links to other governm…	new tab	Add '(opens in new tab)' to text
https://www.fcc.gov/trs	TRS InfoLinks to other governm…	new tab	Add '(opens in new tab)' to text
https://public.govdelivery.com/accounts/…	Signup for Email UpdatesLinks …	new tab	Add '(opens in new tab)' to text
https://x.com/TheJusticeDept	twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/DOJ	facebook	new tab	Add '(opens in new tab)' to text
http://www.youtube.com/TheJusticeDepartm…	youtube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/thejusticedept…	instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/usdoj/m…	linkedin	new tab	Add '(opens in new tab)' to text
https://vote.gov/	Vote.govLinks to other governm…	new tab	Add '(opens in new tab)' to text
https://www.usa.gov/	Contact USA.govLinks to other …	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

108 links and buttons have descriptive text

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

a#main-content

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.fcc.gov/consumers/guides/711-telecommunications-relay-service; https://www.fcc.gov/trs; https://public.govdelivery.com/accounts/USDOJ/subscriber/new; https://x.com/TheJusticeDept; https://www.facebook.com/DOJ; http://www.youtube.com/TheJusticeDepartment; https://www.instagram.com/thejusticedept/; https://www.linkedin.com/company/usdoj/mycompany/; https://vote.gov/; https://www.usa.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-button (#106 on page); button.usa-button (#273 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

C

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 13 fail WCAG AA

REVIEW

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

7 pass 13 fail WCAG AA 1 pass AA only

h2 Utilities

1.66:1

#000000

on

#1A3359

needs 3.0:1 (large text)

24px · mid-page

p An official website of the United States…

1.54:1

#000000

on

#162E51

needs 4.5:1 (normal text)

16px · top of page (header area)

p Here's how you know

1.54:1

#000000

on

#162E51

needs 4.5:1 (normal text)

16px · top of page (header area)

strong Official websites use .gov

1.54:1

#000000

on

#162E51

needs 3.0:1 (large text)

16px · above the fold

strong Secure .gov websites use HTTPS

1.99:1

#000000

on

#213F6C

needs 3.0:1 (large text)

16px · above the fold

strong lock

1.90:1

#000000

on

#1E3C67

needs 3.0:1 (large text)

16px · above the fold

p ) or

1.84:1

#000000

on

#1D3A64

needs 4.5:1 (normal text)

16px · above the fold

strong https://

1.69:1

#000000

on

#18345E

needs 3.0:1 (large text)

16px · above the fold

p means you’ve safely connected to the .…

1.74:1

#000000

on

#1C365E

needs 4.5:1 (normal text)

16px · above the fold

a Our Offices

1.61:1

#000000

on

#183155

needs 4.5:1 (normal text)

16px · mid-page

a Find Help

1.52:1

#000000

on

#142D50

needs 4.5:1 (normal text)

16px · mid-page

a Contact Us

1.44:1

#000000

on

#11294A

needs 4.5:1 (normal text)

16px · mid-page

label Search

1.39:1

#000000

on

#102647

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Utilities	1.66:1	3.0:1	#000000	#1A3359	Fail
h2 Our Values	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 From Our Most Wanted…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Department of Justic…	18.43:1	4.5:1	#000000	#F0F0F0	Pass
a Skip to main content	8.15:1	4.5:1	#000000	#99A2B0	Pass
p An official website …	1.54:1	4.5:1	#000000	#162E51	Fail
p Here's how you know	1.54:1	4.5:1	#000000	#162E51	Fail
span Here's how you know	5.37:1	4.5:1	#000000	#738297	Pass
strong Official websites us…	1.54:1	3.0:1	#000000	#162E51	Fail
strong .gov	9.06:1	3.0:1	#000000	#A2ABB9	Pass
p website belongs to a…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong Secure .gov websites…	1.99:1	3.0:1	#000000	#213F6C	Fail
strong lock	1.90:1	3.0:1	#000000	#1E3C67	Fail
p ) or	1.84:1	4.5:1	#000000	#1D3A64	Fail
strong https://	1.69:1	3.0:1	#000000	#18345E	Fail
p means you’ve safel…	1.74:1	4.5:1	#000000	#1C365E	Fail
a Our Offices	1.61:1	4.5:1	#000000	#183155	Fail
a Find Help	1.52:1	4.5:1	#000000	#142D50	Fail
a Contact Us	1.44:1	4.5:1	#000000	#11294A	Fail
label Search	1.39:1	4.5:1	#000000	#102647	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

10 landmarks

PASS

10 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <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+

Alt Text Quality

All 56 images OK

PASS

All 56 images OK

1 decorative image(s) correctly marked

55 image(s) with good alt text

56 images 55 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-field-en-small-desktop	search	Search	for/id
#mobile-btn	checkbox	Menu Close About About The Attorney General Organizational Chart Budget & Performance History Privacy Program Our Work News News Press Releases Speeches Videos Photo Galleries Blogs Podcasts Resources Resources Guidance Documents Forms Publications Information for Victims in Large Cases Justice Manual Business and Contracts Grants Employment Employment Why Justice ? Benefits DOJ Vacancies Legal Careers at DOJ Our Offices Find Help Contact Us	for/id
#search-field-en-small	search	Search	for/id

A

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 30 passed

PASS

94

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.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.block-live_stream__content_media > div.block-liveStream-embed__wrapper > div.responsive-embed > iframe `div.block-live_stream__content_media > div.block-liveStream-embed__wrapper > div.responsive-embed > iframe`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Kun Jiang DEA Field Office: New York Southern Wanted For: Fentanyl importation … `div > div.most-wanted-view > div.item-list > ul.slick-initialized`

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

●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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●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

●Uses ARIA roles only on compatible elements

●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

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

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