Accessibility

D

Tabindex Anti-Patterns

Action

33 positive, 3 -1-on-focusable

FIX

33 positive, 3 -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 <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.

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

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

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

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

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

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

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.

F

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

B

Heading Hierarchy

15 headings

REVIEW

15 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 RTX Businesses
H2 A new day dawns for the MALD® decoy
H2 Who we are
H2 The RTX effect
H3 RTX accelerates the design and manufacture of complex systems by combining advanced digital tools, scalable design approaches and manufacturing-ready thinking from the start.
H2 Customer outcomes
H3 What will unlock greater capability for the F-35?
H2 What we do
H3 RTX pushes the limits of science and technology to design, build and support innovations that keep people flying safely and protect nations.
H2 Our businesses
H3 Collins Aerospace
H3 Pratt & Whitney
H3 Raytheon
H3 Careers
H4 It’s time to make a difference

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B

Alt Text Quality

2 of 18 images have issues

REVIEW

2 of 18 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

8 decorative image(s) correctly marked

8 image(s) with good alt text

18 images 8 good alt text 8 decorative 2 missing

Issue	Count
missing	2 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

2 issue(s) across 70 links and 7 buttons

REVIEW

2 issue(s) across 70 links and 7 buttons

2 link(s) with generic text

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

Got: /news/2026/07/15/a-new-day-dawns-for-mald ("Learn more"); /who-we-are/we-are-rtx/rtx-big-questions/what-will-unlock-greater-capability-… ("Learn more")

6 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://careers.rtx.com/global/en/lifeatrtx; /external-redirects/rtx-careers; https://www.rtx.com/who-we-are/ethics-and-compliance#speakup; https://www.rtx.com/who-we-are/ethics-and-compliance#raytheon-technologies-co…

62 link(s) with descriptive text

70 links

0 empty

2 generic text

6 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
/news/2026/07/15/a-new-day-dawns-for-mal…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: A New Day Dawns For Mald
/news/news-center/2026/07/21/rtxs-raythe…	Latest News …	img no alt	Add alt attribute to the image
/who-we-are/we-are-rtx/rtx-big-questions…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: What Will Unlock Greater Capability For The F 35
https://www.rtx.com/collinsaerospace/	Collins Aerospace	img no alt	Add alt attribute to the image
https://www.rtx.com/en/prattwhitney	Pratt & Whitney	img no alt	Add alt attribute to the image
https://www.rtx.com/raytheon	Raytheon	img no alt	Add alt attribute to the image
https://careers.rtx.com/global/en/lifeat…	Learn about our culture	new tab	Add '(opens in new tab)' to text
/external-redirects/rtx-careers	Find your next career	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

69 links and buttons have descriptive text

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

/news/2026/07/15/a-new-day-dawns-for-mald ("Learn more"); /who-we-are/we-are-rtx/rtx-big-questions/what-will-unlock-greater-capability-… ("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://careers.rtx.com/global/en; https://investors.rtx.com/#Investors; https://careers.rtx.com/global/en/lifeatrtx; /external-redirects/rtx-careers; 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

C

Mobile-Readable Font Sizes

Action

83% of visible text renders at >= 12 CSS px (13 below threshold)

REVIEW

83% of visible text renders at >= 12 CSS px (13 below threshold)

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

REVIEW

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

10 pass 10 fail WCAG AA

h2 A new day dawns for the MALD® decoy

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Who we are

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The RTX effect

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Customer outcomes

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What we do

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our businesses

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

24px · bottom of viewport

h3 RTX accelerates the design and manufactu…

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

19px · bottom of viewport

h3 What will unlock greater capability for …

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

19px · bottom of viewport

h3 RTX pushes the limits of science and tec…

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Careers

1.19:1

#000000

on

#191919

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 A new day dawns for …	1.19:1	3.0:1	#000000	#191919	Fail
h2 Who we are	1.19:1	3.0:1	#000000	#191919	Fail
h2 The RTX effect	1.19:1	3.0:1	#000000	#191919	Fail
h2 Customer outcomes	1.19:1	3.0:1	#000000	#191919	Fail
h2 What we do	1.19:1	3.0:1	#000000	#191919	Fail
h2 Our businesses	1.19:1	3.0:1	#000000	#191919	Fail
h3 RTX Businesses	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 RTX accelerates the …	1.19:1	3.0:1	#000000	#191919	Fail
h3 What will unlock gre…	1.19:1	3.0:1	#000000	#191919	Fail
h3 RTX pushes the limit…	1.19:1	3.0:1	#000000	#191919	Fail
h3 Careers	1.19:1	3.0:1	#000000	#191919	Fail
title Home \| RTX	8.63:1	4.5:1	#000000	#A6A6A6	Pass
button Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a RTX	8.63:1	4.5:1	#000000	#A6A6A6	Pass
a Collins Aerospace	8.63:1	4.5:1	#000000	#A6A6A6	Pass
a Pratt & Whitney	8.73:1	4.5:1	#000000	#A7A7A7	Pass
a Raytheon	8.73:1	4.5:1	#000000	#A7A7A7	Pass
span RTX	8.73:1	4.5:1	#000000	#A7A7A7	Pass
div Internet Explorer is…	8.74:1	4.5:1	#000000	#A7A7A8	Pass
span Menu	15.31:1	4.5:1	#000000	#DCDCDC	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 — 3 failing, 24 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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.esds-vml-carousel__slide > figure > picture > img `div.esds-vml-carousel__slide > figure > picture > img`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Contacts Corporate and Business Headquarters RTX on LinkedIn RTX on X RTX on Fa… `nav.footer__navigation > div.footer-grid > div.footer__navigation-list > ul`
Corporate Governance Responsibility Contract Vehicles `nav.footer__navigation > div.footer-grid > div.footer__navigation-list > ul`
News Media Resources `nav.footer__navigation > div.footer-grid > div.footer__navigation-list > ul`
RTX Collins Aerospace Pratt & Whitney Raytheon `nav.footer__navigation > div.footer-grid > div.footer__navigation-list > ul`
Speak Up Code of Conduct `nav.footer__navigation > div.footer-grid > div.footer__navigation-list > ul`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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 212.79 `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`
rtx `div > div.footer-row > div.footer-nav__logo > a`
Accept recommended settings `div.component-content > div.gdpr > div.gdpr__buttons > a.gdpr__btn`
Accept necessary cookies only `div.component-content > div.gdpr > div.gdpr__buttons > a.gdpr__btn`
Manage settings `div.gdpr > div.gdpr__buttons > div.gdpr__btn > a.initializeModal`
RTX.com Privacy Policy `div.component-content > div.gdpr > div.gdpr__link > a`

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

●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

●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

○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

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

○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

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 174 chars - H3: 140 chars

Got: 2 >120-char heading(s)

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.

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+

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)

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+

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

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.