Accessibility

F

Heading Hierarchy

Action

53 headings, 6 skip(s)

FIX

53 headings, 6 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H6 (missing H3)

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

H4 Checkout the doc!
H6 "Zena" skipped
H2 Linux Mint 22.3
H5 Features skipped
H2 What is Linux Mint?
H5 Graphic Design skipped
H5 Productivity
H5 Multimedia
H5 Web
H5 Gaming
H2 Give it a try. You’ll Love it!
H2 Easy to use, fast and comfortable.
H3 OOTB
H3 KISS
H3 Home rule
H3 Rock solid
H3 Free and Open Source
H3 Community-centric
H2 Fun, helpful and passionate.
H4 Is it free? skipped
H4 Will it work on my computer?
H4 Can I keep Windows?
H4 Will it suit my needs?
H6 Scott Gilbertson skipped
H6 ars technica
H6 Whitson Gordon
H6 PCMag
H6 Sarvottam Kumar
H6 FossBytes
H6 Steven J. Vaughan-Nichols
H6 ZDNet
H6 David Hayward
H6 Linux Format
H6 Jack Wallen
H6 TechRepublic
H6 Scott Gilbertson
H6 ars technica
H6 Whitson Gordon
H6 PCMag
H6 Sarvottam Kumar
H6 FossBytes
H6 Steven J. Vaughan-Nichols
H6 ZDNet
H6 David Hayward
H6 Linux Format
H6 Jack Wallen
H6 TechRepublic
H2 Latest news
H2 A fantastic community!
H2 Partners and sponsors
H6 Quick Links skipped
H6 Info
H6 Support

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

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

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

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

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

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

F

Alt Text Quality

Action

7 of 12 images have issues

FIX

7 of 12 images have issues

7 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 image-in-link without alt text

An image inside a link with no alt creates an empty link.

5 decorative image(s) correctly marked

12 images 5 decorative 7 missing

Issue	Count
missing	7 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

Link & Button Quality

Action

22 issue(s) across 94 links and 11 buttons

FIX

22 issue(s) across 94 links and 11 buttons

12 link(s) with no accessible text

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

Got: /; https://www.eukhost.com/vps-hosting; https://unixshells.com; http://www.fit-pc.com/web/purchase/order-direct-mintbox/; https://www.datadoghq.com/; https://sucuri.net/; https://linuxmint.thinkpenguin.com/; http://duckduckgo.com/?t=lm; https://www.yahoo.com; https://www.hellotux.com/linux_mint (+2 more)

23 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://app.element.io/#/room/#linuxmint-space:matrix.org; https://www.facebook.com/pages/Linux-Mint/185238108180410; https://www.github.com/linuxmint; https://twitter.com/linux_mint; https://mastodon.social/@linuxmint; https://linuxmint-installation-guide.readthedocs.io/en/latest/; https://blog.linuxmint.com; https://forums.linuxmint.com; https://app.element.io/#/room/#linuxmint-space:matrix.org; https://community.linuxmint.com (+13 more)

10 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.owl-prev (#427 on page); button.owl-next (#429 on page); button.owl-dot (#432 on page); button.owl-dot (#434 on page); button.owl-dot (#436 on page); button.owl-dot (#438 on page); button.owl-dot (#440 on page); button.owl-dot (#442 on page); button.owl-prev (#529 on page); button.owl-next (#531 on page)

59 link(s) with descriptive text

94 links

12 empty

0 generic text

23 new tab

10 empty buttons

Element	Text	Issue	Suggested Fix
https://app.element.io/#/room/#linuxmint…	Chat Rooms	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/pages/Linux-Min…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.github.com/linuxmint	Github	new tab	Add '(opens in new tab)' to text
https://twitter.com/linux_mint	Twitter	new tab	Add '(opens in new tab)' to text
https://mastodon.social/@linuxmint	Mastodon	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
https://linuxmint-installation-guide.rea…	Installation Guide	new tab	Add '(opens in new tab)' to text
https://blog.linuxmint.com	Blog	new tab	Add '(opens in new tab)' to text
https://forums.linuxmint.com	Forums	new tab	Add '(opens in new tab)' to text
https://app.element.io/#/room/#linuxmint…	Chat Rooms	new tab	Add '(opens in new tab)' to text
https://community.linuxmint.com	Community website	new tab	Add '(opens in new tab)' to text
https://www.github.com/linuxmint	Github	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/pages/Linux-Min…	Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/linux_mint	Twitter	new tab	Add '(opens in new tab)' to text
https://mastodon.social/@linuxmint	Mastodon	new tab	Add '(opens in new tab)' to text
https://www.reddit.com/r/linuxmint/	Reddit	new tab	Add '(opens in new tab)' to text
https://discord.gg/mint	Discord	new tab	Add '(opens in new tab)' to text
https://kiwiirc.com/client/irc.spotchat.…	IRC	new tab	Add '(opens in new tab)' to text
https://mintcast.org	mintCast Podcast	new tab	Add '(opens in new tab)' to text
https://www.eukhost.com/vps-hosting	(empty)	empty	Add link text or aria-label
https://unixshells.com	(empty)	empty	Add link text or aria-label
http://www.fit-pc.com/web/purchase/order…	(empty)	empty	Add link text or aria-label
https://www.datadoghq.com/	(empty)	empty	Add link text or aria-label
https://sucuri.net/	(empty)	empty	Add link text or aria-label
https://linuxmint.thinkpenguin.com/	(empty)	empty	Add link text or aria-label
http://duckduckgo.com/?t=lm	(empty)	empty	Add link text or aria-label
https://www.yahoo.com	(empty)	empty	Add link text or aria-label
https://www.hellotux.com/linux_mint	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://linuxmint-installation-guide.rea…	Installation Guide	new tab	Add '(opens in new tab)' to text
https://linuxmint-user-guide.readthedocs…	User Guide	new tab	Add '(opens in new tab)' to text
https://forums.linuxmint.com	Forums	new tab	Add '(opens in new tab)' to text
https://packages.ubuntu.com	https://packages.ubuntu.com	new tab	Add '(opens in new tab)' to text
https://github.com/linuxmint	https://github.com/linuxmint	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

60 links and buttons have descriptive text

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

/; https://www.eukhost.com/vps-hosting; https://unixshells.com; http://www.fit-pc.com/web/purchase/order-direct-mintbox/; https://www.datadoghq.com/; https://sucuri.net/; https://linuxmint.thinkpenguin.com/; http://duckduckgo.com/?t=lm; https://www.yahoo.com; https://www.hellotux.com/linux_mint (+2 more)

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

Add '(opens in new tab)' to link text or aria-label.

https://app.element.io/#/room/#linuxmint-space:matrix.org; https://www.facebook.com/pages/Linux-Mint/185238108180410; https://www.github.com/linuxmint; https://twitter.com/linux_mint; https://mastodon.social/@linuxmint; https://linuxmint-installation-guide.readthedocs.io/en/latest/; https://blog.linuxmint.com; https://forums.linuxmint.com; https://app.element.io/#/room/#linuxmint-space:matrix.org; https://community.linuxmint.com (+13 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.owl-prev (#427 on page); button.owl-next (#429 on page); button.owl-dot (#432 on page); button.owl-dot (#434 on page); button.owl-dot (#436 on page); button.owl-dot (#438 on page); button.owl-dot (#440 on page); button.owl-dot (#442 on page); button.owl-prev (#529 on page); button.owl-next (#531 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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

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

Print Stylesheet

Action

No print styles

FIX

No print styles

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

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

C

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

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

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

B

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found - Linux Mint ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Lighthouse Accessibility Audits

Action

Score 73/100 — 7 failing, 19 passed

REVIEW

73

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
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-md-12 > div.owl-carousel > div.owl-nav > button.owl-prev `div.col-md-12 > div.owl-carousel > div.owl-nav > button.owl-prev`
div.col-md-12 > div.owl-carousel > div.owl-nav > button.owl-next `div.col-md-12 > div.owl-carousel > div.owl-nav > button.owl-next`

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
nav.navbar > div.container > a.navbar-brand > img `nav.navbar > div.container > a.navbar-brand > img`
div.col-md-3 > div.widget > a.footer-logo > img `div.col-md-3 > div.widget > a.footer-logo > 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
header.navbar-transparent > nav.navbar > div.container > a.navbar-brand `header.navbar-transparent > nav.navbar > div.container > a.navbar-brand`
div.container > div.row > div.col-4 > a `div.container > div.row > div.col-4 > a`
div.container > div.row > div.col-4 > a `div.container > div.row > div.col-4 > a`
div.container > div.row > div.col-4 > a `div.container > div.row > div.col-4 > a`
div.container > div.row > div.col-4 > a `div.container > div.row > div.col-4 > a`
div.row > div.col-md-3 > div.widget > a.footer-logo `div.row > div.col-md-3 > div.widget > a.footer-logo`

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
Features `div.container > div.row > div.col-md-4 > h5.text-primary`
Thu, 16 Apr 2026 `div.post > div.post-info > div.post-time > a`
Monthly News – March 2026 `div.item > div.post > div.post-info > a.post-title`
View all sponsors `section > div.container > div.row > 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
Features `div.container > div.row > div.col-md-4 > h5.text-primary`
Graphic Design `div.row > div.col-md-4 > div.bg-light > h5`
Is it free? `div.container > div.row > div.col-md-3 > h4`
Scott Gilbertson `div.item > div.testimonials-wrap > div.testi-text > h6.mb-0`
Quick Links `div.row > div.col-md-2 > div.widget > h6`

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
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`
div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot `div.col-12 > div.owl-carousel > div.owl-dots > button.owl-dot`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

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

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

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Uses ARIA roles only on compatible elements

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

○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

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

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

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

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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
h2 Linux Mint 22.3	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h2 What is Linux Mint?	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h2 Give it a try. You�…	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h2 Easy to use, fast an…	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h2 Fun, helpful and pas…	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h2 Latest news	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h2 A fantastic communit…	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h2 Partners and sponsor…	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h3 OOTB	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h3 KISS	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h3 Home rule	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h3 Rock solid	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h3 Free and Open Source	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h3 Community-centric	20.29:1	3.0:1	#000000	#FBFBFB	Pass
title Home - Linux Mint	8.26:1	4.5:1	#000000	#57B65E	Pass
a Home	8.33:1	4.5:1	#000000	#54B762	Pass
a Download	8.32:1	4.5:1	#000000	#51B767	Pass
li Latest version	8.44:1	4.5:1	#000000	#52B86E	Pass
a Linux Mint 22.3	8.32:1	4.5:1	#000000	#4DB76F	Pass
span Recommended	8.40:1	4.5:1	#000000	#4AB874	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.