Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 4 REVIEW 3 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.

Link & Button Quality

Action

2 issue(s) across 106 links and 11 buttons

REVIEW

2 issue(s) across 106 links and 11 buttons

1 link(s) with no accessible text

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

Got: a#main-content

5 link(s) open in new tab without warning

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

Got: https://www.facebook.com/sharer/sharer.php?u=https%3A//www.ojp.gov/; https://twitter.com/intent/tweet?url=https%3A//www.ojp.gov/&text=Office%20of%…; https://www.linkedin.com/shareArticle?mini=true&url=https%3A//www.ojp.gov/&ti…; https://reddit.com/submit?url=https%3A//www.ojp.gov/&title=Office%20of%20Just…; https://pinterest.com/pin/create/button?url=https%3A//www.ojp.gov/&media=http…

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

100 link(s) with descriptive text

106 links

1 empty

0 generic text

5 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/sharer/sharer.p…	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/intent/tweet?url=htt…	X	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/shareArticle?mi…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://reddit.com/submit?url=https%3A//…	Reddit	new tab	Add '(opens in new tab)' to text
https://pinterest.com/pin/create/button?…	Pinterest	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

110 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.facebook.com/sharer/sharer.php?u=https%3A//www.ojp.gov/; https://twitter.com/intent/tweet?url=https%3A//www.ojp.gov/&text=Office%20of%…; https://www.linkedin.com/shareArticle?mini=true&url=https%3A//www.ojp.gov/&ti…; https://reddit.com/submit?url=https%3A//www.ojp.gov/&title=Office%20of%20Just…; https://pinterest.com/pin/create/button?url=https%3A//www.ojp.gov/&media=http…

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 (#101 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

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Lock ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Navigation UX

Action

3 navigation pattern(s)

REVIEW

3 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

Back-to-top link detected

3 navigation landmark(s) detected

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

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 3 pass AA only

p Here's how you know

2.18:1

#000000

#1A4480

needs 4.5:1 (normal text)

16px · top of page (header area)

span Here's how you know

2.18:1

#000000

#1A4480

needs 4.5:1 (normal text)

16px · above the fold

p website belongs to an official governmen…

2.00:1

#000000

#16416A

needs 4.5:1 (normal text)

16px · above the fold

strong Secure .gov websites use HTTPS

1.81:1

#000000

#0F3A63

needs 3.0:1 (large text)

16px · above the fold

strong lock

1.86:1

#000000

#113C65

needs 3.0:1 (large text)

16px · above the fold

p ) or

1.94:1

#000000

#143F68

needs 4.5:1 (normal text)

16px · above the fold

strong https://

1.68:1

#000000

#0A355E

needs 3.0:1 (large text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Office of Justice Pr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Secondary Footer lin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Office of Justice Pr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Home \| Office of Jus…	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a Skip to main content	20.47:1	4.5:1	#000000	#FCFCFC	Pass
p An official website …	6.25:1	4.5:1	#000000	#748EB2	Pass
p Here's how you know	2.18:1	4.5:1	#000000	#1A4480	Fail
span Here's how you know	2.18:1	4.5:1	#000000	#1A4480	Fail
strong Official websites us…	4.15:1	3.0:1	#000000	#4E7199	Pass
strong .gov	3.09:1	3.0:1	#000000	#335E87	Pass
p website belongs to a…	2.00:1	4.5:1	#000000	#16416A	Fail
strong Secure .gov websites…	1.81:1	3.0:1	#000000	#0F3A63	Fail
strong lock	1.86:1	3.0:1	#000000	#113C65	Fail
p ) or	1.94:1	4.5:1	#000000	#143F68	Fail
strong https://	1.68:1	3.0:1	#000000	#0A355E	Fail
p means you’ve safel…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Menu	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Program Offices	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Program Offices	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Bureau of Justice As…	21.00:1	4.5:1	#000000	#FFFFFF	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.

A+

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

Heading Hierarchy

8 headings, 1 skip(s)

PASS

8 headings, 1 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

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

H1 Office of Justice Programs
H4 Grant Application Resource Guide skipped
H4 Learn about JustGrants, DOJ's Grants Management System
H3 Office of Justice Programs
H4 MORE TOPICS
H4 NEWS CENTER
H4 OTHER RESOURCES
H2 Secondary Footer link menu

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

A+

Alt Text Quality

All 18 images OK

PASS

All 18 images OK

1 image(s) with alt text over 125 characters

2 decorative image(s) correctly marked

15 image(s) with good alt text

18 images 15 good alt text 2 decorative

Issue	Count
too long	1 image(s)

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#gsc-i-id1	text	Search	aria-label

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /sites/g/files/xyckuh241/files/css/css_zxEGTDXeP9ngdNso24-Bomoquys4mkHkVPDlu-SLlg8.css?delta=2&language=en&theme=ojp&include=eJxtUNGKwzAM-6H0_EnBcUyX1o1L7I7lvv5y3Qob7MFYEpZAppVzcW2x1MzVkyit8IYDCZp12NgMZ7ZA2hhyO3aUH1zw8SE4JuEbY-b21Ku2DaX8csi6RLthK3WGNxz44VLqeiW8aBDsenjMxUjv3DpoZVIJlZZmw6z7PtyRsDl80YIuOyQ5eMKap1kln8qYa08JjSfzLqPU4JFen4ALRCQarUsqUryfNxkdz44GnzRYN-cN_kP_AD3ThNk

Print Stylesheet ✓ Print Optimized

Print stylesheet /sites/g/files/xyckuh241/files/css/css_zxEGTDXeP9ngdNso24-Bomoquys4mkHkVPDlu-SLlg8.css?delta=2&language=en&theme=ojp&include=eJxtUNGKwzAM-6H0_EnBcUyX1o1L7I7lvv5y3Qob7MFYEpZAppVzcW2x1MzVkyit8IYDCZp12NgMZ7ZA2hhyO3aUH1zw8SE4JuEbY-b21Ku2DaX8csi6RLthK3WGNxz44VLqeiW8aBDsenjMxUjv3DpoZVIJlZZmw6z7PtyRsDl80YIuOyQ5eMKap1kln8qYa08JjSfzLqPU4JFen4ALRCQarUsqUryfNxkdz44GnzRYN-cN_kP_AD3ThNk ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 24 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

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
Grant Application Resource Guide `div.layout__region > div.block > div.card__body > h4.card__headline`

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.

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

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

○`<frame>` or `<iframe>` elements have a title

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

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