Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 1 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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.

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.

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 ✗

Link & Button Quality

1 issue(s) across 81 links and 2 buttons

REVIEW

1 issue(s) across 81 links and 2 buttons

1 link(s) with no accessible text

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

Got: a#main-content

6 link(s) open in new tab without warning

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

Got: https://slashdotmedia.com/privacy-statement/; https://slashdotmedia.com/terms-of-use/; https://slashdotmedia.com/privacy-statement/; https://slashdotmedia.com/privacy-statement/#rightsToKnow; https://privacyportal.onetrust.com/webform/611e70e2-1994-43ff-b07b-646df870db…; https://privacyportal-cdn.onetrust.com/dsarwebform/611e70e2-1994-43ff-b07b-64…

74 link(s) with descriptive text

81 links

1 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://slashdotmedia.com/privacy-statem…	PRIVACY POLICY	new tab	Add '(opens in new tab)' to text
https://slashdotmedia.com/terms-of-use/	TERMS OF SERVICE	new tab	Add '(opens in new tab)' to text
https://slashdotmedia.com/privacy-statem…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://slashdotmedia.com/privacy-statem…	U.S. State Privacy Policy	new tab	Add '(opens in new tab)' to text
https://privacyportal.onetrust.com/webfo…	use this form	new tab	Add '(opens in new tab)' to text
https://privacyportal-cdn.onetrust.com/d…	NON-COOKIE PI OPT-OUT FORM	new tab	Add '(opens in new tab)' to text

76 links and buttons have descriptive text

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

a#main-content

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://slashdotmedia.com/privacy-statement/; https://slashdotmedia.com/terms-of-use/; https://slashdotmedia.com/privacy-statement/; https://slashdotmedia.com/privacy-statement/#rightsToKnow; https://privacyportal.onetrust.com/webform/611e70e2-1994-43ff-b07b-646df870db…; https://privacyportal-cdn.onetrust.com/dsarwebform/611e70e2-1994-43ff-b07b-64…

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

A+

Landmark Structure

12 landmarks

PASS

12 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

12 headings

PASS

12 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)
H2 Search
H2 Breaking News
H2 Archinstall 4.2 Shifts to Wayland-First Profiles, Leaving X.Org Behind
H2 OpenClaw in 2026: What It Is, Who’s Using It, and Whether Your Business Should Adopt It
H2 Linux Kernel Developers Adopt New Fuzzing Tools
H2 GNOME 50 Reaches Arch Linux: A Leaner, Wayland-Only Future Arrives
H2 MX Linux Pushes Back Against Age Verification: A Stand for Privacy and Open Source Principles
H2 LibreOffice Drives Europe’s Open Source Shift: A Growing Push for Digital Sovereignty
H2 Footer Menu Column 2
H2 Footer Menu Column 3
H2 YOUR PRIVACY CHOICES (DO NOT SELL/SHARE/TARGET)

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 11 images OK

PASS

All 11 images OK

11 image(s) with good alt text

11 images 11 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) without accessible label

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

Got: <input type="checkbox" id="opt-toggle">

1 control(s) properly labeled

2 controls

1 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#edit-keys	search	Search	for/id
#opt-toggle	checkbox	(none)	none

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

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

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found | Linux Journal ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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 Search	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Breaking News	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Footer Menu Column 2	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Footer Menu Column 3	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 YOUR PRIVACY CHOICES…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
title Home \| Linux Journal	16.98:1	4.5:1	#000000	#E7E7E7	Pass
a Skip to main content	12.42:1	4.5:1	#000000	#66E066	Pass
span Toggle navigation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Topics+	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cloud	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Containers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Desktop	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Kernel	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Mobile	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Networking	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Privacy	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Programming	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Security	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Servers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a SysAdmin	21.00:1	4.5:1	#000000	#FFFFFF	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.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 26 passed

PASS

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
I DO NOT ACCEPT `div.cmpboxbtns > span#cmpwelcomebtnno > a.cmpboxbtn > span#cmpbntnotxt`
I ACCEPT `div.cmpboxbtns > span#cmpwelcomebtnyes > a.cmpboxbtn > span#cmpbntyestxt`

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
PRIVACY POLICY `div.field > ul#terms-nav > li > a`
TERMS OF SERVICE `div.field > ul#terms-nav > li > a`
ADVERTISE `div.field > ul#terms-nav > li > a`
PRIVACY CHOICES `div.field > ul#terms-nav > li > 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

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

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

●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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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