Skip to content
https://energystar.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 REVIEW 3 FIX
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search
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
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Back to top ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
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 1 pass AA only
h1 The simple choice for saving energy.
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
32px · bottom of viewport
h2 ENERGY STAR certified products help you …
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Efficient Home Upgrades Tax Credits & Re…
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tax credits for residential energy effic…
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ways to Save Energy at Home
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
24px · bottom of viewport
h2 New Homes & Apartments
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Strategies for Buildings & Plants
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ENERGY STAR Home Upgrade
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Rebate Finder
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Save Energy.
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Learn More.
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Stay Informed.
2.40:1
#000000
on
#0E4D82
needs 3.0:1 (large text)
19px · bottom of viewport
strong .gov
2.90:1
#000000
on
#5F554F
needs 3.0:1 (large text)
16px · above the fold
p website belongs to an official governmen…
3.81:1
#000000
on
#6D676C
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The simple choice fo…2.40:13.0:1
#000000
#0E4D82
Fail
h2 ENERGY STAR certifie…2.40:13.0:1
#000000
#0E4D82
Fail
h2 Efficient Home Upgra…2.40:13.0:1
#000000
#0E4D82
Fail
h2 Tax credits for resi…2.40:13.0:1
#000000
#0E4D82
Fail
h2 Ways to Save Energy …2.40:13.0:1
#000000
#0E4D82
Fail
h2 New Homes & Apartmen…2.40:13.0:1
#000000
#0E4D82
Fail
h2 Strategies for Build…2.40:13.0:1
#000000
#0E4D82
Fail
h2 ENERGY STAR Home Upg…2.40:13.0:1
#000000
#0E4D82
Fail
h3 Rebate Finder2.40:13.0:1
#000000
#0E4D82
Fail
h3 Save Energy.2.40:13.0:1
#000000
#0E4D82
Fail
h3 Learn More.2.40:13.0:1
#000000
#0E4D82
Fail
h3 Stay Informed.2.40:13.0:1
#000000
#0E4D82
Fail
title Homepage | ENERGY ST…19.26:14.5:1
#000000
#F5F5F5
Pass
a Skip to main content19.26:14.5:1
#000000
#F5F5F5
Pass
p An official website …21.00:14.5:1
#000000
#FFFFFF
Pass
p Here’s how you kno…21.00:14.5:1
#000000
#FFFFFF
Pass
span Here’s how you kno…15.08:14.5:1
#000000
#DFDAD0
Pass
strong Official websites us…3.70:13.0:1
#000000
#746456
Pass
strong .gov2.90:13.0:1
#000000
#5F554F
Fail
p website belongs to a…3.81:14.5:1
#000000
#6D676C
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::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "skip-to-main" MAIN CONTENTINFO footer
A+
Heading Hierarchy
12 headings
PASS
12 headings
Info::
Single H1 present
  • H1 The simple choice for saving energy.
  • H2 ENERGY STAR certified products help you save energy.
  • H2 Efficient Home Upgrades Tax Credits & Rebates
  • H3 Rebate Finder
  • H2 Tax credits for residential energy efficiency
  • H2 Ways to Save Energy at Home
  • H2 New Homes & Apartments
  • H2 Strategies for Buildings & Plants
  • H2 ENERGY STAR Home Upgrade
  • H3 Save Energy.
  • H3 Learn More.
  • H3 Stay Informed.
A+
Alt Text Quality
All 20 images OK
PASS
All 20 images OK
Info::
1 decorative image(s) correctly marked
Info::
19 image(s) with good alt text
20 images 19 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 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="search_submit" id="edit-search-submit">
Info::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#querytextSearchfor/id
#edit-zip-code-filtertextZip Codefor/id
#edit-urltextLeave this field blankfor/id
#edit-search-submitsubmit(none)none

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

<input type="submit" name="search_submit" id="edit-search-submit">

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+
Lighthouse Accessibility Audits
Score 97/100 — 1 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
Search Submit Search div.l-header__row > div.l-header__menus > div.l-header__search > div.header-search-box

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.

○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
●Input buttons have discernible text.
●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
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●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 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.
○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
○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