Skip to content
https://canonical.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
3
REVIEW
5
PASS
5
INFO
0
Checks
13
5 PASS 5 REVIEW 3 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #262626
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Categories" MAIN (missing!) CONTENTINFO footer

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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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::
Apple touch icon present
Info::
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
Info::
Name present: Canonical
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Canonical ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Canonical Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
A+
Heading Hierarchy
73 headings
PASS
73 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Quick links
  • H2 Categories
  • H2 Industries
  • H2 Case studies ›
  • H2 Categories
  • H2 Industries
  • H2 Case studies ›
  • H2 Partner programs
  • H2 Quick links
  • H2 Partner programs
  • H2 Quick links
  • H2 Roles by department
  • H2 Working here
  • H2 Roles by department
  • H2 Working here
  • H2 Explore Canonical
  • H2 Latest updates
  • H2 Explore Canonical
  • H2 Latest updates
  • H2 Company highlights ›
  • H1 Trusted open source
  • H2 New security research
  • H2 Innovate on your own terms
  • H3 Start with Ubuntu
  • H3 Take control of your infrastructure
  • H3 Build apps at speed and stay secure
  • H3 Get an optimized stack for data and AI
  • H3 Deploy smart things at the edge
  • H2 Get full-stack security, support, and compliance
  • H2 Do more with trusted open source
  • H3 Unlocking economies of scale with open source infrastructure
  • H3 Lowering the cost and complexity of critical space missions
  • H3 Putting business continuity at the heart of cloud migration
  • H3 Securing medical devices to improve healthcare outcomes
  • H3 Meeting FedRAMP compliance for government contracts
  • H2 Accelerate innovation on any platform
  • H3 Cloud
  • H3 Silicon
  • H3 Hardware
  • H2 News and insights from the source
  • H3 Latest stories
  • H3 Webinars and events
  • H3 Guides and research
  • H3 Canonical joins the Rust Foundation as a Gold Member
  • H3 Canonical partners with Snyk for scanning chiseled Ubuntu containers
  • H3 Canonical announces it will distribute NVIDIA DOCA-OFED in Ubuntu
  • H3 (empty)
  • H3 Join a Canonical day near you
  • H3 Resolve the tension between security and stability
  • H3 Ubuntu on Windows Subsystem for Linux
  • H3 Sovereign cloud: the essential guide for enterprises
  • H3 Prepare your devices for the CRA
  • H3 The state of global open source
  • H3 Contact Canonical
  • H3 Your comments
  • H2 Your tracker settings

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

A+
Alt Text Quality
All 67 images OK
PASS
All 67 images OK
Info::
40 decorative image(s) correctly marked
Info::
27 image(s) with good alt text
67 images 27 good alt text 40 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 48 controls labeled
PASS
All 48 controls labeled
Info::
48 control(s) properly labeled
48 controls
48 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#navigation-searchsearchSearch our sitesaria-label
#about-your-projecttextareaAbout your projectfor/id
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
inputcheckboxnone
#desktop-workstationcheckboxnone
#physical-servercheckboxnone
#public-cloudcheckboxnone
#virtual-machinecheckboxnone
#iot-edge-devicecheckboxnone
#less-5-machinesradionone
#5-to-15-machinesradionone
#15-to-50-machinesradionone
#50-to-100-machinesradionone
#greater-than-100radionone
#ubuntu-repositoriescheckboxnone
#github-upstreamcheckboxnone
#internally-approved-repositorycheckboxnone
#opensource-i-dont-knowcheckboxnone
#pcicheckboxnone
#hipaacheckboxnone
#fismacheckboxnone
#fips-140checkboxnone
#ncsccheckboxnone
#disa-stigcheckboxnone
#fedrampcheckboxnone
#cis-benchmarkcheckboxnone
#individual-developerscheckboxnone
#project-teamcheckboxnone
#third-party-vendorcheckboxnone
#tracking-i-dont-knowcheckboxnone
#firstNametextFirst name:for/id
#lastNametextLast name:for/id
#emailemailEmail:for/id
#companytextCompany:for/id
#titletextJob Title:for/id
#countryselectCountry:for/id
#phonetelMobile/cell phone number:for/id
#selfReportedAttributiontextHow did you hear about us?:for/id
canonicalUpdatesOptIncheckboxnone
#Comments_from_lead__ctextareaYour commentsnone
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)
ElementRatioRequiredFGBGResult
h1 Trusted6.84:13.0:1
#000000
#939393
Pass
h1 open source6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.0:1
#000000
#939393
Pass
h2 Quick links6.84:13.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 93/100 — 2 failing, 29 passed
PASS
93

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
privacy policy footer.p-footer > div.row > p.p-text--small > a

These are opportunities to improve the legibility of your content.

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
Improve this site div.p-section--shallow > ul.p-list > li.p-list__item--condensed > 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
●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
●`[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.
●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
●`<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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○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
○`<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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback