Accessibility

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #000000

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 2 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

C

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

Skip navigation link present

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

B

Link & Button Quality

359 links, 4 buttons — all OK

REVIEW

359 links, 4 buttons — all OK

3 image-only link(s) without alt text

356 link(s) with descriptive text

359 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cncf.io/blog/2026/04/06/peer…	Peer-to-Peer acceleration for …	img no alt	Add alt attribute to the image
https://www.cncf.io/blog/2026/04/02/gito…	GitOps policy-as-code: Securin…	img no alt	Add alt attribute to the image
https://www.cncf.io/blog/2026/03/31/sust…	Sustaining OpenTelemetry: Movi…	img no alt	Add alt attribute to the image

360 links and buttons have descriptive text

B

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: CNCF

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name CNCF ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name CNCF Display Mode standalone Theme Color #000 Background Color #000 Icons 2 icon(s)

A+

Heading Hierarchy

17 headings

PASS

17 headings

Single H1 present

H4 Mumbai, India
H1 MAKE CLOUD NATIVE UBIQUITOUS
H2 CNCF is the open source, vendor-neutral hub of cloud native computing, hosting projects like Kubernetes and Prometheus to make cloud native universal and sustainable.
H2 CNCF projects are the foundation of cloud native computing
H2 Transforming leadingorganizations across the world
H2 Ready to go cloud native? Join our foundation of doers
H3 Members
H3 Contributors
H3 End Users
H3 New to CNCF?
H3 Upcoming Events
H2 Together we are #TeamCloudNative
H2 We're redefining how software gets built
H2 Latest from CNCF
H3 Peer-to-Peer acceleration for AI model distribution with Dragonfly
H3 GitOps policy-as-code: Securing Kubernetes with Argo CD and Kyverno
H3 Sustaining OpenTelemetry: Moving from dependency management to stewardship

A+

Alt Text Quality

All 199 images OK

PASS

All 199 images OK

4 decorative image(s) correctly marked

195 image(s) with good alt text

199 images 195 good alt text 4 decorative

All images have appropriate alt text.

A

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search-bar	search	Search CNCF	for/id
input	submit	(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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | CNCF ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A

Favicon & Branding

6 icon(s) detected

PASS

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 MAKE	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h1 CLOUD NATIVE	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 CNCF is the open sou…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 , hosting projec…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 CNCF projects …	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Transforming leading	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 organizations across…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Ready to go cloud na…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Join our foundation …	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Together we are #…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 We're redefining how…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h2 Latest from CNCF	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 Members	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 Contributors	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 End Users	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 New to CNCF?	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 Upcoming Events	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 Peer-to-Peer acceler…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 GitOps policy-as-cod…	20.65:1	3.0:1	#000000	#FDFDFD	Pass
h3 Sustaining OpenTelem…	20.65:1	3.0:1	#000000	#FDFDFD	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 95/100 — 2 failing, 27 passed

PASS

95

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

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Logo of KubeEdge `div.slider > div.slick-list > div.slick-track > div.slick-slide`
Logo of Istio `div.slider > div.slick-list > div.slick-track > div.slick-slide`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.no-focus-outline `html.no-focus-outline`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●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

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

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

○`[lang]` attributes have a valid value

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

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