Skip to content
https://ustr.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
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::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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.
C
Landmark Structure
Action
1 landmarks
REVIEW
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

B
Heading Hierarchy
10 headings
REVIEW
10 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
3 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 "I am convinced that American workers, farmers, ranchers, and service providers can compete with anyone else in the world, in this market and beyond – so long as they have a level playing field."
  • H1 News
  • H2 (empty)
  • H2 (empty)
  • H2 (empty)
  • H1 Leadership duplicate H1
  • H2 United States Trade Representative
  • H3 Jamieson Greer
  • H3 Ambassador Jamieson Greer was confirmed by the U.S. Senate as the 20th United States Trade Representative on February 27, 2025. As a key member of President Trump’s cabinet, Ambassador Greer has ma
  • H1 Priorities duplicate H1

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

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

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

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

3 pass 17 fail WCAG AA
title Home | United States Trade Representativ…
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Trade Agreements
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Agreements on Reciprocal Trade
1.16:1
#000000
on
#0E142E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Free Trade Agreements
1.16:1
#000000
on
#0E142E
needs 4.5:1 (normal text)
16px · above the fold
a Trade & Investment Framework Agreements
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · above the fold
a Bilateral Investment Treaties
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · above the fold
a Other Initiatives
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · above the fold
a Countries & Regions
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · above the fold
a Africa
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · above the fold
a Western Hemisphere
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · above the fold
a Southeast Asia & Pacific
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · above the fold
a Europe & Middle East
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · above the fold
a South & Central Asia
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · mid-page
a China, Mongolia & Taiwan
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · mid-page
a Japan, Korea & APEC
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · mid-page
a United States Trade Data
1.15:1
#000000
on
#0D132D
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 News10.34:13.0:1
#000000
#D7B300
Pass
h1 Leadership10.34:13.0:1
#000000
#D7B300
Pass
h1 Priorities10.34:13.0:1
#000000
#D7B300
Pass
title Home | United States…1.15:14.5:1
#000000
#0D132D
Fail
a Skip to main content1.15:14.5:1
#000000
#0D132D
Fail
a Trade Agreements1.15:14.5:1
#000000
#0D132D
Fail
a Agreements on Recipr…1.16:14.5:1
#000000
#0E142E
Fail
a Free Trade Agreement…1.16:14.5:1
#000000
#0E142E
Fail
a Trade & Investment F…1.15:14.5:1
#000000
#0D132D
Fail
a Bilateral Investment…1.15:14.5:1
#000000
#0D132D
Fail
a Other Initiatives1.15:14.5:1
#000000
#0D132D
Fail
a Countries & Regions1.15:14.5:1
#000000
#0D132D
Fail
a Africa1.15:14.5:1
#000000
#0D132D
Fail
a Western Hemisphere1.15:14.5:1
#000000
#0D132D
Fail
a Southeast Asia & Pac…1.15:14.5:1
#000000
#0D132D
Fail
a Europe & Middle East1.15:14.5:1
#000000
#0D132D
Fail
a South & Central Asia1.15:14.5:1
#000000
#0D132D
Fail
a China, Mongolia & Ta…1.15:14.5:1
#000000
#0D132D
Fail
a Japan, Korea & APEC1.15:14.5:1
#000000
#0D132D
Fail
a United States Trade …1.15:14.5:1
#000000
#0D132D
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 85/100 — 4 failing, 22 passed
REVIEW
85

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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dialog-off-canvas-main-canvas > div.masthead > div.hero-background > img div.dialog-off-canvas-main-canvas > div.masthead > div.hero-background > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-12 > nav.site-navigation > div.d-inline-block > a.site-menu-toggle div.col-12 > nav.site-navigation > div.d-inline-block > a.site-menu-toggle
div.hero-container > div > div > a div.hero-container > div > div > a

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.

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
search li#search > span > form > button.submit-mobile

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These items highlight common accessibility best practices.

○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
●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.
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`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
○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
○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
Alt Text Quality
1 of 24 images have issues
PASS
1 of 24 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
24 images 22 good alt text 1 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="EMAIL" id="mce-EMAIL">
Info::
2 control(s) properly labeled
3 controls
2 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#collapseExampletextSearch through site contentaria-label
#collapseExampletextSearch through site contentaria-label
#mce-EMAILemail(Email Address)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="email" name="EMAIL" id="mce-EMAIL">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | United States Trade Representative ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback