Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 2 REVIEW 6 FIX

404 Error Page

Action

HTTP 429, custom page

FIX

HTTP 429, custom page

Unexpected status code: HTTP 429

Expected HTTP 404 but received 429. This may confuse search engine crawlers.

Got: HTTP 429

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 429 ✗Page Title Blocked due to excessive requests [LWN.net] ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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 ✗

Landmark Structure

Action

1 landmarks

REVIEW

1 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

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

Form Accessibility

Action

3 of 5 controls have issues

REVIEW

3 of 5 controls have issues

3 control(s) without accessible label

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

Got: <input type="submit" name="submit">; <input type="submit" name="submit">; <input type="submit" name="submit">

2 control(s) properly labeled

5 controls

2 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
#uc	text	User:	none
#pc	password	Password:	none
submit	submit	(none)	none
submit	submit	(none)	none
submit	submit	(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

A+

Heading Hierarchy

21 headings

PASS

21 headings

Single H1 present

H1 Welcome to LWN.net
H2 [$] Using LLMs to find Python C-extension bugs
H2 [$] Digging into drama at The Document Foundation
H2 [$] A more efficient implementation of Shor's algorithm
H2 [$] The 7.0 scheduler regression that wasn't
H2 [$] The first half of the 7.1 merge window
H2 [$] LWN.net Weekly Edition for April 16, 2026
H2 [$] Forking Vim to avoid LLM-generated code
H2 [$] Tagging music with MusicBrainz Picard
H2 [$] Development statistics for the 7.0 kernel
H2 [$] A build system aimed at license compliance
H2 Fedora Verified: a proposal to recognize Fedora contributor status
H2 Firefox 150 released
H2 Security updates for Tuesday
H2 Git 2.54.0 released
H2 Arch Linux now has a reproducible container image
H2 Debian Project Leader Election 2026 results
H2 Security updates for Monday
H2 Seven stable kernels for Saturday
H2 Security updates for Friday
H2 Rust 1.95.0 released

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

Link & Button Quality

1 issue(s) across 110 links and 3 buttons

PASS

1 issue(s) across 110 links and 3 buttons

1 link(s) with no accessible text

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

Got: a (#12 on page)

109 link(s) with descriptive text

110 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label

112 links and buttons have descriptive text

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

a (#12 on page)

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

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
h1 Welcome to LWN.net	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] Using LLMs to find…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] Digging into drama…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] A more efficient i…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] The 7.0 scheduler …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] The first half of …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] LWN.net Weekly Edi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] Forking Vim to avo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] Tagging music with…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] Development statis…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ] A build system aim…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Fedora Verified: a p…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Firefox 150 released	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Security updates for…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Git 2.54.0 released	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Arch Linux now has a…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Debian Project Leade…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Security updates for…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Seven stable kernels…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Security updates for…	21.00:1	3.0: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 100/100 — 0 failing, 20 passed

PASS

100

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.

○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

●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

●Background and foreground colors have a sufficient contrast ratio

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

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

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