Skip to content
https://treas.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 Page Title Access Denied Custom Styling Navigation Homepage Link Search Form
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
12 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 12 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
27 landmarks
REVIEW
27 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
12 <nav> landmark(s) found
Warning::
2 of 12 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

C
Form Accessibility
Action
7 of 14 controls have issues
REVIEW
7 of 14 controls have issues
Critical::
7 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">
Info::
7 control(s) properly labeled
14 controls
7 labeled
0 placeholder only
7 unlabeled
ControlTypeLabelMethod
#querytextEnter Search Term(s):for/id
#querytextEnter Search Term(s):for/id
#querytextEnter Search Term(s):for/id
#querytextEnter Search Term(s):for/id
#querytextEnter Search Term(s):for/id
#querytextEnter Search Term(s):for/id
#querytextEnter Search Term(s):for/id
commitsubmit(none)none
commitsubmit(none)none
commitsubmit(none)none
commitsubmit(none)none
commitsubmit(none)none
commitsubmit(none)none
commitsubmit(none)none

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

<input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">; <input type="submit" name="commit">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
p An official website of the United States…
1.36:1
#000000
on
#11253F
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Federal Financial Da…18.72:13.0:1
#000000
#F1F2F2
Pass
h2 Whistleblowing and F…18.72:13.0:1
#000000
#F1F2F2
Pass
h2 Stay Connected18.72:13.0:1
#000000
#F1F2F2
Pass
h2 The Public18.72:13.0:1
#000000
#F1F2F2
Pass
h2 Businesses18.72:13.0:1
#000000
#F1F2F2
Pass
h2 Financial Institutio…18.72:13.0:1
#000000
#F1F2F2
Pass
h2 Government18.72:13.0:1
#000000
#F1F2F2
Pass
h2 Data Center18.72:13.0:1
#000000
#F1F2F2
Pass
h2 Tools18.72:13.0:1
#000000
#F1F2F2
Pass
h3 Financial Sanctions18.72:13.0:1
#000000
#F1F2F2
Pass
h3 Daily Interest Rates18.72:13.0:1
#000000
#F1F2F2
Pass
h3 Treasury Hunt18.72:13.0:1
#000000
#F1F2F2
Pass
h3 Bureaus18.72:13.0:1
#000000
#F1F2F2
Pass
h3 Inspector General Si…18.72:13.0:1
#000000
#F1F2F2
Pass
h3 U.S. Government Shar…18.72:13.0:1
#000000
#F1F2F2
Pass
h3 Additional Resources18.72:13.0:1
#000000
#F1F2F2
Pass
h3 Other Government Sit…18.72:13.0:1
#000000
#F1F2F2
Pass
title Front page | U.S. De…18.43:14.5:1
#000000
#F0F0F0
Pass
a Skip to main content7.75:14.5:1
#000000
#969EA8
Pass
p An official website …1.36:14.5:1
#000000
#11253F
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+
Heading Hierarchy
67 headings
PASS
67 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 U.S. Department of the Treasury
  • H2 General Information
  • H2 Offices
  • H2 Bureaus
  • H2 Budget, Financial Reporting, Planning and Performance
  • H2 History
  • H2 Careers
  • H2 COVID19 Economic Relief
  • H2 Tax Policy
  • H2 Economic Policy
  • H2 Terrorism and Illicit Finance
  • H2 Financing the Government
  • H2 Financial Markets, Financial Institutions, and Fiscal Service
  • H2 Financial Sanctions
  • H2 Consumer Policy
  • H2 International
  • H2 Small Business Programs
  • H2 Tribal Affairs
  • H2 Interest Rates
  • H2 Treasury Coupon-Issue and Corporate Bond Yield Curve
  • H2 Federal Financial Data
  • H2 How Your Money Is Spent
  • H2 National Debt
  • H2 Quarterly Refunding
  • H2 Investor Class Auction Allotments
  • H2 Other Programs
  • H2 Treasury International Capital (TIC) System
  • H2 U.S. International Reserve Position
  • H2 Troubled Assets Relief Program
  • H2 Office of the Chief Data Officer
  • H2 Report Fraud, Waste & Abuse
  • H2 Bonds and Securities
  • H2 Grant Programs
  • H2 Treasury Payments
  • H2 Currency and Coins
  • H2 Auctions
  • H2 Kline-Miller Multiemployer Pension Reform Act of 2014
  • H2 Education
  • H2 Whistleblowing and Financial Integrity
  • H2 Taxes
  • H2 Forms
  • H2 Government Shared Services
  • H2 Tours and Library
  • H2 Featured Stories
  • H2 Press Releases
  • H2 Remarks and Statements
  • H2 Press Information
  • H2 Stay Connected
  • H2 The Public
  • H2 Businesses
  • H2 Financial Institutions
  • H2 Government
  • H2 (empty)
  • H2 Secretary Bessent
  • H2 Role of the Treasury
  • H2 Featured Stories
  • H2 Press Releases
  • H2 Data Center
  • H2 Tools
  • H3 Financial Sanctions
  • H3 Daily Interest Rates
  • H3 Treasury Hunt
  • H3 Bureaus
  • H3 Inspector General Sites
  • H3 U.S. Government Shared Services
  • H3 Additional Resources
  • H3 Other Government Sites

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
2 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
11 images 9 good alt text 2 decorative
All images have appropriate alt text.
A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 28 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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Google Privacy div.site-menu > ul > li > a
Careers div.site-menu > ul > li > a

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn More div#banner--treasury-alert > div.treasury-america250-banner > div.treasury-america250-banner__meta > a.treasury-america250-banner__cta
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.
`button`, `link`, and `menuitem` elements have accessible names
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 are distinguishable without relying on color.
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
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
`[accesskey]` values are unique
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
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
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.
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