Accessibility

F

Heading Hierarchy

Action

23 headings, 5 skip(s)

FIX

23 headings, 5 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H6 (missing H3)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H4 GE.com has been updated to serve our three go-forward companies.
H3 About us
H3 Investors
H3 News
H3 FAQs
H3 Contact
H3 About us
H3 Investors
H3 News
H3 FAQs
H3 Contact
H1 GE - Once, Now, Forever
H3 We were meant to fly skipped
H6 Learn more skipped
H3 The Energy To Change The World
H6 learn more skipped
H3 Building a healthier future we can thrive in
H6 LEARn MORE skipped
H2 Now three standalone and publicly traded companies
H6 Visit GE Aerospace skipped
H6 Visit GE Vernova
H6 Visit GE HealthCare
H6 (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

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

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

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

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

D

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: #ffffff

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 2 <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.

C

Alt Text Quality

Action

8 of 19 images have issues

REVIEW

8 of 19 images have issues

8 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 decorative image(s) correctly marked

10 image(s) with good alt text

19 images 10 good alt text 1 decorative 8 missing

Issue	Count
missing	8 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B

Link & Button Quality

3 issue(s) across 52 links and 13 buttons

REVIEW

3 issue(s) across 52 links and 13 buttons

3 link(s) with generic text

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

Got: https://www.geaerospace.com/ ("Learn more"); https://www.gevernova.com/ ("learn more"); https://www.gehealthcare.com/ ("LEARn MORE")

18 link(s) open in new tab without warning

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

Got: https://accessibe.com/blog/knowledgebase/screen-reader-guide; https://www.geaerospace.com/; https://www.gevernova.com/; https://www.gehealthcare.com/; https://www.geaerospace.com/; https://www.geaerospace.com/; https://www.gevernova.com/; https://www.gevernova.com/; https://www.gehealthcare.com/; https://www.gehealthcare.com/ (+8 more)

31 link(s) with descriptive text

52 links

0 empty

3 generic text

18 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://accessibe.com/blog/knowledgebase…	Accessibility Screen-Reader Gu…	new tab	Add '(opens in new tab)' to text
https://www.geaerospace.com/	GE Aerospace	new tab	Add '(opens in new tab)' to text
https://www.gevernova.com/	GE Vernova	new tab	Add '(opens in new tab)' to text
https://www.gehealthcare.com/	GE HealthCare	new tab	Add '(opens in new tab)' to text
https://www.geaerospace.com/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Home page
https://www.gevernova.com/	learn more	generic text	Replace with descriptive text
Before: learn more Suggested: Home page
https://www.gehealthcare.com/	LEARn MORE	generic text	Replace with descriptive text
Before: LEARn MORE Suggested: Home page
https://www.geaerospace.com/	The future is our starting poi…	new tab	Add '(opens in new tab)' to text
https://www.geaerospace.com/	Visit GE Aerospace	new tab	Add '(opens in new tab)' to text
https://www.gevernova.com/	The energy to change the world	new tab	Add '(opens in new tab)' to text
https://www.gevernova.com/	Visit GE Vernova	new tab	Add '(opens in new tab)' to text
https://www.gehealthcare.com/	Every patient has a story to t…	new tab	Add '(opens in new tab)' to text
https://www.gehealthcare.com/	Visit GE HealthCare	new tab	Add '(opens in new tab)' to text
https://www.geaerospace.com/	GE Aerospace …	new tab	Add '(opens in new tab)' to text
https://www.gehealthcare.com/	GE HealthCare …	new tab	Add '(opens in new tab)' to text
https://www.gevernova.com/	GE Vernova …	new tab	Add '(opens in new tab)' to text
https://www.gevernova.com/sustainability	ESG Reports	new tab	Add '(opens in new tab)' to text
https://www.geaerospace.com/company/glob…	Global Impact …	new tab	Add '(opens in new tab)' to text
https://jobs.gecareers.com/aviation/glob…	Accessibility …	new tab	Add '(opens in new tab)' to text
	Cookies …	new tab	Add '(opens in new tab)' to text
//www.ge.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text

44 links and buttons have descriptive text

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

https://www.geaerospace.com/ ("Learn more"); https://www.gevernova.com/ ("learn more"); https://www.gehealthcare.com/ ("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://accessibe.com/blog/knowledgebase/screen-reader-guide; https://www.geaerospace.com/; https://www.gevernova.com/; https://www.gehealthcare.com/; https://www.geaerospace.com/; https://www.geaerospace.com/; https://www.gevernova.com/; https://www.gevernova.com/; https://www.gehealthcare.com/; https://www.gehealthcare.com/ (+8 more)

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

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Error | General Electric ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Favicon & Branding

8 icon(s) detected

REVIEW

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

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

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

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, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA

h3 We were meant to fly

1.11:1

#FFFFFF

on

#F0F3F7

needs 3.0:1 (large text)

19px · bottom of viewport

title GE Companies: Next Generation and Future…

1.16:1

#000000

on

#0D1623

needs 4.5:1 (normal text)

16px · top of page (header area)

span Press Alt+1 for screen-reader mode, Alt+…

1.16:1

#000000

on

#0D1623

needs 4.5:1 (normal text)

16px · top of page (header area)

a Accessibility Screen-Reader Guide, Feedb…

4.09:1

#000000

on

#686E78

needs 4.5:1 (normal text)

16px · top of page (header area) · 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)

Element	Ratio	Required	FG	BG	Result
h1 GE - Once, Now, Fore…	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h2 Now three standalone…	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 About us	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 Investors	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 News	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 FAQs	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 Contact	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 About us	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 Investors	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 News	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 FAQs	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 Contact	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 We were meant to fly	1.11:1	3.0:1	#FFFFFF	#F0F3F7	Fail
h3 The Energy To Change…	18.87:1	3.0:1	#000000	#F0F3F7	Pass
h3 Building a healthier…	18.87:1	3.0:1	#000000	#F0F3F7	Pass
title GE Companies: Next G…	1.16:1	4.5:1	#000000	#0D1623	Fail
span Press Alt+1 for scre…	1.16:1	4.5:1	#000000	#0D1623	Fail
a Accessibility Screen…	4.09:1	4.5:1	#000000	#686E78	Fail
a Skip to main content	18.87:1	4.5:1	#000000	#F0F3F7	Pass
h4 GE.com has been upda…	18.87:1	3.0:1	#000000	#F0F3F7	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.

B

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 26 passed

REVIEW

87

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

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
× GE.com has been updated to serve our three go-forward companies. Please visi… `body.node-43651 > div.dialog-off-canvas-main-canvas > div.page`
General Electric `body.node-43651 > div.dialog-off-canvas-main-canvas > div.page > header.header`
GE Aerospace (link is external) GE HealthCare (link is external) GE Vernova … `body.node-43651 > div.dialog-off-canvas-main-canvas > footer.ge-footer`
© 2026 General Electric Company `body.node-43651 > div.dialog-off-canvas-main-canvas > footer.ge-footer > div.ge-copyrights`

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.

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
We use cookies to personalize and enhance your experience on our site. Visit ou… `body.node-43651 > div#_evidon_banner > div#_evidon-message`
Privacy Policy `body.node-43651 > div#_evidon_banner > div#_evidon-message > a`
Cookie Consent Tool `body.node-43651 > div#_evidon_banner > div#_evidon-message > a`
OPTIONS `body.node-43651 > div#_evidon_banner > button#_evidon-option-button`

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We use cookies to personalize and enhance your experience on our site. Visit ou… `body.node-43651 > div#_evidon_banner`

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
VISIT GE AEROSPACE `div.card-container > div.card-stack > div.card-cta > h6.call-to-action`

These are opportunities to improve keyboard navigation in your application.

○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

●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

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Elements with visible text labels have matching accessible names.

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

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

○Identical links have the same purpose.

○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

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

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+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.