Skip to content
https://linux.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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
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::
Search functionality detected
Got: role-search
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
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.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV SEARCH MAIN ASIDE CONTENTINFO (missing!)

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
Form Accessibility
Action
5 of 8 controls have issues
REVIEW
5 of 8 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="s" id="td-header-search-mob">; <input type="button" name="login_button" id="login_button">; <input type="button" name="forgot_button" id="forgot_button">; <input type="text" name="s" id="td-header-search">; <input type="submit" id="td-header-search-top">
Info::
3 control(s) properly labeled
8 controls
3 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#login_emailtextyour usernamefor/id
#login_passpasswordyour passwordfor/id
#forgot_emailtextyour emailfor/id
#login_buttonbutton(none)none
#td-header-search-mobtext(none)none
#forgot_buttonbutton(none)none
#td-header-searchtext(none)none
#td-header-search-topsubmit(none)none

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

<input type="text" name="s" id="td-header-search-mob">; <input type="button" name="login_button" id="login_button">; <input type="button" name="forgot_button" id="forgot_button">; <input type="text" name="s" id="td-header-search">; <input type="submit" id="td-header-search-top">

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 Page not found - Linux.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A
Heading Hierarchy
35 headings, 1 skip(s)
PASS
35 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 Linux.com
  • H3 Linux Foundation Announces OpenSearch Software Foundation to Foster Open Collaboration in Search and Analytics skipped
  • H4 Featured News
  • H3 Celebrating the Second Year of Linux Man-Pages Maintenance Sponsorship
  • H3 How to Deploy Lightweight Language Models on Embedded Linux with LiteLLM
  • H3 Automating Compliance Management with UTMStack’s Open Source SIEM & XDR
  • H3 Using OpenTelemetry and the OTel Collector for Logs, Metrics, and Traces
  • H3 Xen 4.19 is released
  • H3 Advancing Xen on RISC-V: key updates
  • H3 AI Produces Data-driven OpenFOAM Speedup (HPC Wire)
  • H3 Delivering Prime Training Deals – 2 DAYS ONLY
  • H3 Why You Need to Know About Event Modeling:  —An Intro
  • H3 Take the Cloud Native Security Survey
  • H4 Linux Foundation
  • H3 Implementing Secure Zero-Touch Provisioning in AI and Edge Infrastructure
  • H3 From DHCP to SZTP – The Trust Revolution
  • H3 Celebrating the Second Year of Linux Man-Pages Maintenance Sponsorship
  • H3 Disaggregated Routing with SONiC and VPP: Lab Demo and Performance Insights – Part Two
  • H3 Disaggregated Routing with SONiC and VPP: Architecture and Integration – Part One
  • H3 Kubernetes on Bare Metal for Maximum Performance
  • H3 Automating Compliance Management with UTMStack’s Open Source SIEM & XDR
  • H3 A Simple Way to Install Talos Linux on Any Machine, with Any Provider
  • H3 Project Tazama, A Project Hosted by LF Charities With Support From the Gates Foundation,...
  • H3 Linux Foundation Announces OpenSearch Software Foundation to Foster Open Collaboration in Search and Analytics
  • H4 System Administration + Linux Kernel
  • H3 mkfs.ext4 – What it actually creates
  • H3 Pipe and Splice
  • H3 Syscall latency… and some uses of speculative execution
  • H3 sos report – The Swiss Army Knife of Diagnostic Tools
  • H3 Reverse Engineering UndefinedBehaviorSanitizer (UBScan)
  • H3 Network Interface transmission queue timeout, cause and recovery methods
  • H3 Understanding Ext4 Disk Layout, Part 2
  • H3 Introducing OCIFS
  • H3 Introducing bpftune for lightweight, always-on auto-tuning of system behaviour
  • H3 Measuring NVMe Latency

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

A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
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
title Linux.com - News For…7.40:14.5:1
#000000
#FF6C0E
Pass
a Topic7.40:14.5:1
#000000
#FF6C0E
Pass
a AI/ML21.00:14.5:1
#000000
#FFFFFF
Pass
a Cloud21.00:14.5:1
#000000
#FFFFFF
Pass
a Desktop21.00:14.5:1
#000000
#FFFFFF
Pass
a Embedded/IoT21.00:14.5:1
#000000
#FFFFFF
Pass
a Governance21.00:14.5:1
#000000
#FFFFFF
Pass
a Hardware21.00:14.5:1
#000000
#FFFFFF
Pass
a Linux21.00:14.5:1
#000000
#FFFFFF
Pass
a Networking21.00:14.5:1
#000000
#FFFFFF
Pass
a Open Source21.00:14.5:1
#000000
#FFFFFF
Pass
a Security21.00:14.5:1
#000000
#FFFFFF
Pass
a System Administratio…21.00:14.5:1
#000000
#FFFFFF
Pass
a Audience21.00:14.5:1
#000000
#FFFFFF
Pass
a Developers21.00:14.5:1
#000000
#FFFFFF
Pass
a DevOps21.00:14.5:1
#000000
#FFFFFF
Pass
a Enterprise21.00:14.5:1
#000000
#FFFFFF
Pass
a Enthusiast21.00:14.5:1
#000000
#FFFFFF
Pass
a Resources21.00:14.5:1
#000000
#FFFFFF
Pass
a Tutorials21.00:14.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.

A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 21 passed
PASS
90

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
Featured News div.td_block_wrap > div.td-block-title-wrap > h4.td-block-title > span.td-pulldown-size
Linux Foundation div.td_block_wrap > div.td-block-title-wrap > h4.td-block-title > span.td-pulldown-size
System Administration + Linux Kernel div.td_block_wrap > div.td-block-title-wrap > h4.td-block-title > span.td-pulldown-size

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
Trademark Usage div.td-pb-row > div.td-pb-span10 > aside.footer-text-wrap > 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
Linux Foundation Announces OpenSearch Software Foundation to Foster Open Collab… div.td_module_flex_2 > div.td-module-container > div.td-module-meta-info > h3.entry-title

These are opportunities to improve keyboard navigation in your application.

○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
●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 use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
○`[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
○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
○`<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.
○Uses ARIA roles only on compatible elements
○Identical links have the same purpose.
○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.

Send Feedback