Skip to content
https://arstechnica.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 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
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::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 3 <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
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
Heading Hierarchy
50 headings, 2 skip(s)
REVIEW
50 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 We and our partners process data for the following purposes
  • H1 Ars Technica homepage
  • H4 Included stories skipped
  • H4 Most read
  • H4 These settings are only available for Ars Pro subscribers
  • H4 These settings are only available for Ars Pro subscribers
  • H2 New Rowhammer attacks give complete control of machines running Nvidia GPUs
  • H2 Trump proposes steep cut to NASA budget as astronauts head for the Moon
  • H2 Ice Age dice show early Native Americans may have understood probability
  • H2 As Artemis II zooms to the Moon, everything seems to be going swimmingly
  • H2 Elon Musk insists banks working on SpaceX IPO must buy Grok subscriptions
  • H2 Trump proposes steep cut to NASA budget as astronauts head for the Moon
  • H2 Ice Age dice show early Native Americans may have understood probability
  • H2 As Artemis II zooms to the Moon, everything seems to be going swimmingly
  • H2 Elon Musk insists banks working on SpaceX IPO must buy Grok subscriptions
  • H2 “Cognitive surrender” leads AI users to abandon logical thinking, research finds
  • H2 Trump ignores biggest reasons his AI data center buildout is failing
  • H2 OpenClaw gives users yet another reason to be freaked out about security
  • H2 Netflix must refund customers for years of price hikes, Italian court rules
  • H2 EV adoption in America: Who’s winning, who’s losing?
  • H2 OpenAI takes on another “side quest,” buys tech-focused talk show TBPN
  • H2 Launch day has arrived for NASA’s Artemis II mission—here’s what to expect
  • H2 Four astronauts are now inexorably bound for the Moon
  • H2 Perplexity’s “Incognito Mode” is a “sham,” lawsuit says
  • H2 SpaceX tries to convince FCC that Amazon put satellites into wrong altitude
  • H2 Google Vids gets AI upgrade with Veo and Lyria models, directable AI avatars
  • H2 Male octopuses guided through mating by female hormones
  • H2 New fossil deposits show complex animal groups predating the Cambrian
  • H2 Renewables dominate 2025’s newly installed generating capacity
  • H2 Google announces Gemma 4 open AI models, switches to Apache 2.0 license
  • H2 This Ford is the quickest production car at the Nürburgring, ever
  • H2 Anthropic says its leak-focused DMCA effort unintentionally hit legit GitHub forks
  • H2 Why is NASA bothering to go back to the Moon if we’ve already been there?
  • H2 Tesla sales grew by 6% in Q1, but company has an overproduction problem
  • H2 Amazon is trying to buy Globalstar to compete with SpaceX’s Starlink
  • H2 Artemis II, NASA’s boldest mission in generations, launches crew to the Moon
  • H2 Nvidia rolls out its fix for PC gaming’s “compiling shaders” wait times
  • H2 Here’s what that Claude Code source leak reveals about Anthropic’s plans
  • H2 Research roundup: 7 cool science stories we almost missed
  • H2 Did Nazis escape on a UFO? Dev who asked the question just built the official White House app.
  • H2 Musk loves Grok’s “roasts.” Swiss official sues in attempt to neuter them.
  • H2 SpaceX finally files for IPO, targets $1.75 trillion valuation
  • H2 Trump defunding of NPR and PBS blocked by judge, but damage is already done
  • H2 A word from Editor Moonshark about Artemis II
  • H2 Kia shows off small cars in NY: The 2027 EV3 and 2027 Seltos Hybrid
  • H2 LIGO data hints at supernovae so powerful they leave nothing behind
  • H4 Included stories skipped
  • H4 Most read
  • H4 These settings are only available for Ars Pro subscribers
  • H4 These settings are only available for Ars Pro subscribers

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

B
Form Accessibility
2 of 33 controls have issues
REVIEW
2 of 33 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="most_read_category">; <select name="most_read_category">
Info::
31 control(s) properly labeled
33 controls
31 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
pri_c02deb9a-6197-4915-b376-bad31a62cdcacheckboxEssentialaria-label
pri_29ebd463-72cc-403a-99bd-93ca1c4ea83acheckboxFunctional Cookiesaria-label
pri_5ce0b1a5-80c5-40d1-b8ad-751c667393e2checkboxAudience Measurementaria-label
pri_4de8eec0-ef79-417a-be42-22520111d7c8checkboxTargeted Advertisingaria-label
pri_c293c532-40d4-4012-9ec8-64c0d2e80e49checkboxPerformance Cookiesaria-label
pri_2936cc91-a0d0-4927-8394-3e3724bdb36acheckboxSocial Media Cookiesaria-label
1checkboxStore and/or access information on a devicearia-label
2checkboxUse limited data to select advertisingaria-label
3checkboxCreate profiles for personalised advertisingaria-label
4checkboxUse profiles to select personalised advertisingaria-label
5checkboxCreate profiles to personalise contentaria-label
6checkboxUse profiles to select personalised contentaria-label
7checkboxMeasure advertising performancearia-label
8checkboxMeasure content performancearia-label
9checkboxUnderstand audiences through statistics or combinations of data from different sourcesaria-label
10checkboxDevelop and improve servicesaria-label
11checkboxUse limited data to select contentaria-label
1checkboxUse precise geolocation dataaria-label
2checkboxActively scan device characteristics for identificationaria-label
gvl.740checkbox6sensearia-label
gvl.272checkboxA.Mobaria-label
gvl.1271checkboxABCS INSIGHTSaria-label
gvl.259checkboxADYOULIKE (OpenWeb)aria-label
gvl.27checkboxADventoriaria-label
gvl.174checkboxAMAaria-label
gvl.40checkboxActive Agent (Virtual Minds)aria-label
gvl.231checkboxAcuityAdsaria-label
gvl.196checkboxAdElement Media Solutionsaria-label
gvl.57checkboxAdara (Rate Gain)aria-label
#most-read-disabledcheckboxDisable Most Read module throughout the sitefor/id
#most-read-disabledcheckboxDisable Most Read module throughout the sitefor/id
most_read_categoryselect(none)none
most_read_categoryselect(none)none

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

<select name="most_read_category">; <select name="most_read_category">

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

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 Page not found 404 | Ars Technica ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
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
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
h1 Ars Technica homepage
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 We and our partners process data for the…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
button Features
1.22:1
#000000
on
#1A1B1E
needs 4.5:1 (normal text)
16px · above the fold
button Vendors
1.22:1
#000000
on
#1A1B1E
needs 4.5:1 (normal text)
16px · above the fold
button Consent
2.77:1
#000000
on
#5A5254
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button Legitimate interest
1.06:1
#000000
on
#080912
needs 4.5:1 (normal text)
16px · above the fold
div Purposes
1.17:1
#000000
on
#00182B
needs 4.5:1 (normal text)
16px · above the fold
span Essential
1.22:1
#000000
on
#041D2E
needs 4.5:1 (normal text)
16px · above the fold
p This website uses essential cookies and …
1.19:1
#000000
on
#0A1B22
needs 4.5:1 (normal text)
16px · above the fold
span Functional Cookies
1.22:1
#000000
on
#0F1E1A
needs 4.5:1 (normal text)
16px · above the fold
span Off
1.15:1
#000000
on
#0D1619
needs 4.5:1 (normal text)
16px · mid-page
p These cookies enable the website to prov…
1.22:1
#000000
on
#1A1B1E
needs 4.5:1 (normal text)
16px · mid-page
span Audience Measurement
1.22:1
#000000
on
#1A1B1E
needs 4.5:1 (normal text)
16px · mid-page
p We use audience measurement cookies in o…
1.22:1
#000000
on
#1A1B1E
needs 4.5:1 (normal text)
16px · mid-page
span Targeted Advertising
1.22:1
#000000
on
#1A1B1E
needs 4.5:1 (normal text)
16px · mid-page

1 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
h1 Ars Technica homepag…1.00:13.0:1
#000000
#000000
Fail
h2 We and our partners …1.00:13.0:1
#000000
#000000
Fail
title Ars Technica - Servi…9.57:14.5:1
#000000
#AEAFB1
Pass
div About Your Privacy9.57:14.5:1
#000000
#AEAFB1
Pass
div We process your data…9.57:14.5:1
#000000
#AEAFB1
Pass
button Purposes9.57:14.5:1
#000000
#AEAFB1
Pass
button Features1.22:14.5:1
#000000
#1A1B1E
Fail
button Vendors1.22:14.5:1
#000000
#1A1B1E
Fail
div Below, you will find…9.57:14.5:1
#000000
#AEAFB1
Pass
button Consent2.77:14.5:1
#000000
#5A5254
Fail
button Legitimate interest1.06:14.5:1
#000000
#080912
Fail
div Purposes1.17:14.5:1
#000000
#00182B
Fail
span Essential1.22:14.5:1
#000000
#041D2E
Fail
p This website uses es…1.19:14.5:1
#000000
#0A1B22
Fail
span Functional Cookies1.22:14.5:1
#000000
#0F1E1A
Fail
span Off1.15:14.5:1
#000000
#0D1619
Fail
p These cookies enable…1.22:14.5:1
#000000
#1A1B1E
Fail
span Audience Measurement1.22:14.5:1
#000000
#1A1B1E
Fail
p We use audience meas…1.22:14.5:1
#000000
#1A1B1E
Fail
span Targeted Advertising1.22:14.5:1
#000000
#1A1B1E
Fail

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
Alt Text Quality
All 61 images OK
PASS
All 61 images OK
Info::
8 image(s) with alt text over 125 characters
Info::
27 decorative image(s) correctly marked
Info::
26 image(s) with good alt text
61 images 26 good alt text 27 decorative
IssueCount
too long8 image(s)
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 30 passed
PASS
97

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.

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
article#card-2148335 > div.dusk:bg-gray-700 > div.relative > a article#card-2148335 > div.dusk:bg-gray-700 > div.relative > a
article#card-2148621 > div.dusk:bg-gray-700 > div.relative > a article#card-2148621 > div.dusk:bg-gray-700 > div.relative > a
article#card-2148639 > div.dusk:bg-gray-700 > div.relative > a article#card-2148639 > div.dusk:bg-gray-700 > div.relative > a
article#card-2148605 > div.dusk:bg-gray-700 > div.relative > a article#card-2148605 > div.dusk:bg-gray-700 > div.relative > a
article#card-2148587 > div.dusk:bg-gray-700 > div.relative > a article#card-2148587 > div.dusk:bg-gray-700 > div.relative > a
div.dusk:bg-gray-700 > div.flex > div.relative > a div.dusk:bg-gray-700 > div.flex > div.relative > a
article#card-2148522 > div.dusk:bg-gray-700 > div.relative > a article#card-2148522 > div.dusk:bg-gray-700 > div.relative > a
article#card-2148397 > div.dusk:bg-gray-700 > div.relative > a article#card-2148397 > div.dusk:bg-gray-700 > div.relative > a
article#card-2148459 > div.dusk:bg-gray-700 > div.relative > a article#card-2148459 > div.dusk:bg-gray-700 > div.relative > a
div.dusk:bg-gray-700 > div.flex > div.relative > a div.dusk:bg-gray-700 > div.flex > div.relative > a
div.dusk:bg-gray-700 > div.flex > div.relative > a div.dusk:bg-gray-700 > div.flex > div.relative > a
div.dusk:bg-gray-700 > div.flex > div.relative > a div.dusk:bg-gray-700 > div.flex > div.relative > a
div.dusk:bg-gray-700 > div.flex > div.relative > a div.dusk:bg-gray-700 > div.flex > div.relative > a
div.dusk:bg-gray-700 > div.flex > div.relative > a div.dusk:bg-gray-700 > div.flex > div.relative > a
div.dusk:bg-gray-700 > div.flex > div.relative > a div.dusk:bg-gray-700 > div.flex > div.relative > a
div.dusk:bg-gray-700 > div.flex > div.relative > a div.dusk:bg-gray-700 > div.flex > div.relative > a
div.dusk:bg-gray-700 > div.flex > div.relative > a div.dusk:bg-gray-700 > div.flex > div.relative > a
div.mx-auto > div.justify-between > div.site-footer-statement > a div.mx-auto > div.justify-between > div.site-footer-statement > 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.

○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
●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
●`[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
●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.
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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.
○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.
○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