Accessibility

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

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Skip navigation link detected

Back-to-top link detected

5 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 5 <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

Heading Hierarchy

Action

45 headings, 1 skip(s)

REVIEW

45 headings, 1 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H1 → H4 (missing H2)

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

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 A CTO’s guide to real-time Linux
H2 Understanding real-time systems, their use cases and inner workings.
H1 Open source storage for enterprises duplicate H1
H4 私たちの日本のウェブサイトを試してみてください › skipped
H4 嗨！你知道我们有中文站吗？立即带我去！ ›
H2 Modern enterprise open source
H2 Latest news from our blog ›
H3 RISC-V 101 – what is it and what does it mean for Canonical?
H3 Ubuntu Summit 26.04 is coming: Save the date and share your story!
H3 How to manage Ubuntu fleets using on-premises Active Directory and ADSys
H3 Canonical partners with Snyk for scanning chiseled Ubuntu containers
H3 (empty)
H3 (empty)
H2 Energize your engineers
H2 Open source security
H2 Significant enterprise savings
H2 Public cloud optimization
H2 Multi-cloud Kubernetes and containers
H2 Carrier–grade private cloud
H2 Ultra secure things
H2 Workstations and desktops
H2 Data center automation
H2 Smart robots of all shapes and sizes
H2 Multi–cloud applications – beyond PAAS
H3 The Ubuntu experts
H3 Your comments
H2 OpenStack OpenStack
H2 Ceph Ceph
H2 Kubernetes Kubernetes
H2 Managed infrastructure Managed infrastructure
H2 AI / ML AI / ML
H2 Robotics Robotics
H2 IoT IoT
H2 Ubuntu Core Ubuntu Core
H2 Ubuntu Desktop Ubuntu Desktop
H2 Ubuntu Server Ubuntu Server
H2 Cloud Cloud
H2 Security Security
H2 Landscape Landscape
H2 Containers Containers
H2 Downloads Downloads
H2 Support Support
H2 Pricing Pricing
H2 Sectors
H2 Your tracker settings

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

C

Link & Button Quality

Action

2 issue(s) across 314 links and 15 buttons

REVIEW

2 issue(s) across 314 links and 15 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: ;

10 image-only link(s) without alt text

302 link(s) with descriptive text

314 links

2 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	Canonical Ubuntu	img no alt	Add alt attribute to the image
https://ubuntu.com/	Ubuntu	img no alt	Add alt attribute to the image
https://ubuntu.com/pro	Ubuntu Pro	img no alt	Add alt attribute to the image
https://snapcraft.io/	Snapcraft	img no alt	Add alt attribute to the image
https://ubuntu.com/lxd	LXD	img no alt	Add alt attribute to the image
https://maas.io/	MAAS	img no alt	Add alt attribute to the image
https://ubuntu.com/openstack	OpenStack	img no alt	Add alt attribute to the image
https://ubuntu.com/ceph	Ceph	img no alt	Add alt attribute to the image
https://ubuntu.com/kubernetes	Kubernetes	img no alt	Add alt attribute to the image
https://juju.is/	Juju	img no alt	Add alt attribute to the image
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label

317 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

;

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

C

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

B

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Canonical Ubuntu

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

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

Name Canonical Ubuntu Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

A

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

5 <nav> landmark(s) found

2 of 5 <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

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+

Alt Text Quality

All 72 images OK

PASS

All 72 images OK

22 decorative image(s) correctly marked

50 image(s) with good alt text

72 images 50 good alt text 22 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 50 controls labeled

PASS

All 50 controls labeled

50 control(s) properly labeled

50 controls

50 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search	search	Search our sites	aria-label
q	search	Search our sites	aria-label
#about-your-project	textarea	Tell us about your project	aria-label
input	checkbox		none
input	checkbox		none
input	checkbox		none
input	checkbox		none
input	checkbox		none
input	checkbox		none
input	checkbox		none
input	checkbox		none
input	checkbox		none
input	checkbox		none
#desktop-workstation	checkbox		none
#physical-server	checkbox		none
#public-cloud	checkbox		none
#virtual-machine	checkbox		none
#iot-edge-device	checkbox		none
#less-5-machines	radio		none
#5-to-15-machines	radio		none
#15-to-50-machines	radio		none
#50-to-100-machines	radio		none
#greater-than-100	radio		none
#ubuntu-repositories	checkbox		none
#github-upstream	checkbox		none
#internally-approved-repository	checkbox		none
#i-dont-know-how-i-consume-oss	checkbox		none
#pci	checkbox		none
#hipaa	checkbox		none
#fisma	checkbox		none
#fips-140	checkbox		none
#ncsc	checkbox		none
#disa-stig	checkbox		none
#fedramp	checkbox		none
#cis-benchmark	checkbox		none
#individual-developers	checkbox		none
#project-team	checkbox		none
#third-party-vendor	checkbox		none
#i-dont-know-tracking-responsibility	checkbox		none
#advice	textarea	What advice are you looking for?	aria-label
#firstName	text	First name:	for/id
#lastName	text	Last name:	for/id
#email	email	Email:	for/id
#company	text	Company:	for/id
#title	text	Job Title:	for/id
#country	select	Country:	for/id
input	text	Search	aria-label
#phone	tel	Mobile/cell phone number:	for/id
canonicalUpdatesOptIn	checkbox		none
#Comments_from_lead__c	textarea	Your comments	none

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 404: Page not found | Ubuntu ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /static/css/print.css?v=b63170c

Print Stylesheet ✓ Print Optimized

Print stylesheet /static/css/print.css?v=b63170c ✓Inline @media print Not detected ✗

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 A CTO’s guide to r…	6.84:1	3.0:1	#000000	#939393	Pass
h1 Open source storage …	6.84:1	3.0:1	#000000	#939393	Pass
h2 Understanding real-t…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Modern enterprise op…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Latest news from	6.84:1	3.0:1	#000000	#939393	Pass
h2 Energize your engine…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Open source security	6.84:1	3.0:1	#000000	#939393	Pass
h2 Significant enterpri…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Public cloud optimiz…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Multi-cloud Kubernet…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Carrier–grade priv…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Ultra secure things	6.84:1	3.0:1	#000000	#939393	Pass
h2 Workstations and des…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Data center automati…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Smart robots of all …	6.84:1	3.0:1	#000000	#939393	Pass
h2 Multi–cloud applic…	6.84:1	3.0:1	#000000	#939393	Pass
h2 Sectors	6.84:1	3.0:1	#000000	#939393	Pass
h2 Your tracker setting…	6.84:1	3.0:1	#000000	#939393	Pass
h3 The Ubuntu experts	6.84:1	3.0:1	#000000	#939393	Pass
h3 Your comments	6.84:1	3.0:1	#000000	#939393	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 100/100 — 0 failing, 32 passed

PASS

100

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.

○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

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[accesskey]` values are unique

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Skip links are focusable.

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

○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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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