Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Alt Text Quality

Action

11 of 11 images have issues

FIX

11 of 11 images have issues

11 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

10 image-in-link without alt text

An image inside a link with no alt creates an empty link.

11 images 11 missing

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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Favicon & Branding

Action

4 icon(s) detected

FIX

4 icon(s) detected

No favicon.ico at site root

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

HTML icon links detected

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

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

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.

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 ✗

Heading Hierarchy

15 headings, 2 skip(s)

REVIEW

15 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H2 → H5 (missing H3)

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

H1 Delivering the best technology, at scale
H3 Core technologies to accelerate innovation skipped
H4 AI Infrastructure
H4 Automotive
H4 Data Center
H4 Private Cloud
H4 Wi-Fi 8
H3 Popular Links
H2 Latest Products
H2 Latest News
H2 Latest Blogs
H5 Broadcom’s Cathy Liu: A Trailblazer in SerDes Technology and Life skipped
H5 OFC 2026: Broadcom Paves the Path for the 200T AI Era
H5 From Workshop Tools to Far-Field Voice: How Broadcom’s Distinguished Engineer Qutubuddin “Qutub” Saifee Built a Career on First Principles
H2 About Us

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

46 links, 11 buttons — all OK

REVIEW

46 links, 11 buttons — all OK

5 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="/solutions/ai-solutions/ai-infrastructure"]; a[href="/solutions/industry/industrial-automotive/automotive-solutions"]; a[href="/solutions/data-center/data-center-solutions"]; a[href="/solutions/private-cloud"]; a[href="/solutions/wireless-mobile-communications/wifi8"]

3 link(s) open in new tab without warning

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

Got: https://www.linkedin.com/company/broadcom; https://x.com/Broadcom; https://www.youtube.com/user/BroadcomCorporation

38 link(s) with descriptive text

46 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/solutions/ai-solutions/ai-infrastructur…	AI Infrastructure	img no alt	Add alt attribute to the image
/solutions/industry/industrial-automotiv…	Automotive	img no alt	Add alt attribute to the image
/solutions/data-center/data-center-solut…	Data Center	img no alt	Add alt attribute to the image
/solutions/private-cloud	Private Cloud	img no alt	Add alt attribute to the image
/solutions/wireless-mobile-communication…	Wi-Fi 8	img no alt	Add alt attribute to the image
https://www.linkedin.com/company/broadco…	LinkedIn (opens to new window)	new tab	Add '(opens in new tab)' to text
https://x.com/Broadcom	Twitter (opens to new window)	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/BroadcomCor…	YouTube (opens to new window)	new tab	Add '(opens in new tab)' to text

49 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="/solutions/ai-solutions/ai-infrastructure"]; a[href="/solutions/industry/industrial-automotive/automotive-solutions"]; a[href="/solutions/data-center/data-center-solutions"]; a[href="/solutions/private-cloud"]; a[href="/solutions/wireless-mobile-communications/wifi8"]

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.

https://www.linkedin.com/company/broadcom; https://x.com/Broadcom; https://www.youtube.com/user/BroadcomCorporation

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 - Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

8 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 8 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA

a Skip to main content

3.07:1

#000000

#6C4B94

needs 4.5:1 (normal text)

16px · top of page (header area)

span Products

3.07:1

#000000

#6C4B94

needs 4.5:1 (normal text)

16px · above the fold

span Solutions

3.07:1

#000000

#6C4B94

needs 4.5:1 (normal text)

16px · above the fold

span Support and Services

3.07:1

#000000

#6C4B94

needs 4.5:1 (normal text)

16px · above the fold

span Company

3.07:1

#000000

#6C4B94

needs 4.5:1 (normal text)

16px · above the fold

span How To Buy

3.07:1

#000000

#6C4B94

needs 4.5:1 (normal text)

16px · above the fold

button Support Portal

3.07:1

#000000

#6C4B94

needs 4.5:1 (normal text)

16px · above the fold

a Register

3.07:1

#000000

#6C4B94

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Delivering the best …	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Latest Products	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Latest News	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 Latest Blogs	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h2 About Us	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h3 Core technologies to…	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h3 Popular Links	19.60:1	3.0:1	#000000	#F7F7F7	Pass
title Broadcom Inc. \| Conn…	19.27:1	4.5:1	#000000	#F5F5F6	Pass
a Broadcom	19.27:1	4.5:1	#000000	#F5F5F6	Pass
a Read the accessibili…	7.99:1	4.5:1	#000000	#9E9FA9	Pass
a Skip to main content	3.07:1	4.5:1	#000000	#6C4B94	Fail
span Products	3.07:1	4.5:1	#000000	#6C4B94	Fail
span Solutions	3.07:1	4.5:1	#000000	#6C4B94	Fail
span Support and Services	3.07:1	4.5:1	#000000	#6C4B94	Fail
span Company	3.07:1	4.5:1	#000000	#6C4B94	Fail
span How To Buy	3.07:1	4.5:1	#000000	#6C4B94	Fail
button Support Portal	3.07:1	4.5:1	#000000	#6C4B94	Fail
a Go To Portal	18.17:1	4.5:1	#000000	#E7F0F4	Pass
a Register	3.07:1	4.5:1	#000000	#6C4B94	Fail
a Forgot Username/Pass…	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.

Landmark Structure

12 landmarks

PASS

12 landmarks

<main> landmark present

8 <nav> landmark(s) found

8 of 8 <nav> elements are unlabeled

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

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

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

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	SEARCH	aria-label

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 22 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

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
Core technologies to accelerate innovation `div.container > div.solutions-container > div.hm-section-title > h3`
Broadcom Announces Tanzu Platform Agent Foundations: Bringing PaaS Simplicity a… `div.loaded > ul > li > h5`
Broadcom’s Cathy Liu: A Trailblazer in SerDes Technology and Life `div.feed-body > ul > li > h5`

These are opportunities to improve keyboard navigation in your application.

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
a.lnk > div.solution-icon > div > img.image-source `a.lnk > div.solution-icon > div > img.image-source`
a.lnk > div.solution-icon > div > img.image-source `a.lnk > div.solution-icon > div > img.image-source`
a.lnk > div.solution-icon > div > img.image-source `a.lnk > div.solution-icon > div > img.image-source`
a.lnk > div.solution-icon > div > img.image-source `a.lnk > div.solution-icon > div > img.image-source`
a.lnk > div.solution-icon > div > img.image-source `a.lnk > div.solution-icon > div > img.image-source`

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.

○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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○Form elements have associated labels

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

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

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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