Skip to content
https://kde.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✗ PNG Icons Missing
✗ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <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.
B
Alt Text Quality
1 of 38 images have issues
REVIEW
1 of 38 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
12 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
38 images 25 good alt text 12 decorative 1 missing
IssueCount
missing1 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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="s">
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#donateAmountFieldtextAmountfor/id
stext(Search)placeholder only
stext(Search)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="s">; <input type="text" name="s">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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 - KDE Community ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: KDE Community
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name KDE Community ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name KDE Community Display Mode standalone Theme Color #1f99f3 Background Color #1f99f3 Icons 2 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 6 failing, 22 passed
REVIEW
78

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.

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
div.container > div.row > div.col-lg-5 > a.mx-auto div.container > div.row > div.col-lg-5 > a.mx-auto

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.

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
Join the fun here div.container > div.row > div.col-auto > a.button
Learn More section > div.container > div.mb-3 > a.button
Get Involved section > div.container > div.mb-3 > a.noblefir
Install on your computer section.text-center > div.container > div.text-center > a.learn-more
Germany div.row > div.col-12 > div.text-muted > span.badge
Canada div.row > div.col-12 > div.text-muted > span.badge
Austria div.row > div.col-12 > div.text-muted > span.badge
Brazil div.row > div.col-12 > div.text-muted > span.badge
Maintained by KDE Webmasters (public mailing list). Generated from 60d4cce. footer#kFooter > div#kLegal > p.d-block > small.maintenance
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V. … footer#kFooter > div#kLegal > p.d-block > small.trademark

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
See all devices section > div.container > p > a
Why Donate? div#kDonateForm > div.center > h2.h5 > a
KDE Webmasters div#kLegal > p.d-block > small.maintenance > a
60d4cce div#kLegal > p.d-block > small.maintenance > a

These are opportunities to improve the legibility of your content.

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
div.row > div.col > a > img div.row > div.col > a > img

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
div.container > div.row > div.col > a div.container > div.row > div.col > a
body > footer#kFooter > div#kSocial > a body > footer#kFooter > div#kSocial > a

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.

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
Go to slide 1 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 7 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 8 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 9 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 10 div.for-you-carousel > div.swiper > div.swiper-pagination > span.swiper-pagination-bullet

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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●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
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●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.
○`[accesskey]` values are unique
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○`<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
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
6 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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
Heading Hierarchy
77 headings
PASS
77 headings
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 KDE is turning 30 this year!
  • H1 What is KDE?
  • H1 Plasma duplicate H1
  • H2 KDE Applications
  • H3 Powerful, multi-platform, and for everyone
  • H3 Marknote
  • H3 Kontact
  • H3 KDevelop
  • H3 For You
  • H3 We develop KDE for everyone, from kids to grandparents and from professionals to hobbyists.
  • H2 KDE For Digital Sovereignty
  • H2 KDE for Creators
  • H2 KDE for Scientists
  • H2 KDE for Activists
  • H2 KDE for Developers
  • H2 KDE for Gamers
  • H2 KDE for Kids
  • H2 KDE For Students
  • H2 KDE for Travelers
  • H2 KDE for Windows 10 Exiles
  • H2 KDE For Digital Sovereignty
  • H2 KDE for Creators
  • H2 KDE for Scientists
  • H2 KDE for Activists
  • H2 KDE for Developers
  • H2 KDE for Gamers
  • H2 KDE for Kids
  • H2 KDE For Students
  • H2 KDE for Travelers
  • H2 KDE for Windows 10 Exiles
  • H2 KDE For Digital Sovereignty
  • H2 KDE for Creators
  • H2 KDE for Scientists
  • H2 KDE for Activists
  • H2 KDE for Developers
  • H2 KDE for Gamers
  • H2 KDE for Kids
  • H2 KDE For Students
  • H2 KDE for Travelers
  • H2 KDE for Windows 10 Exiles
  • H2 Devices
  • H2 Buy a computer with Plasma preinstalled
  • H3 Steam Deck
  • H3 Tuxedo Computers
  • H3 KDE Slimbook
  • H3 Kubuntu Focus
  • H2 Announcements
  • H3 KDE Gear ⚙️ 26.04
  • H3 KDE Ships Frameworks 6.25.0
  • H3 KDE Plasma 6.6.4, Bugfix Release for April
  • H3 KDE Plasma 6.6.3, Bugfix Release for March
  • H2 KDE Eco
  • H3 Join the sustainable software movement
  • H1 Community duplicate H1
  • H2 Next Events
  • H3 Linux Application Summit
  • H3 FOSSY 2026
  • H3 Akademy 2026
  • H3 IFBA - KDE's Birthday Party
  • H2 Previous Events
  • H2 Kdenlive 2025 Sprint
  • H2 FOSDEM 2025
  • H2 conf.kde.in 2025
  • H2 Scale22x
  • H2 FOSSAsia
  • H2 IndiaFOSS
  • H2 Linux App Summit
  • H2 Akademy-es 2025
  • H2 Akademy 2025
  • H3 KDE Patrons
  • H2 Donate to KDE Why Donate?
  • H2 Visit the KDE MetaStore
  • H3 Products
  • H3 Develop
  • H3 News & Press
  • H3 Resources
  • H3 Destinations

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

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 What is KDE?20.47:13.0:1
#000000
#FCFCFC
Pass
h1 Plasma20.47:13.0:1
#000000
#FCFCFC
Pass
h1 Community20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE Applications20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE For Digital Sove…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Creators20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Scientists20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Activists20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Developers20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Gamers20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Kids20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE For Students20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Travelers20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Windows 10 E…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE For Digital Sove…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Creators20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Scientists20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Activists20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Developers20.47:13.0:1
#000000
#FCFCFC
Pass
h2 KDE for Gamers20.47:13.0:1
#000000
#FCFCFC
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback