Skip to content
https://gentoo.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
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
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: #54487a
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
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)
1 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
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
Warning::
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
BANNER header NAV 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

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

C
Heading Hierarchy
Action
15 headings
REVIEW
15 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 (empty)
  • H2 The Gentoo Big Forum Upgrade (Apr 2, 2026)
  • H2 (empty)
  • H2 Gentoo GNU/Hurd (Apr 1, 2026)
  • H2 Developer blogs live from Planet Gentoo
  • H2 Security advisories from our Security database
  • H2 New packages at the Gentoo packages database
  • H2 Fresh documentation on the Gentoo wiki
  • H3 Questions or comments?
  • H3 Home
  • H3 Get Started
  • H3 Downloads
  • H3 Inside Gentoo
  • H3 Support
  • H3 Get Involved

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

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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Gentoo Linux — Error 404 (Not Found) ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
span gentoo.org sites
2.45:1
#000000
on
#504575
needs 4.5:1 (normal text)
16px · top of page (header area)
a gentoo.org
1.96:1
#000000
on
#2F3D62
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Wiki
1.28:1
#000000
on
#0B2037
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Bugs
1.48:1
#000000
on
#432124
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Packages
1.16:1
#000000
on
#041820
needs 4.5:1 (normal text)
16px · above the fold
a Forums
1.56:1
#000000
on
#172F51
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Developer blogs20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Security advisories20.12:13.0:1
#000000
#FAFAFA
Pass
h2 New packages20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Fresh documentation20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Questions or comment…20.12:13.0:1
#000000
#FAFAFA
Pass
title Welcome – Gentoo L…13.84:14.5:1
#000000
#D3CFE6
Pass
strong Get Gentoo!15.31:13.0:1
#000000
#DDDAEC
Pass
span gentoo.org sites2.45:14.5:1
#000000
#504575
Fail
a gentoo.org1.96:14.5:1
#000000
#2F3D62
Fail
a Wiki1.28:14.5:1
#000000
#0B2037
Fail
a Bugs1.48:14.5:1
#000000
#432124
Fail
a Packages1.16:14.5:1
#000000
#041820
Fail
a Forums1.56:14.5:1
#000000
#172F51
Fail
a Planet8.26:14.5:1
#000000
#9AA3B2
Pass
a Archives20.12:14.5:1
#000000
#FAFAFA
Pass
a Devmanual20.12:14.5:1
#000000
#FAFAFA
Pass
a Gitweb20.12:14.5:1
#000000
#FAFAFA
Pass
a Infra status20.12:14.5:1
#000000
#FAFAFA
Pass
span Toggle navigation20.12:14.5:1
#000000
#FAFAFA
Pass
a Home20.12:14.5:1
#000000
#FAFAFA
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 16 passed
REVIEW
82

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
(Apr 2, 2026) section#news > article.newsitem > h2.stick-top > small
(Apr 1, 2026) section#news > article.newsitem > h2.stick-top > small
All news items div.row > div.col-md-12 > div.news-more > a.btn
live from Planet Gentoo div.row > div.col-xs-12 > h2 > small
from our Security database div.row > div.col-xs-12 > h2 > small
normal tbody > tr > td.text-right > span.label
normal tbody > tr > td.text-right > span.label
low tbody > tr > td.text-right > span.label
high tbody > tr > td.text-right > span.label
high tbody > tr > td.text-right > span.label
at the Gentoo packages database div.row > div.col-xs-12 > h2 > small
on the Gentoo wiki div.row > div.col-xs-12 > h2 > small

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
not Discourse div.newsitem-content > ul > li > a
GNU Hurd article.newsitem > div.newsitem-content > p > a
crack team article.newsitem > div.newsitem-content > p > a

These are opportunities to improve the legibility of your content.

Names and labels

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.site-title-buttons > div.btn-group > div.btn-group > a.btn
div.col-md-12 > div.row > div.col-xs-12 > a div.col-md-12 > div.row > div.col-xs-12 > 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

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GLSA 202604-04 DTrace: Arbitrary file creation via dtprobed normal GLSA 202604-… div.col-md-12 > div.row > div.col-xs-12 > table.table
○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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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.
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○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
○`<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.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
A+
Alt Text Quality
All 7 images OK
PASS
All 7 images OK
Info::
1 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
7 images 6 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback