Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 6 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #14110f

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Link & Button Quality

2 issue(s) across 101 links and 7 buttons

REVIEW

2 issue(s) across 101 links and 7 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /resources/privacy-policy ("Learn more")

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://na4-onlineapp.dnbi.com/createApp/JCL+Energy+Partners%2C+LLC?token=A%2…; /media/literature/JCL-Standard-Terms-Conditions-Feb2026.pdf

97 link(s) with descriptive text

101 links

1 empty

1 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://na4-onlineapp.dnbi.com/createApp…	Apply for CreditSet up terms	new tab	Add '(opens in new tab)' to text
/media/literature/JCL-Standard-Terms-Con…	Terms & Conditions	new tab	Add '(opens in new tab)' to text
/resources/privacy-policy	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Privacy Policy

104 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/resources/privacy-policy ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://na4-onlineapp.dnbi.com/createApp/JCL+Energy+Partners%2C+LLC?token=A%2…; /media/literature/JCL-Standard-Terms-Conditions-Feb2026.pdf

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Mobile Keyboard & Autofill

Action

2/3 eligible field(s) missing autocomplete or inputmode

REVIEW

2/3 eligible field(s) missing autocomplete or inputmode

2 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel, email.

Got: <input type="tel" name="phone">, <input type="email" name="email">

Mobile-Readable Font Sizes

Action

82% of visible text renders at >= 12 CSS px (29 below threshold)

REVIEW

82% of visible text renders at >= 12 CSS px (29 below threshold)

29 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Data Centers"); <span> 11.0px ("Delivered"); <div> 11.0px ("15/20/25 MVA · 34.5 kV – 13.8 kV"); <span> 11.0px ("Utility interconnect"); <span> 11.0px ("Renewables").

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

h2 The responsibility is

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We're simplifying what comes next.

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built for the nation's largest energy pr…

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Process-driven,

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 solution-oriented.

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 REDUCING COMPLEXITY FROM START TO FINISH

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Project highlights

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Fewer vendors to manage

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Built for your challenges

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Continuous support

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Less downtime

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Lower cost of ownership

1.24:1

#000000

#1F1C1A

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Solving	16.95:1	3.0:1	#FFFFFF	#1F1C1A	Pass
h1 Transformer	16.95:1	3.0:1	#FFFFFF	#1F1C1A	Pass
h2 The responsibility i…	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h2 We're simplifying wh…	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h2 Built for the nation…	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h2 ONE PARTNER FOR THE …	16.95:1	3.0:1	#FFFFFF	#1F1C1A	Pass
h2 Process-driven,	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h2 solution-oriented.	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h2 REDUCING COMPLEXITY …	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h2 Project highlights	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h2 Start with a convers…	16.95:1	3.0:1	#FFFFFF	#1F1C1A	Pass
h3 Discovery	16.95:1	3.0:1	#FFFFFF	#1F1C1A	Pass
h3 Engineer the solutio…	16.95:1	3.0:1	#FFFFFF	#1F1C1A	Pass
h3 Delivery & commissio…	16.95:1	3.0:1	#FFFFFF	#1F1C1A	Pass
h3 Support for life	16.95:1	3.0:1	#FFFFFF	#1F1C1A	Pass
h3 Fewer vendors to man…	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h3 Built for your chall…	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h3 Continuous support	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h3 Less downtime	1.24:1	3.0:1	#000000	#1F1C1A	Fail
h3 Lower cost of owners…	1.24:1	3.0:1	#000000	#1F1C1A	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

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

25 headings

PASS

25 headings

Single H1 present

H1 SolvingTransformerProblems.
H2 The responsibility is now yours.
H2 We're simplifying what comes next.
H2 Built for the nation's largest energy projects.
H2 ONE PARTNER FOR THE ENTIRE LIFECYCLE.
H2 Process-driven, solution-oriented.
H3 Discovery
H3 Engineer the solution
H3 Delivery & commissioning
H3 Support for life
H2 REDUCING COMPLEXITY FROM START TO FINISH
H3 Fewer vendors to manage
H3 Built for your challenges
H3 Continuous support
H3 Less downtime
H3 Lower cost of ownership
H3 Less risk on the critical path
H2 Project highlights
H3 Hyperscale data center
H3 Community solar
H3 Commercial facility
H3 Utility-scale solar
H3 Electric cooperative
H3 Industrial facility
H2 Start with a conversation.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 2 all-caps heading(s)

A+

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

7 decorative image(s) correctly marked

8 image(s) with good alt text

15 images 8 good alt text 7 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
firstName	text	First name	aria-label
lastName	text	Last name	aria-label
company	text	Company	aria-label
phone	tel	Phone	aria-label
email	email	Work email	aria-label
projectType	text	Project type — data center, CI facility, utility	aria-label

A+

Form Input Types

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

6 form control(s) checked, no input-semantic issues

PASS

6 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 24 passed

PASS

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
GET A QUOTE `header.jcl-bar > div.jcl-bar-in > div > a.hdr-quote`
BRING US YOUR PROJECT `div.r-hero-pad > div.hero-copy > div > a.home-cta`

These are opportunities to improve the legibility of your content.

○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

●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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●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

○`[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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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.

○Identical links have the same purpose.

○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.