Skip to content
https://eia.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Favicon & Branding
Action
4 icon(s) detected
FIX
4 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 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
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO footer

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

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Heading Hierarchy
70 headings, 1 skip(s)
REVIEW
70 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 U.S. Energy Information Administration - EIA - Independent Statistics and Analysis
  • H3 Petroleum & Other Liquids skipped
  • H3 Natural Gas
  • H3 Electricity
  • H3 Consumption & Efficiency
  • H3 Coal
  • H3 Renewable & Alternative Fuels
  • H3 Nuclear & Uranium
  • H3 Total Energy
  • H3 A-Z Index
  • H3 Analysis & Projections
  • H3 Markets & Finance
  • H3 Environment
  • H3 Energy Disruptions
  • H3 A-Z Index
  • H3 U.S. States
  • H3 International
  • H3 A-Z Index
  • H3 Glossary
  • H3 Data Tools, Apps, & Maps
  • H3 Open Data
  • H3 EIA Beta
  • H3 Open Source Code
  • H3 All Reports & Publications
  • H3 EIA Survey Forms
  • H3 Email Updates
  • H3 RSS Feeds
  • H3 Follow us. . .
  • H3 A-Z Index
  • H3 Today in Energy
  • H3 Energy Explained
  • H3 For Teachers
  • H3 Glossary
  • H3 FAQs
  • H3 A-Z Index
  • H3 What's New?
  • H3 Press Room
  • H3 A-Z Index
  • H2 Today in Energy More Today in Energy
  • H3 Natural gas inventories at the end of winter heating season were near five-year average ›
  • H3 Previously in Today in Energy
  • H2 What's New
  • H3 Coming Up
  • H2 Top Picks
  • H2 Data, Analysis, & Projections
  • H3 Natural Gas
  • H3 Electricity
  • H3 Nuclear & Uranium
  • H3 Consumption & Efficiency
  • H3 Analysis & Projections
  • H3 Petroleum & Other Liquids
  • H3 Coal
  • H3 Renewable & Alternative Fuels
  • H3 Total Energy
  • H2 Data Tools, Apps, & MapsMore Data Tools, Apps, & Maps
  • H3 Crude Import Tracking Tool
  • H3 API Query Browser
  • H3 STEO Data Browser
  • H3 Total Energy Data Browser
  • H3 U.S. States Energy Portal
  • H3 U.S. Energy Atlas
  • H2 Press RoomMore Press Room
  • H3 EIA releases the Annual Energy Outlook 2026
  • H3 Hormuz closure and related production outages are key drivers in EIA’s latest forecast
  • H3 EIA launches pilot survey on energy use at data centers
  • H3 EIA releases latest Short-Term Energy Outlook amid Middle East conflict
  • H2 Energy Education
  • H3 Energy Explained Your guide to understanding energy
  • H3 Frequently Asked Questions (FAQs)
  • H3 (empty)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

B
Form Accessibility
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="glossary">; <input type="text" name="glossary">; <input type="text" name="query" id="query">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
glossarytext(Search the glossary)placeholder only
glossarytext(Search the glossary)placeholder only
#querytext(Search eia.gov)placeholder only

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

<input type="text" name="glossary">; <input type="text" name="glossary">; <input type="text" name="query" id="query">

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

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 U.S. Energy Information Administration (EIA) ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 76/100 — 6 failing, 19 passed
REVIEW
76

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SEARCH div.search-reports-by-tags > div#headerTagSearch > form#headerTagSearchForm > button.button

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
div.addthis_toolbox > ul.social > li > a div.addthis_toolbox > ul.social > li > a
div.addthis_toolbox > ul.social > li > a div.addthis_toolbox > ul.social > li > a
div.l-body-wrapper > header > nav.navigation > a.logo div.l-body-wrapper > header > nav.navigation > a.logo

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
Open Data div.l-col > ul.above-address-links > li > a
Contact Us div.l-col > ul.above-address-links > li > a
Natural Gas div.l-row > ul.l-col > li > a
Renewable div.l-row > ul.l-col > li > a
Nuclear div.l-row > ul.l-col > li > a
Electricity div.l-row > ul.l-col > li > a
Consumption div.l-row > ul.l-col > li > a
Total Energy div.l-row > ul.l-col > li > a
Markets & Finance div.l-row > ul.l-col > li > a
Energy Disruptions div.l-row > ul.l-col > li > a
Privacy/Security div.l-row > ul.l-col > li > a
Copyright & Reuse div.l-row > ul.l-col > li > a

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 html

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●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
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●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
●All heading elements contain content.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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 a valid value for its `[lang]` attribute
○`<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
○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>`.
○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.
A+
Alt Text Quality
All 3 images OK
PASS
All 3 images OK
Info::
3 image(s) with good alt text
3 images 3 good alt text
All images have appropriate alt text.
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /global/styles/global.print.min.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /global/styles/global.print.min.css ✓Inline @media print Not detected ✗
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 U.S. Energy Informat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Today in Energy21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What's New21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Top Picks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Data, Analysis, & Pr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Data Tools, Apps, & …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Press Room21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Energy Education21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Follow us. . .21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Previously in Today …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Coming Up21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Natural Gas21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Electricity21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Nuclear & Uranium21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Consumption & Effici…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Analysis & Projectio…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Petroleum & Other Li…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Coal21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Renewable & Alternat…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Total Energy21.00:13.0:1
#000000
#FFFFFF
Pass

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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback