Skip to content
https://uschamber.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 2 icon(s)
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::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <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
Heading Hierarchy
16 headings
REVIEW
16 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 The 2026 State of American Business Address
  • H2 Making News
  • H2 Spotlight on Small Business
  • H2 Economy
  • H2 International
  • H2 More Headlines
  • H2 Artificial Intelligence
  • H2 About the U.S. Chamber
  • H2 Deep Dives on Workforce Data
  • H2 Major Initiatives
  • H2 We Work for You
  • H3 Become a Member
  • H2 Upcoming Events
  • H2 Trending Topics
  • H2 Latest Content
  • H2 Featured Topics

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA
title U.S. Chamber of Commerce | U.S. Chamber …
1.37:1
#000000
on
#002452
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
1.37:1
#000000
on
#002452
needs 4.5:1 (normal text)
16px · top of page (header area)
span U.S. Chamber of Commerce
1.26:1
#000000
on
#021C46
needs 4.5:1 (normal text)
16px · top of page (header area)
span USCC Homepage
1.21:1
#000000
on
#031841
needs 4.5:1 (normal text)
16px · top of page (header area)
span U.S. Chamber of Commerce
1.23:1
#000000
on
#031947
needs 4.5:1 (normal text)
16px · above the fold
a Topics
1.24:1
#000000
on
#0D1A40
needs 4.5:1 (normal text)
16px · above the fold
a Events
1.47:1
#000000
on
#352534
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Work
1.32:1
#000000
on
#1A1F44
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Menu
1.32:1
#000000
on
#051E55
needs 4.5:1 (normal text)
16px · above the fold
span Close menu
1.34:1
#000000
on
#061F57
needs 4.5:1 (normal text)
16px · above the fold
li Main Menu
1.35:1
#000000
on
#051F59
needs 4.5:1 (normal text)
16px · above the fold

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
h2 Making News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 More Headlines21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Major Initiatives21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We Work for You21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Upcoming Events21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trending Topics21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest Content21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Topics21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The 2026 State of Am…21.00:13.0:1
#000000
#FFFFFF
Pass
title U.S. Chamber of Comm…1.37:14.5:1
#000000
#002452
Fail
a Skip to content1.37:14.5:1
#000000
#002452
Fail
span U.S. Chamber of Comm…1.26:14.5:1
#000000
#021C46
Fail
span USCC Homepage1.21:14.5:1
#000000
#031841
Fail
span U.S. Chamber of Comm…1.23:14.5:1
#000000
#031947
Fail
a Topics1.24:14.5:1
#000000
#0D1A40
Fail
a Events1.47:14.5:1
#000000
#352534
Fail
a Work1.32:14.5:1
#000000
#1A1F44
Fail
span Menu1.32:14.5:1
#000000
#051E55
Fail
span Close menu1.34:14.5:1
#000000
#061F57
Fail
li Main Menu1.35:14.5:1
#000000
#051F59
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
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
2 of 5 <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 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+
Alt Text Quality
All 48 images OK
PASS
All 48 images OK
Info::
46 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
48 images 2 good alt text 46 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 5 controls have issues
PASS
1 of 5 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="checkbox" name="queryly_toggle" id="queryly_toggle">
Info::
4 control(s) properly labeled
5 controls
4 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#global_search_querysearchEnter your search queryfor/id
#contentTypeselectFilter by Content Typefor/id
#topicselectFilter by Topicfor/id
#queryly_querysearchSearcharia-label
#queryly_togglecheckbox(none)none

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

<input type="checkbox" name="queryly_toggle" id="queryly_toggle">

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

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 | U.S. Chamber of Commerce ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 27 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Menu div.container > ul.uscc-header-primary-actions > li#MenuBurgerListItem > button.burger-btn

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.

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
Spotlight on Small Business div.flex > div.flex-col > h2.f-heading-2 > a.flex
Economy div.flex > div.flex-col > h2.f-heading-2 > a.flex
International div.flex > div.flex-col > h2.f-heading-2 > a.flex
Artificial Intelligence div.flex > div.flex-col > h2.f-heading-2 > a.flex
For the Pursuit: The U.S. Chamber Story div.relative > span.block > strong.f-heading-expressive-1 > a.hover:text-link-off
Deep Dives on Workforce Data div.flex > div.flex-col > h2.f-heading-2 > a.flex
The State of American Business U.S. Chamber President and CEO Suzanne P. Clark … div.blocks > ul.grid > li > a.block
Brought to You by American Business America’s businesses are working together –… div.blocks > ul.grid > li > a.block
America Works Initiative We are calling on elected officials and the federal an… div.blocks > ul.grid > li > a.block
Growing America's Future Competitive, pro-growth tax policy is essential to gro… div.blocks > ul.grid > li > a.block
Small Business Small Business Grant Program Awards Wednesday, April 29 09:00 AM… div.blocks > ul.grid > li > a.block
Health Care 2026 Health Summit Thursday, April 30 09:15 AM EDT - 05:30 PM EDT U… div.blocks > ul.grid > li > a.block
Security and Resilience 2026 Building Resilience Conference Tuesday, May 05 - W… div.blocks > ul.grid > li > a.block
Technology Information and news for businesses about the latest advances in tec… div.blocks > ul.grid > li > a.block
Workforce Information on how businesses can adapt their workforce development a… div.blocks > ul.grid > li > a.block
Health Care Information about how to make quality health care more affordable, … div.blocks > ul.grid > li > a.block
○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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●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
○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
○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.
○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