Skip to content
https://gpo.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN CONTENTINFO footer

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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title GPO Project ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
a Who We Are
1.66:1
#FFFFFF
on
#BDCBD3
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
strong Our Agency
1.54:1
#000000
on
#002F57
needs 3.0:1 (large text)
16px · top of page (header area)
a Mission, Vision, and Values
1.68:1
#000000
on
#163651
needs 4.5:1 (normal text)
16px · top of page (header area) · 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)
ElementRatioRequiredFGBGResult
h1 Congressionally Mand…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 GPO Strategic Plan F…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 GPO Named Best Emplo…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 GPO Services for Fed…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 GPO Named America's …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Our Customers Explai…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GPO Director Present…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A Game Changer on th…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Fifty Years at Laure…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GPO Director Names M…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GPO Director Appoint…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GPO and the Library …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Events and Training21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Facebook Feed21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Free Government Info…21.00:13.0:1
#000000
#FFFFFF
Pass
title U.S. Government Publ…21.00:14.5:1
#000000
#FFFFFF
Pass
a Who We Are1.66:14.5:1
#FFFFFF
#BDCBD3
Fail
strong Our Agency1.54:13.0:1
#000000
#002F57
Fail
a Mission, Vision, and…1.68:14.5:1
#000000
#163651
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 3 failing, 17 passed
REVIEW
82

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Congressionally Mandated Reports Read More form#form > div#wrapper > div#myCarousel > div.carousel-inner

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
Congressionally Mandated Reports Read More form#form > div#wrapper > div#myCarousel > div.carousel-inner

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
Read More div.container > div.carousel-caption > p > a#ctl00_cphHeader_T97BC6AE4003_carouselList_ctrl0_slidesRepeater_ctl00_slideButton
GPO Director Presents FY2027 Appropriations Request to Congress a > div.row > div.col-md-12 > h2.featurette-heading
The U.S. Government Publishing Office (GPO) Director Hugh Nathanial Halpern pre… div.row > div.col-md-12 > p.lead > span.sfnewsSummary
A Game Changer on the Press Floor a > div.row > div.col-md-12 > h2.featurette-heading
When the new press on GPO’s production floor roars to life, it doesn’t just pri… div.row > div.col-md-12 > p.lead > span.sfnewsSummary
Fifty Years at Laurel a > div.row > div.col-md-12 > h2.featurette-heading
For 50 years, GPO’s Distribution Center in Laurel, Maryland, has quietly played… div.row > div.col-md-12 > p.lead > span.sfnewsSummary
GPO Director Names Managing Director of Government Integrated Print Services a > div.row > div.col-md-12 > h2.featurette-heading
U.S. Government Publishing Office (GPO) Director Hugh Nathanial Halpern named R… div.row > div.col-md-12 > p.lead > span.sfnewsSummary
GPO Director Appoints Leaders To Depository Library Council a > div.row > div.col-md-12 > h2.featurette-heading
U.S. Government Publishing Office (GPO) Director Hugh Nathanial Halpern, on the… div.row > div.col-md-12 > p.lead > span.sfnewsSummary
GPO and the Library of Congress Digitize 10,000 Volumes of the United States Se… a > div.row > div.col-md-12 > h2.featurette-heading
U.S. Government Publishing Office (GPO) achieved a major milestone by uploading… div.row > div.col-md-12 > p.lead > span.sfnewsSummary
View More News div.col-md-7 > div > p > a.btn
Testing Accessible Web Applications and Forms li.sfeventListItem > div.post-preview > a > p.lead
Dates: April 22 – 23 Location: Online Cost: $775 li.sfeventListItem > div.post-preview > a > p.text-muted
Dates: div.post-preview > a > p.text-muted > strong
Location: div.post-preview > a > p.text-muted > strong
Cost: div.post-preview > a > p.text-muted > strong
Testing Accessible Web Pages li.sfeventListItem > div.post-preview > a > p.lead
Dates: April 23 Location: Online Cost: $575 li.sfeventListItem > div.post-preview > a > p.text-muted
Dates: div.post-preview > a > p.text-muted > strong
Location: div.post-preview > a > p.text-muted > strong
Cost: div.post-preview > a > p.text-muted > strong
View All Events div.col-md-4 > div.sfContentBlock > p > a.btn
THE OFFICIAL WEBSITE OF THE U.S. GOVERNMENT PUBLISHING OFFICE div#wrapper > div.sfContentBlock > footer > p
Accessibility | Privacy | COOP | Inspector General div#wrapper > div.sfContentBlock > footer > p
Accessibility div.sfContentBlock > footer > p > a
Privacy div.sfContentBlock > footer > p > a
COOP div.sfContentBlock > footer > p > a
Inspector General div.sfContentBlock > footer > p > a

These are opportunities to improve the legibility of your content.

○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Touch targets have sufficient size and spacing.
●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.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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.
○No element has a `[tabindex]` value greater than 0
○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.
○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.
A
Heading Hierarchy
30 headings
PASS
30 headings
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H4 Our Agency
  • H4 News and Media
  • H4 Careers
  • H4 Agencies
  • H4 Vendors
  • H4 Search, Review, and Access
  • H4 Students, Parents, and Educators
  • H4 Visit Our Partners
  • H1 Congressionally Mandated Reports
  • H1 GPO Strategic Plan FY2023-2027 duplicate H1
  • H1 GPO Named Best Employer in America for New Graduates duplicate H1
  • H1 GPO Services for Federal Agencies duplicate H1
  • H1 GPO Named America's Best Employer Four Years in a Row duplicate H1
  • H1 Our Customers Explain the Advantages of Partnering with GPO duplicate H1
  • H2 Latest News
  • H2 GPO Director Presents FY2027 Appropriations Request to Congress
  • H2 A Game Changer on the Press Floor
  • H2 Fifty Years at Laurel
  • H2 GPO Director Names Managing Director of Government Integrated Print Services
  • H2 GPO Director Appoints Leaders To Depository Library Council
  • H2 GPO and the Library of Congress Digitize 10,000 Volumes of the United States Serial Set
  • H2 Events and Training
  • H2 Facebook Feed
  • H2 Free Government Information Resources
  • H2 GovInfo
  • H2 Ben’s Guide to the U.S. Government
  • H2 Catalog of U.S. Government Publications
  • H2 Government Book Talk
  • H2 U.S. Government Bookstore
  • H2 Locate a Federal Depository Library

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
All 10 images OK
PASS
All 10 images OK
Info::
2 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
10 images 8 good alt text 2 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 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="submit" name="ctl00$cphHeader$T97BC6AE4030$ctl00$ctl00$searchButton" id="cphHeader_T97BC6AE4030_ctl00_ctl00_searchButton">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#srch-termtextSearchfor/id
#cphHeader_T97BC6AE4030_ctl00_ctl00_searchTextBoxtextSearch Text Boxfor/id
#cphHeader_T97BC6AE4030_ctl00_ctl00_searchButtonsubmit(none)none

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

<input type="submit" name="ctl00$cphHeader$T97BC6AE4030$ctl00$ctl00$searchButton" id="cphHeader_T97BC6AE4030_ctl00_ctl00_searchButton">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback