Skip to content
https://trade.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 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
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 3 <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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

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

6 pass 14 fail WCAG AA 2 pass AA only
h1 International Trade Administration
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
32px · bottom of viewport
h2 National AI Center: Gateway for AI Expor…
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About ITA
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Learn How To Export
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Global Business Navigator Chatbot
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Footer
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Global Business Navigator Chatbot
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Limitations
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Privacy
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Translation
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Limitations
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Privacy
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Translation
2.44:1
#000000
on
#0000FF
needs 3.0:1 (large text)
19px · bottom of viewport
p website belongs to an official governmen…
2.13:1
#000000
on
#453F60
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

1 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 International Trade …2.44:13.0:1
#000000
#0000FF
Fail
h2 National AI Center: …2.44:13.0:1
#000000
#0000FF
Fail
h2 About ITA2.44:13.0:1
#000000
#0000FF
Fail
h2 Learn How To Export2.44:13.0:1
#000000
#0000FF
Fail
h2 Global Business Navi…2.44:13.0:1
#000000
#0000FF
Fail
h2 Footer2.44:13.0:1
#000000
#0000FF
Fail
h2 Global Business Navi…2.44:13.0:1
#000000
#0000FF
Fail
h3 Limitations2.44:13.0:1
#000000
#0000FF
Fail
h3 Privacy2.44:13.0:1
#000000
#0000FF
Fail
h3 Translation2.44:13.0:1
#000000
#0000FF
Fail
h3 Limitations2.44:13.0:1
#000000
#0000FF
Fail
h3 Privacy2.44:13.0:1
#000000
#0000FF
Fail
h3 Translation2.44:13.0:1
#000000
#0000FF
Fail
title International Trade …21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
div Official Website of …21.00:14.5:1
#000000
#FFFFFF
Pass
a Here’s how you kno…21.00:14.5:1
#000000
#FFFFFF
Pass
strong Official websites us…3.14:13.0:1
#000000
#005EA5
Pass
strong .gov3.14:13.0:1
#000000
#005EA5
Pass
p website belongs to a…2.13:14.5:1
#000000
#453F60
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
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN ASIDE "official-website-banner" CONTENTINFO footer

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+
Heading Hierarchy
13 headings
PASS
13 headings
Info::
Single H1 present
  • H1 International Trade Administration
  • H2 National AI Center: Gateway for AI Exports
  • H2 About ITA
  • H2 Learn How To Export
  • H2 Global Business Navigator Chatbot Beta
  • H3 Limitations
  • H3 Privacy
  • H3 Translation
  • H2 Footer
  • H2 Global Business Navigator Chatbot Beta
  • H3 Limitations
  • H3 Privacy
  • H3 Translation
A+
Alt Text Quality
All 15 images OK
PASS
All 15 images OK
Info::
15 image(s) with good alt text
15 images 15 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#header-searchtextSearch ITAfor/id
#header-search-mobiletextSearch ITAfor/id
#a2a_copy_link_texttextCopy linkfor/id
#a2apage_findtextFind any servicefor/id
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 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 24 passed
PASS
96

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

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
section.ita-landing-page > article.layout-container > p > a.chatbot-launcher section.ita-landing-page > article.layout-container > p > a.chatbot-launcher
body > p > a.chatbot-launcher body > p > a.chatbot-launcher

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.

○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.
●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
●No element has a `[tabindex]` value greater than 0
●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
○`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.
○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.

Send Feedback