Browse & Analyze

Browse recent website audits and performance trends

Explore technology stacks detected across the web

Side-by-side technology comparisons and market share

Curated technology stacks and the sites that use them

Editorial deep-dives on the state of web performance

Browse and download favicons from analyzed websites

Learn

Common questions about BeaverCheck scores and checks

How we calculate scores across 100+ checks

The story behind BeaverCheck and the team

Practical guides to fix common web performance issues

Migration Guides

Step-by-step guides for moving between web technologies

Definitions for performance, SEO, and web platform terms

Contrast Checker

Check WCAG color contrast ratios between any two colors

Inspect HTTP response headers for any URL

Analyze SSL/TLS certificate details and chain

Look up DNS records for any domain

Redirect Checker

Trace the full redirect chain for any URL

Real-user INP and Core Web Vitals from Google's Chrome UX Report.

RESTful API for programmatic website audits

Embed an auto-updating health score badge on your site

https://rtx.com

Accessibility

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

SCORE

76

GRADE

C

FIX

6

REVIEW

3

PASS

15

INFO

0

Checks

24

15 PASS 3 REVIEW 6 FIX

D

Tabindex Anti-Patterns

Action

55 positive, 0 -1-on-focusable

FIX

55 positive, 0 -1-on-focusable

Positive tabindex on <button>: tabindex=2

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=3

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=3

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=3

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=3

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=3

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=1

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <button>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <button>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <button>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <button>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <button>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <a>: tabindex=4

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <input id="searchBar">: tabindex=6

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <button>: tabindex=5

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

Positive tabindex on <button>: tabindex=6

Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

F

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 2 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

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

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

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

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

C

Mobile-Readable Font Sizes

Action

88% of visible text renders at >= 12 CSS px (6 below threshold)

REVIEW

88% of visible text renders at >= 12 CSS px (6 below threshold)

6 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: <a> 10.0px ("RTX"); <a> 10.0px ("Collins Aerospace"); <a> 10.0px ("Pratt & Whitney"); <a> 10.0px ("Raytheon"); <span> 10.0px ("RTX").

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

h1 Delivering for our Customers

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Vision, breadth and scale come together …

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Progress is developed. It is produced. I…

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Tech and talent to transform the world

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Delivering for our C…	1.19:1	3.0:1	#000000	#191919	Fail
h2 Vision, breadth and …	1.19:1	3.0:1	#000000	#191919	Fail
h2 Progress is develope…	1.19:1	3.0:1	#000000	#191919	Fail
h2 Tech and talent to t…	1.19:1	3.0:1	#000000	#191919	Fail
h3 RTX Businesses	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Home \| RTX	12.04:1	4.5:1	#000000	#C4C4C4	Pass
button Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a RTX	15.24:1	4.5:1	#000000	#D2DDE7	Pass
a Collins Aerospace	16.52:1	4.5:1	#000000	#DEE5EC	Pass
a Pratt & Whitney	17.62:1	4.5:1	#000000	#E6ECF0	Pass
a Raytheon	18.25:1	4.5:1	#000000	#EBF0F0	Pass
span RTX	13.40:1	4.5:1	#000000	#CCCFD0	Pass
div Internet Explorer is…	12.58:1	4.5:1	#000000	#C8C8CB	Pass
span Menu	16.81:1	4.5:1	#000000	#E6E6E5	Pass
a Who We Are	20.11:1	4.5:1	#000000	#FAFAF9	Pass
span Who We Are	20.11:1	4.5:1	#000000	#FAFAF9	Pass
a Overview	20.11:1	4.5:1	#000000	#FAFAF9	Pass
a Our Leadership	20.11:1	4.5:1	#000000	#FAFAF9	Pass
a Our Values	20.11:1	4.5:1	#000000	#FAFAF9	Pass
a Our Global Presence	21.00:1	4.5: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.

A+

Heading Hierarchy

11 headings

PASS

11 headings

Single H1 present

H3 RTX Businesses
H1 Delivering for our Customers
H2 Vision, breadth and scale come together with a unique perspective
H3 Scaling up to deliver with speed
H3 Delivering for America
H3 RTX to release second quarter earnings results on July 23, 2026
H2 Progress is developed. It is produced. It defines the future, and it defines us.
H2 Tech and talent to transform the world
H3 Fast track: Engineering with speed
H3 RTX recognized as global leader in patents and innovation
H3 A commitment to lifesaving performance

A+

Heading Text Quality

All 11 heading(s) have substantive, well-formed text

PASS

All 11 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 13 images OK

PASS

All 13 images OK

1 decorative image(s) correctly marked

12 image(s) with good alt text

13 images 12 good alt text 1 decorative

All images have appropriate alt text.

A

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="checkbox" id="esds-bu-bar__toggle">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#searchBar	text	Input search request	aria-label
#esds-bu-bar__toggle	checkbox	(none)	none

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

<input type="checkbox" id="esds-bu-bar__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

Link & Button Quality

82 links, 8 buttons — all OK

PASS

82 links, 8 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://careers.rtx.com/global/en; https://investors.rtx.com/#Investors; https://investors.rtx.com/; https://www.rtx.com/who-we-are/ethics-and-compliance#speakup; https://www.rtx.com/who-we-are/ethics-and-compliance#raytheon-technologies-co…

77 link(s) with descriptive text

82 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://careers.rtx.com/global/en	Careers	new tab	Add '(opens in new tab)' to text
https://investors.rtx.com/#Investors	Investors	new tab	Add '(opens in new tab)' to text
/who-we-are/global-presence/america	Delivering for America	img no alt	Add alt attribute to the image
https://investors.rtx.com/	Investors	new tab	Add '(opens in new tab)' to text
https://www.rtx.com/who-we-are/ethics-an…	Speak Up	new tab	Add '(opens in new tab)' to text
https://www.rtx.com/who-we-are/ethics-an…	Code of Conduct	new tab	Add '(opens in new tab)' to text

85 links and buttons have descriptive text

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

https://careers.rtx.com/global/en; https://investors.rtx.com/#Investors; https://investors.rtx.com/; https://www.rtx.com/who-we-are/ethics-and-compliance#speakup; https://www.rtx.com/who-we-are/ethics-and-compliance#raytheon-technologies-co…

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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "searchBar" should use type="search" (currently type="text")

Field name "searchBar" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

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

Got: en

A

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

<iframe> missing title attribute (src="")

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title (404 - Page Not Found) | RTX ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 26 passed

PASS

96

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.

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
Skip to main content `div#wrapper > header > div#header > button.esds-mega-nav__skip-link`
RTX `div > ul > li > a.active`
Collins Aerospace `div > ul > li > a`
Pratt & Whitney `div > ul > li > a`
Raytheon `div > ul > li > a`
RTX 195.93 `div > div.simple-stock-quote > div.initialized > a.esds-bu-bar__quote-link`
RTX logo `div > div.row > div.esds-mega-nav__logo > a`
Menu `section.wrapper > div > div.row > a.esds-mega-nav__hamburger`
Input search request `div.row > div.esds-mega-nav__search-bar > form.esds-mega-nav__search-bar-form > input#searchBar`
Submit search request `div.row > div.esds-mega-nav__search-bar > form.esds-mega-nav__search-bar-form > button.esds-mega-nav__search-bar-form-submit`

These are opportunities to improve keyboard navigation in your application.

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
We are RTX `div > div.row > article.equal-grid__item > a`

○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

●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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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 buttons have discernible text.

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

○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