Skip to content
https://kubernetes.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Favicon & Branding
Action
7 icon(s) detected
FIX
7 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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'>.
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
Info::
1 navigation landmark(s) detected
Info::
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 1 <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.
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #326de6 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
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
title Kubernetes
1.59:1
#000000
on
#303030
needs 4.5:1 (normal text)
16px · top of page (header area)
span Kubernetes
1.59:1
#000000
on
#303030
needs 4.5:1 (normal text)
16px · top of page (header area)
span Documentation
1.59:1
#000000
on
#303030
needs 4.5:1 (normal text)
16px · top of page (header area)
span Kubernetes Blog
1.61:1
#000000
on
#313131
needs 4.5:1 (normal text)
16px · top of page (header area)
span Training
1.59:1
#000000
on
#303030
needs 4.5:1 (normal text)
16px · above the fold
span Careers
1.59:1
#000000
on
#303030
needs 4.5:1 (normal text)
16px · above the fold
span Partners
1.59:1
#000000
on
#303030
needs 4.5:1 (normal text)
16px · above the fold
span Community
1.59:1
#000000
on
#303030
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Production-Grade Con…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Absolute Beginne…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Attend upcoming Kube…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Kubernetes Features21.00:13.0:1
#000000
#FFFFFF
Pass
title Kubernetes1.59:14.5:1
#000000
#303030
Fail
span Kubernetes1.59:14.5:1
#000000
#303030
Fail
span Documentation1.59:14.5:1
#000000
#303030
Fail
span Kubernetes Blog1.61:14.5:1
#000000
#313131
Fail
span Training1.59:14.5:1
#000000
#303030
Fail
span Careers1.59:14.5:1
#000000
#303030
Fail
span Partners1.59:14.5:1
#000000
#303030
Fail
span Community1.59:14.5:1
#000000
#303030
Fail
a Versions9.25:14.5:1
#000000
#ACACAC
Pass
a Release Information21.00:14.5:1
#000000
#FFFFFF
Pass
a v1.3519.77:14.5:1
#000000
#F8F8F8
Pass
a v1.3417.94:14.5:1
#000000
#EDEDED
Pass
a v1.3317.94:14.5:1
#000000
#EDEDED
Pass
a v1.3221.00:14.5:1
#000000
#FFFFFF
Pass
a v1.3121.00:14.5:1
#000000
#FFFFFF
Pass
a English21.00:14.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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 21 passed
REVIEW
82

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.

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
body.td-home > header > nav.js-navbar-scroll > button#hamburger body.td-home > header > nav.js-navbar-scroll > button#hamburger

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.td-home > header > nav.js-navbar-scroll > a.navbar-brand body.td-home > header > nav.js-navbar-scroll > a.navbar-brand

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
Automated rollouts and rollbacks div > div.feature-box > h3 > a
Service discovery and load balancing div > div.feature-box > h3 > a
Storage orchestration div > div.feature-box > h3 > a
Secret and configuration management div > div.feature-box > h3 > a
Automatic bin packing div > div.feature-box > h3 > a
Batch execution div > div.feature-box > h3 > a
Self-healing div > div.feature-box > h3 > a
Horizontal scaling div > div.feature-box > h3 > a
Vertical scaling div > div.feature-box > h3 > a
IPv4/IPv6 dual-stack div > div.feature-box > h3 > a
Designed for extensibility div > div.feature-box > h3 > a

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
Planet scale section#td-block-0-section > div.main-section > div.content > h4#planet-scale

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Learn Kubernetes Basics div.td-outer > main.td-main > section.row > a

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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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.
○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.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN CONTENTINFO footer

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

A
Heading Hierarchy
19 headings, 1 skip(s)
PASS
19 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Production-Grade Container Orchestration
  • H4 Planet scale skipped
  • H4 Never outgrow
  • H4 Run K8s anywhere
  • H2 The Absolute Beginner's Guide To Cloud Native
  • H2 Attend upcoming KubeCon + CloudNativeCon events
  • H2 Kubernetes Features
  • H3 Automated rollouts and rollbacks
  • H3 Service discovery and load balancing
  • H3 Storage orchestration
  • H3 Secret and configuration management
  • H3 Automatic bin packing
  • H3 Batch execution
  • H3 Self-healing
  • H3 Horizontal scaling
  • H3 Vertical scaling
  • H3 IPv4/IPv6 dual-stack
  • H3 Designed for extensibility
  • H3 Case Studies

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

A+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
4 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
9 images 5 good alt text 4 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputsearchSearch this sitearia-label
inputsearchSearch this sitearia-label
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Page not found | Kubernetes ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Web Manifest
Valid manifest
PASS
Valid manifest
Info::
Name present: Kubernetes
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Kubernetes ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode browser ✗
Name Kubernetes Display Mode browser Theme Color #326ce5 Background Color #326ce5 Icons 2 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback