Accessibility

D

Landmark Structure

Action

6 landmarks

FIX

6 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

3 <nav> landmark(s) found

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F

Heading Hierarchy

Action

88 headings, 18 skip(s)

FIX

88 headings, 18 skip(s)

Multiple H1 headings (7 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H6 (missing H2)

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

Heading level skipped: H1 → H6 (missing H2)

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

Heading level skipped: H1 → H6 (missing H2)

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

Heading level skipped: H1 → H6 (missing H2)

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

Heading level skipped: H1 → H6 (missing H2)

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

Heading level skipped: H1 → H6 (missing H2)

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

Heading level skipped: H1 → H6 (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: 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: H3 → H6 (missing H4)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

H1 Commercial
H6 Connecting people and economies with the most complete and competitive family of airplanes skipped
H5 Commercial Market Outlook
H5 Boeing Business Jets
H1 Defense duplicate H1
H6 Game-changing family of systems that empower warfighters, protect nations and advance global security skipped
H5 Phantom Works
H5 Government Services
H1 Space duplicate H1
H6 Exploring what’s possible in the future of space and satellite technology skipped
H5 United Launch Alliance
H1 Services duplicate H1
H6 Committed to ensuring optimal aircraft availability and mission readiness of our customers’ fleets skipped
H5 Boeing Global Services
H5 Services Market Outlook
H1 Safety duplicate H1
H6 Our work begins and ends with safety. It’s ingrained in everything we do skipped
H5 Safety Experience at Boeing
H1 Innovation duplicate H1
H6 Driving ingenuity and passion that will transform aerospace and defense as we know it skipped
H5 Cascade Climate Impact Model
H1 Company duplicate H1
H6 A long tradition of aerospace leadership and innovation skipped
H5 Tours and Merchandise
H3 Search
H3 Commercial
H6 Connecting people and economies with the most complete and competitive family of airplanes skipped
H5 Commercial Market Outlook
H5 Boeing Business Jets
H3 Defense
H6 Game-changing family of systems that empower warfighters, protect nations and advance global security skipped
H5 Phantom Works
H5 Government Services
H3 Space
H6 Exploring what’s possible in the future of space and satellite technology skipped
H5 United Launch Alliance
H3 Services
H6 Committed to ensuring optimal aircraft availability and mission readiness of our customers’ fleets skipped
H5 Boeing Global Services
H5 Services Market Outlook
H3 Safety
H6 Our work begins and ends with safety. It’s ingrained in everything we do skipped
H5 Safety Experience at Boeing
H3 Innovation
H6 Driving ingenuity and passion that will transform aerospace and defense as we know it skipped
H5 Cascade Climate Impact Model
H3 Company
H6 A long tradition of aerospace leadership and innovation skipped
H5 Tours and Merchandise
H2 Connect, protect and explore our world and beyond
H3 Recent news
H4 Boeing Announces First Quarter Deliveries
H6 Boeing backs U.S. Army with digital and logistics sustainment capabilities skipped
H6 US Army orders 6 more Boeing Chinook helicopters
H6 Boeing, Millennium scale production for growing space demand
H6 Culture change continues to gain momentum
H6 Boeing backs U.S. Army with digital and logistics sustainment capabilities
H6 US Army orders 6 more Boeing Chinook helicopters
H6 Boeing, Millennium scale production for growing space demand
H6 Culture change continues to gain momentum
H3 Featured products
H4 787 Dreamliner
H4 MQ-28 Ghost Bat
H4 777X
H4 KC-46 Pegasus
H4 737 MAX
H4 X-37B
H4 Strengthening safety and quality
H2 Innovating aerospace since 1916
H5 A leading global aerospace company and top U.S. exporter, Boeing develops, manufactures and services commercial airplanes, defense products and space systems for customers in more than 150 countries. skipped
H4 Commercial
H4 Defense
H4 Space
H4 Boeing Global Services
H2 Supporting responsible growth
H5 We're engineering the future of aerospace by combining smart, sustainable innovation with safety and quality at every step. Investing in our people and communities fosters environments where ideas thr skipped
H4 Safety
H4 Innovation
H4 Global Presence
H4 Explore more
H5 People and Culture
H5 Sustainability
H5 Community Engagement
H5 Aerospace Safety Timeline
H5 Our History
H5 Tours and Merchandise
H4 Let’s explore what’s next in aerospace
H6 Stock Price skipped

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

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

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

D

Alt Text Quality

Action

7 of 69 images have issues

FIX

7 of 69 images have issues

7 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

4 image(s) with alt text over 125 characters

49 decorative image(s) correctly marked

9 image(s) with good alt text

69 images 9 good alt text 49 decorative 7 missing

Issue	Count
missing	7 image(s)
too long	4 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

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

Web Manifest

Action

Not found

FIX

Not found

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

3 navigation landmark(s) detected

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

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

C

Form Accessibility

Action

3 of 16 controls have issues

REVIEW

3 of 16 controls have issues

3 control(s) without accessible label

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

Got: <select id="vjs_select_731">; <select id="vjs_select_750">; <select id="vjs_select_765">

13 control(s) properly labeled

16 controls

13 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
#commercial-0	checkbox	Back	for/id
#defense-1	checkbox	Back	for/id
#space-2	checkbox	Back	for/id
#services-3	checkbox	Back	for/id
#safety-4	checkbox	Back	for/id
#innovation-5	checkbox	Back	for/id
#company-6	checkbox	Back	for/id
#vjs_select_681	select	Color	for/id
#vjs_select_686	select	Opacity	for/id
#vjs_select_696	select	Color	for/id
#vjs_select_701	select	Opacity	for/id
#vjs_select_711	select	Color	for/id
#vjs_select_716	select	Opacity	for/id
#vjs_select_731	select	(none)	none
#vjs_select_750	select	(none)	none
#vjs_select_765	select	(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

C

Link & Button Quality

Action

1 issue(s) across 220 links and 25 buttons

REVIEW

1 issue(s) across 220 links and 25 buttons

28 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/commercial/market/commercial-market-outlook"]; a[href="https://businessjets.boeing.com/"]; a[href="/defense/phantom-works"]; a[href="/services/government"]; a[href="https://www.ulalaunch.com/"]; a[href="https://services.boeing.com/"]; a[href="/commercial/market/services-market-outlook"]; a[href="/safety/safetyexperience"]; a[href="https://cascade.boeing.com/"]; a[href="/company/tours-and-merchandise"] (+18 more)

23 link(s) open in new tab without warning

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

Got: http://investors.boeing.com/?_gl=1*169wy4g*_ga*NTk1NTE0ODYzLjE2OTc2NTk2NDA.*_…; http://www.boeingsuppliers.com/; http://boeing.mediaroom.com/?_gl=1*1y16wii*_ga*NTk1NTE0ODYzLjE2OTc2NTk2NDA.*_…; http://investors.boeing.com/?_gl=1*169wy4g*_ga*NTk1NTE0ODYzLjE2OTc2NTk2NDA.*_…; http://www.boeingsuppliers.com/; http://boeing.mediaroom.com/?_gl=1*1y16wii*_ga*NTk1NTE0ODYzLjE2OTc2NTk2NDA.*_…; https://boeing.mediaroom.com/2026-04-14-Boeing-Announces-First-Quarter-Delive…; https://services.boeing.com/; https://jobs.boeing.com?utm_source=boeing.com&utm_medium=careerslink&utm_camp…; https://investmentrecovery.boeing.com/Default.aspx (+13 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.jumbotron-pause-button (#1414 on page)

169 link(s) with descriptive text

220 links

0 empty

0 generic text

23 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
http://investors.boeing.com/?_gl=1*169wy…	Investors opens i…	new tab	Add '(opens in new tab)' to text
http://www.boeingsuppliers.com/	Suppliers opens i…	new tab	Add '(opens in new tab)' to text
http://boeing.mediaroom.com/?_gl=1*1y16w…	News and Stories …	new tab	Add '(opens in new tab)' to text
/commercial/market/commercial-market-out…	Commercial Market Outlook	img no alt	Add alt attribute to the image
https://businessjets.boeing.com/	Boeing Business Jets …	new tab	Add '(opens in new tab)' to text
/defense/phantom-works	Phantom Works	img no alt	Add alt attribute to the image
/services/government	Government Services	img no alt	Add alt attribute to the image
https://www.ulalaunch.com/	United Launch Alliance …	new tab	Add '(opens in new tab)' to text
https://services.boeing.com/	Boeing Global Services …	new tab	Add '(opens in new tab)' to text
/commercial/market/services-market-outlo…	Services Market Outlook	img no alt	Add alt attribute to the image
/safety/safetyexperience	Safety Experience at Boeing	img no alt	Add alt attribute to the image
https://cascade.boeing.com/	Cascade Climate Impact Model …	new tab	Add '(opens in new tab)' to text
/company/tours-and-merchandise	Tours and Merchandise	img no alt	Add alt attribute to the image
/commercial/market/commercial-market-out…	Commercial Market Outlook	img no alt	Add alt attribute to the image
https://businessjets.boeing.com/	Boeing Business Jets …	new tab	Add '(opens in new tab)' to text
/defense/phantom-works	Phantom Works	img no alt	Add alt attribute to the image
/services/government	Government Services	img no alt	Add alt attribute to the image
https://www.ulalaunch.com/	United Launch Alliance …	new tab	Add '(opens in new tab)' to text
https://services.boeing.com/	Boeing Global Services …	new tab	Add '(opens in new tab)' to text
/commercial/market/services-market-outlo…	Services Market Outlook	img no alt	Add alt attribute to the image
/safety/safetyexperience	Safety Experience at Boeing	img no alt	Add alt attribute to the image
https://cascade.boeing.com/	Cascade Climate Impact Model …	new tab	Add '(opens in new tab)' to text
/company/tours-and-merchandise	Tours and Merchandise	img no alt	Add alt attribute to the image
http://investors.boeing.com/?_gl=1*169wy…	Investors opens i…	new tab	Add '(opens in new tab)' to text
http://www.boeingsuppliers.com/	Suppliers opens i…	new tab	Add '(opens in new tab)' to text
http://boeing.mediaroom.com/?_gl=1*1y16w…	News and Stories …	new tab	Add '(opens in new tab)' to text
https://boeing.mediaroom.com/2026-04-14-…	Learn More opens…	new tab	Add '(opens in new tab)' to text
/features/2026/04/boeing-backs-us-army-w…	Boeing backs U.S. Army with di…	img no alt	Add alt attribute to the image
/features/2026/04/boeing-backs-us-army-w…	Boeing backs U.S. Army with di…	img no alt	Add alt attribute to the image
https://services.boeing.com/	Global Services Website …	new tab	Add '(opens in new tab)' to text
/company/people-and-culture	People and Culture	img no alt	Add alt attribute to the image
/innovation/sustainability	Sustainability	img no alt	Add alt attribute to the image
/company/community-engagement	Community Engagement	img no alt	Add alt attribute to the image
/safety/safetyexperience	Aerospace Safety Timeline	img no alt	Add alt attribute to the image
/history	Our History	img no alt	Add alt attribute to the image
/company/tours-and-merchandise	Tours and Merchandise	img no alt	Add alt attribute to the image
https://jobs.boeing.com?utm_source=boein…	Find jobs …	new tab	Add '(opens in new tab)' to text
https://investmentrecovery.boeing.com/De…	Investment Recovery …	new tab	Add '(opens in new tab)' to text
https://investmentrecovery.boeing.com/De…	Investment Recovery …	new tab	Add '(opens in new tab)' to text
http://investors.boeing.com/?_gl=1*1u3oa…	Investors opens i…	new tab	Add '(opens in new tab)' to text
http://www.boeingsuppliers.com/	Suppliers opens i…	new tab	Add '(opens in new tab)' to text
https://services.boeing.com	Boeing Global Services …	new tab	Add '(opens in new tab)' to text
http://investors.boeing.com/?_gl=1*1u3oa…	Investors opens i…	new tab	Add '(opens in new tab)' to text
http://www.boeingsuppliers.com/	Suppliers opens i…	new tab	Add '(opens in new tab)' to text
https://services.boeing.com	Boeing Global Services …	new tab	Add '(opens in new tab)' to text
https://boeing.mediaroom.com/	Newsroom opens in…	new tab	Add '(opens in new tab)' to text
https://media-portal.boeing.com/	Media Asset Portal …	new tab	Add '(opens in new tab)' to text
https://boeing.mediaroom.com/social-medi…	Social Media Center …	new tab	Add '(opens in new tab)' to text
https://boeing.mediaroom.com/	Newsroom opens in…	new tab	Add '(opens in new tab)' to text
https://media-portal.boeing.com/	Media Asset Portal …	new tab	Add '(opens in new tab)' to text
https://boeing.mediaroom.com/social-medi…	Social Media Center …	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

193 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/commercial/market/commercial-market-outlook"]; a[href="https://businessjets.boeing.com/"]; a[href="/defense/phantom-works"]; a[href="/services/government"]; a[href="https://www.ulalaunch.com/"]; a[href="https://services.boeing.com/"]; a[href="/commercial/market/services-market-outlook"]; a[href="/safety/safetyexperience"]; a[href="https://cascade.boeing.com/"]; a[href="/company/tours-and-merchandise"] (+18 more)

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

http://investors.boeing.com/?_gl=1*169wy4g*_ga*NTk1NTE0ODYzLjE2OTc2NTk2NDA.*_…; http://www.boeingsuppliers.com/; http://boeing.mediaroom.com/?_gl=1*1y16wii*_ga*NTk1NTE0ODYzLjE2OTc2NTk2NDA.*_…; http://investors.boeing.com/?_gl=1*169wy4g*_ga*NTk1NTE0ODYzLjE2OTc2NTk2NDA.*_…; http://www.boeingsuppliers.com/; http://boeing.mediaroom.com/?_gl=1*1y16wii*_ga*NTk1NTE0ODYzLjE2OTc2NTk2NDA.*_…; https://boeing.mediaroom.com/2026-04-14-Boeing-Announces-First-Quarter-Delive…; https://services.boeing.com/; https://jobs.boeing.com?utm_source=boeing.com&utm_medium=careerslink&utm_camp…; https://investmentrecovery.boeing.com/Default.aspx (+13 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

Icon-only buttons need an aria-label so screen readers can announce them.

button.jumbotron-pause-button (#1414 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

h1 Commercial

1.29:1

#000000

on

#241E29

needs 3.0:1 (large text)

32px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Commercial	1.29:1	3.0:1	#000000	#241E29	Fail
h1 Defense	5.85:1	3.0:1	#000000	#878787	Pass
h1 Space	5.85:1	3.0:1	#000000	#878787	Pass
h1 Services	5.85:1	3.0:1	#000000	#878787	Pass
h1 Safety	5.85:1	3.0:1	#000000	#878787	Pass
h1 Innovation	5.85:1	3.0:1	#000000	#878787	Pass
h1 Company	5.85:1	3.0:1	#000000	#878787	Pass
h2 Connect, protect and…	5.85:1	3.0:1	#000000	#878787	Pass
h2 Innovating aerospace…	5.85:1	3.0:1	#000000	#878787	Pass
h2 Supporting responsib…	5.85:1	3.0:1	#000000	#878787	Pass
h3 Search	5.85:1	3.0:1	#000000	#878787	Pass
h3 Commercial	5.85:1	3.0:1	#000000	#878787	Pass
h3 Defense	5.85:1	3.0:1	#000000	#878787	Pass
h3 Space	5.85:1	3.0:1	#000000	#878787	Pass
h3 Services	5.85:1	3.0:1	#000000	#878787	Pass
h3 Safety	5.85:1	3.0:1	#000000	#878787	Pass
h3 Innovation	5.85:1	3.0:1	#000000	#878787	Pass
h3 Company	5.85:1	3.0:1	#000000	#878787	Pass
h3 Recent news	5.85:1	3.0:1	#000000	#878787	Pass
h3 Featured products	5.85:1	3.0:1	#000000	#878787	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

Lighthouse Accessibility Audits

Score 91/100 — 4 failing, 29 passed

PASS

91

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#container-2fc0ef3e62 > div.jumbotron > div#teaser-526d123299 > button.jumbotron-pause-button `div#container-2fc0ef3e62 > div.jumbotron > div#teaser-526d123299 > button.jumbotron-pause-button`

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.

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
Learn more `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`
Cookie Settings `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler`

These are opportunities to improve the legibility of your content.

Navigation

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
Boeing backs U.S. Army with digital and logistics sustainment capabilities `div#teaser-260a23bacb > a.cmp-card__link > div.card-body > h6.cmp-card__title`
A leading global aerospace company and top U.S. exporter, Boeing develops, manu… `div#section-beb9885678 > div.text > div#text-935dea097f > h5`
We're engineering the future of aerospace by combining smart, sustainable innov… `div#section-6a1f5977eb > div.text > div#text-b1baa726d9 > h5`
Stock Price `div#container-4f575fe8d6 > div.title > div#title-83da06824f > h6.cmp-title__text`

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
MENU `div.container > div#meganavHolder > div.button > a#navbarToggle`
Learn more `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

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

●`button`, `link`, and `menuitem` elements have accessible names

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

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