Skip to content
https://www.fedoraproject.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
Alt Text Quality
Action
17 of 19 images have issues
FIX
17 of 19 images have issues
Critical::
17 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
4 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
2 image(s) with good alt text
19 images 2 good alt text 17 missing
IssueCount
missing17 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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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.
D
Lighthouse Accessibility Audits
Action
Score 67/100 — 7 failing, 14 passed
FIX
67

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Latest release header.-mb-1 > section.container > a.my-4 > p.text-xs
43 header.-mb-1 > section.container > a.my-4 > p.text-5xl
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit
Learn More div.container > div.relative > div.absolute > a.max-w-fit

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Editions Workstation KDE Plasma Server Cloud CoreOS IoT footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Atomic Desktops Silverblue Kinoite Sway Atomic Budgie Atomic COSMIC Atomic footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Spins Xfce Desktop Cinnamon Desktop MATE+Compiz Desktop i3 Tiling WM LXQt Deskt… footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Labs Astronomy Design Suite Games Jam Python Classroom Scientific Security Lab footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label
Languages العربية Беларуская Bulgarian Català Čeština Deutsch Ελληνικά English … footer.bg-gray-200 > nav.p-4 > div.mx-auto > div.footer-label

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
The leading Linux desktop div.container > div.relative > a > h3.bg-gradient-to-r

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.scroll-smooth html.scroll-smooth

These are opportunities to improve the interpretation of your content by users in different locales.

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.section-headers > div#section-header-3 > div.m-icon > img.FPImage div.section-headers > div#section-header-3 > div.m-icon > img.FPImage
section.align-end > a > div.flex > img.FPImage section.align-end > a > div.flex > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage
section.w-full > div.container > div.relative > img.FPImage section.w-full > div.container > div.relative > img.FPImage

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#__nuxt > div#app > nav#mobile > input#expander div#__nuxt > div#app > nav#mobile > input#expander

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
main.w-full > header.-mb-1 > section.align-end > a main.w-full > header.-mb-1 > section.align-end > 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.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●`[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
●Document has a `<title>` element
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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
○Buttons have an accessible name
○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 a valid value for its `[lang]` attribute
○`<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.
○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.
C
Form Accessibility
Action
47 of 67 controls have issues
REVIEW
47 of 67 controls have issues
Critical::
47 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="radio" name="lock0" id="button-downloads-a">; <input type="radio" name="lock0" id="button-downloads-b">; <input type="radio" name="lock1" id="button-downloads-0-a">; <input type="radio" name="lock1" id="button-downloads-0-b">; <input type="radio" name="lock1" id="button-downloads-1-a">; <input type="radio" name="lock1" id="button-downloads-1-b">; <input type="radio" name="lock1" id="button-downloads-2-a">; <input type="radio" name="lock1" id="button-downloads-2-b">; <input type="radio" name="lock1" id="button-downloads-3-a">; <input type="radio" name="lock1" id="button-downloads-3-b"> (+37 more)
Info::
20 control(s) properly labeled
67 controls
20 labeled
0 placeholder only
47 unlabeled
ControlTypeLabelMethod
#m-button-downloadsradioGet Fedorafor/id
#m-button-downloads-0radioEditionsfor/id
#m-button-downloads-1radioAtomic Desktopsfor/id
#m-button-downloads-2radioSpinsfor/id
#m-button-downloads-3radioLabsfor/id
#m-button-contributorsradioContributorsfor/id
#m-button-contributors-0radioAccounts & Appsfor/id
#m-button-contributors-1radioPackaging & Developmentfor/id
#m-button-contributors-2radioContributor Guidesfor/id
#m-button-contributors-3radioNew Contributorsfor/id
#m-button-connectionsradioConnectionsfor/id
#m-button-connections-0radioNews & Publicationsfor/id
#m-button-connections-1radioAsk Fedorafor/id
#m-button-connections-2radioProject Discussionfor/id
#m-button-connections-3radioSocial & Eventsfor/id
#m-button-helpradioHelpfor/id
#m-button-help-0radioAsk Fedorafor/id
#m-button-help-1radioUser Guidesfor/id
#m-button-help-2radioDocumentationfor/id
#m-button-help-3radioAboutfor/id
#button-connections-aradio(none)none
#button-connections-bradio(none)none
#button-connections-0-aradio(none)none
#button-connections-0-bradio(none)none
#button-connections-1-aradio(none)none
#button-connections-1-bradio(none)none
#button-connections-2-aradio(none)none
#button-connections-2-bradio(none)none
#button-connections-3-aradio(none)none
#button-connections-3-bradio(none)none
#button-help-aradio(none)none
#button-help-bradio(none)none
#button-help-0-aradio(none)none
#button-help-0-bradio(none)none
#button-help-1-aradio(none)none
#button-help-1-bradio(none)none
#button-help-2-aradio(none)none
#button-help-2-bradio(none)none
#button-help-3-aradio(none)none
#button-help-3-bradio(none)none
#button-languages-aradio(none)none
#button-languages-bradio(none)none
#button-languages-0-aradio(none)none
#button-languages-0-bradio(none)none
#button-languages-1-aradio(none)none
#button-languages-1-bradio(none)none
#expandercheckbox(none)none
#button-downloads-aradio(none)none
#button-downloads-bradio(none)none
#button-downloads-0-aradio(none)none
#button-downloads-0-bradio(none)none
#button-downloads-1-aradio(none)none
#button-downloads-1-bradio(none)none
#button-downloads-2-aradio(none)none
#button-downloads-2-bradio(none)none
#button-downloads-3-aradio(none)none
#button-downloads-3-bradio(none)none
#button-contributors-aradio(none)none
#button-contributors-bradio(none)none
#button-contributors-0-aradio(none)none
#button-contributors-0-bradio(none)none
#button-contributors-1-aradio(none)none
#button-contributors-1-bradio(none)none
#button-contributors-2-aradio(none)none
#button-contributors-2-bradio(none)none
#button-contributors-3-aradio(none)none
#button-contributors-3-bradio(none)none

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

<input type="radio" name="lock0" id="button-downloads-a">; <input type="radio" name="lock0" id="button-downloads-b">; <input type="radio" name="lock1" id="button-downloads-0-a">; <input type="radio" name="lock1" id="button-downloads-0-b">; <input type="radio" name="lock1" id="button-downloads-1-a">; <input type="radio" name="lock1" id="button-downloads-1-b">; <input type="radio" name="lock1" id="button-downloads-2-a">; <input type="radio" name="lock1" id="button-downloads-2-b">; <input type="radio" name="lock1" id="button-downloads-3-a">; <input type="radio" name="lock1" id="button-downloads-3-b"> (+37 more)

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

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 Fedora Logo Text ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Fedora Linux | The Fedora Project
4.08:1
#000000
on
#3C6EB4
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
4.08:1
#000000
on
#3C6EB4
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 It's your Operating …18.75:13.0:1
#000000
#F1F2F4
Pass
h2 Editions18.75:13.0:1
#000000
#F1F2F4
Pass
h2 Want more Fedora opt…18.75:13.0:1
#000000
#F1F2F4
Pass
h2 Support Resources18.75:13.0:1
#000000
#F1F2F4
Pass
h3 A Registered Digital…18.75:13.0:1
#000000
#F1F2F4
Pass
h3 The leading Linux de…18.75:13.0:1
#000000
#F1F2F4
Pass
h3 The next generation …18.75:13.0:1
#000000
#F1F2F4
Pass
h3 A Community Server O…18.75:13.0:1
#000000
#F1F2F4
Pass
h3 The lightweight VM e…18.75:13.0:1
#000000
#F1F2F4
Pass
h3 The container optimi…18.75:13.0:1
#000000
#F1F2F4
Pass
h3 The solid edge found…18.75:13.0:1
#000000
#F1F2F4
Pass
h3 Atomic Desktops18.75:13.0:1
#000000
#F1F2F4
Pass
h3 Fedora Spins18.75:13.0:1
#000000
#F1F2F4
Pass
h3 Fedora Labs18.75:13.0:1
#000000
#F1F2F4
Pass
h3 Miscellaneous Downlo…18.75:13.0:1
#000000
#F1F2F4
Pass
h3 Documentation18.75:13.0:1
#000000
#F1F2F4
Pass
h3 Support18.75:13.0:1
#000000
#F1F2F4
Pass
h3 Chat18.75:13.0:1
#000000
#F1F2F4
Pass
title Fedora Linux | The F…4.08:14.5:1
#000000
#3C6EB4
Fail
a Skip to main content4.08:14.5:1
#000000
#3C6EB4
Fail

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
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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 ASIDE 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
18 headings, 1 skip(s)
PASS
18 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 It's your Operating System.
  • H3 A Registered Digital Public Good skipped
  • H2 Editions
  • H3 The leading Linux desktop
  • H3 The next generation personal desktop
  • H3 A Community Server OS
  • H3 The lightweight VM environment
  • H3 The container optimized OS
  • H3 The solid edge foundation
  • H2 Want more Fedora options?
  • H3 Atomic Desktops
  • H3 Fedora Spins
  • H3 Fedora Labs
  • H3 Miscellaneous Downloads
  • H2 Support Resources
  • H3 Documentation
  • H3 Support
  • H3 Chat

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

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

Send Feedback