Skip to content
https://wired.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
5
REVIEW
7
PASS
12
INFO
0
Checks
24
12 PASS 7 REVIEW 5 FIX
D
Iframe Accessibility
Action
7/9 iframe(s) missing title; 0 placeholder(s)
FIX
7/9 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://cdn.permutive.app/topics.html")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.google.com/recaptcha/api2/aframe")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://s.amazon-adsystem.com/iu3?cm3ppd=1&d=dtb-pub&csif=t&dl=ox-db5_n-index_n…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://cm.g.doubleclick.net/partnerpixels?url=https%3A%2F%2Fwww.wired.com%2F")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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::
Skip navigation link detected
Info::
8 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 8 <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.
C
Alt Text Quality
Action
31 of 55 images have issues
REVIEW
31 of 55 images have issues
Critical::
31 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
6 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
55 images 18 good alt text 6 decorative 31 missing
IssueCount
missing31 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

C
Tabindex Anti-Patterns
Action
0 positive, 7 -1-on-focusable
REVIEW
0 positive, 7 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="fidesActiveMenuItem">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Mobile-Readable Font Sizes
97% of visible text renders at >= 12 CSS px (7 below threshold)
REVIEW
97% of visible text renders at >= 12 CSS px (7 below threshold)
Info::
7 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <button> 11.0px ("More From WIRED"); <button> 11.0px ("Reviews and Guides"); <p> 11.0px ("2026"); <p> 11.0px ("Condé Nast. All rights reserved."); <em> 11.0px ("WIRED").
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found | WIRED ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 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
Lighthouse Accessibility Audits
Action
Score 76/100 — 7 failing, 24 passed
REVIEW
76

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Navigation Area header.OneNavContainer-kolMaZ > div.OneNavRowGrid-dOvkpA > div.OneNavRowContent-iBmA-dB > div.OneNavAreaContainer-bbElNi

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0__container__ > iframe#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0 > div > button div#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0__container__ > iframe#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0 > div > button

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL
div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL div.MediaAssetWrapper-cXozZc > span.SpanWrapper-kFnjvc > picture.ResponsiveImagePicture-jKunQM > img.ResponsiveImageContainer-dkeESL

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0__container__ > iframe#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0 > div > input div#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0__container__ > iframe#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0 > div > input

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#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0__container__ > iframe#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0 > div > a div#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0__container__ > iframe#google_ads_iframe_3379/conde.wired/hero/homepage/bundle/1_0 > div > 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

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
FACT CHECK div > div.SummaryItemRubricWrapper-iBcwqE > div.RubricWrapper-cQVtQV > a.RubricLink-BwroS
AUTOCOMPLETE INTERVIEW div > div.SummaryItemRubricWrapper-iBcwqE > div.RubricWrapper-cQVtQV > a.RubricLink-BwroS

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SUBSCRIBE div.CTAWrapper-bmUbTy > div.journey-unit__container > div.NavCTALinkContainer-ZsoAz > a.NavCTALink-brNKFz
A New Tool Found Malware That’s Guided by an AI Hive Mind—No Humans in Sight div.SubtopicDiscoveryGridContent-epBBzZ > div.SubtopicDiscoveryItemContainer-euhdUm > div.SubtopicDiscoveryHedContainer-zA-dRC > a.BaseText-fEwdHD
Primetime Exposes the Ego-Driven Core of Vigilante Pedophile Hunting div.SubtopicDiscoveryGridContent-epBBzZ > div.SubtopicDiscoveryItemContainer-euhdUm > div.SubtopicDiscoveryHedContainer-zA-dRC > a.BaseText-fEwdHD
Marvel Has Assigned 42 Hours of Homework Before Avengers: Doomsday div.SubtopicDiscoveryGridContent-epBBzZ > div.SubtopicDiscoveryItemContainer-euhdUm > div.SubtopicDiscoveryHedContainer-zA-dRC > a.BaseText-fEwdHD
Anonymous Men Have Turned Cyberharassment Into a Group Sport—Here’s One Woman’s… div.SubtopicDiscoveryItemContainer-euhdUm > div.SubtopicDiscoveryHedContainer-zA-dRC > div.SubtopicDiscoveryArticleContent-hRZkdp > a.BaseText-fEwdHD
Join WIRED@Night for an Uncanny Valley Live Recording on Women, Tech, and Power div.SubtopicDiscoveryGridContent-epBBzZ > div.SubtopicDiscoveryItemContainer-euhdUm > div.SubtopicDiscoveryHedContainer-zA-dRC > a.BaseText-fEwdHD
○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●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 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
●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.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` 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
○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
○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.
A+
Landmark Structure
17 landmarks
PASS
17 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Navigation Row" MAIN ASIDE CONTENTINFO footer
A
Heading Hierarchy
83 headings, 1 skip(s)
PASS
83 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 WIRED
  • H2 Today’s Picks
  • H2 Trending Stories
  • H3 Meta’s Muse Is Adults-Only. Why Does It Look Like a Kids’ Toy?
  • H3 Old-School Credit Card Scams Are Far From Dead
  • H3 Thieves Stole ‘Nvidia’ Trailers. They Got 20 Tons of Sand
  • H3 The Search for Silicon Valley’s Most Powerful Woman
  • H3 A Gravitational Battle Within the Earth Is Changing the Length of Days
  • H3 This Browser Extension Lets You Snooze Open Tabs Until Later
  • H3 I’ve Been Hunting Deals for 13 Years. These Early Prime Day Discounts Are Actually Worth It
  • H3 Scientists Detect Radio Signals From an Exoplanet for the First Time in History
  • H3 She’s 28, Loves God and Her Family, and Might Be the Reason You Can’t Have Kids
  • H3 AI Agents Teamed Up to Cheat at Blackjack. Their Collusion Is Getting Harder to Spot
  • H3 How to Claim Your Cut of Apple’s $250 Million Siri Settlement
  • H3 I Think I Found an AI Agent Worth the Risk
  • H3 No One Wants to Talk About Women in Tech—So We Will
  • H2 Reviews
  • H3 The Holidays Are Coming—and So Are the White Elephant Parties
  • H3 The Best Mesh Wi-Fi Systems to Achieve Networking Nirvana
  • H3 Quince Luggage Gives Away a Run for Its Money
  • H3 After Testing Hundreds of Laptops, These Are the Best Options I Recommend
  • H2 Subscriber Exclusives
  • H3 War Bros Didn’t Always Rule Silicon Valley
  • H3 I Think I Found an AI Agent Worth the Risk
  • H3 A US-China AI Hotline Won’t Be Ready for a While
  • H3 AI Agents Teamed Up to Cheat at Blackjack. Their Collusion Is Getting Harder to Spot
  • H3 Forget the AI Slowdown—the Vulnerability Explosion Is Already Happening
  • H2 The UK Government Faces a Reckoning Over Palantir
  • H2 AI, Tariffs, Rare Minerals: What to Expect From Trump’s Upcoming Summit With Xi Jinping
  • H2 It’s Donald Trump Versus MAGA on Data Centers
  • H2 An OpenAI Agent Hacked Australia’s Health Service. Their Government Found Out Months Later
  • H2 Meta’s Muse AI Assistant Rolled Out With a Serious Security Flaw
  • H2 A New Tool Found Malware That’s Guided by an AI Hive Mind—No Humans in Sight
  • H2 The Data Center Backlash Should Also Be a Climate Reckoning. It Isn’t Yet
  • H2 Nicotine Is Mounting a Comeback in the Wellness Movement
  • H2 Some Pancreatic Cells Are Just One Genetic Tweak Away From Treating Diabetes
  • H2 Appeals Court Lets the Pentagon Designate Anthropic a Supply-Chain Risk
  • H2 The Trump Administration Is Trying to Get Musk and X Out of a $137 Million EU Fine
  • H2 The Pope’s AI Guy Is Worried About ‘Cartel’ Behavior Among Big Labs
  • H2 You Don’t Need to Pay for Distraction-Blocking Software
  • H2 How to Record Your Screen on Any Phone
  • H2 Nearly a Decade Later, the Electric Tesla Semi Is Here
  • H2 The 34 Very Best Gifts for Dads
  • H2 The 10 Best Coffee Subscriptions of 2026 to Keep You Wired
  • H2 Bose’s Premium Open Earbuds Are $100 Off
  • H2 Party Invite Phishing Scams Are the New Missed Connections
  • H2 Primetime Exposes the Ego-Driven Core of Vigilante Pedophile Hunting
  • H2 SeaWorld Wants to Make You Horny
  • H2 The 8 Best Movies to Stream This Month
  • H2 The 9 Best TV Shows to Stream This Month
  • H2 Marvel Has Assigned 42 Hours of Homework Before Avengers: Doomsday
  • H2 Anonymous Men Have Turned Cyberharassment Into a Group Sport—Here’s One Woman’s Side of the Story
  • H2 Here’s What the AI Apocalypse Could Look Like
  • H2 Join WIRED@Night for an Uncanny Valley Live Recording on Women, Tech, and Power
  • H2 The Big Story
  • H3 Who Killed Paulina Borsook’s Career?
  • H3 Why No One Wants to Date Tech Bros
  • H3 She’s 28, Loves God and Her Family, and Might Be the Reason You Can’t Have Kids
  • H3 Patti Harrison Had Dreams of a Tech Utopia. Silicon Valley Smashed Them
  • H3 Women Still Face Too Much Bullshit—in Silicon Valley and Beyond
  • H2 Special Editions
  • H3 Welcome to the WIRED Women Issue
  • H3 Inside WIRED’s Brain Week
  • H3 The Truth About Kids These Days
  • H3 The Future of Home
  • H2 WIRED Classics
  • H3 Deliver Us, Lord, From the Startup Life
  • H3 A Genetic Curse, a Scared Mom, and the Quest to ‘Fix’ Embryos
  • H3 Two Nations, a Horrible Accident, and the Urgent Need to Understand the Laws of Space
  • H3 Life as a 21st-Century Trucker
  • H3 Google Throws Open Doors to Its Top-Secret Data Center
  • H2 Videos
  • H3 Scientists Detect Radio Signals From Exoplanet for the First Time Ever
  • H3 The Backlash Against Women in Tech Is in Full Swing
  • H3 I Built AI Clones of My Coworkers and Things Got Weird Pretty Quickly
  • H3 Biomedical Scientist Fact Checks Pseudoscience Slop
  • H3 Tech Leaders Attend Trump-Xi Banquet at White House
  • H3 Reckless Ben Answers The Web's Most Searched Questions
  • H3 The Ick Factor: No One Wants to Date Tech Bros
  • H3 Australia Says Rogue OpenAI Agent Hacked Health Service Website
  • H3 Can Bentley's Torcal SUV Break the Curse of the Luxury EV?
  • H3 Psychiatrist Debunks The Biggest Psychopath Myths on Reddit
  • H6 Select international site skipped

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+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
social_mediacheckboxSocial Mediaaria-label
essentialcheckboxEssentialaria-label
sales_sharing_targeted_advertisingcheckboxTargetedaria-label
analyticscheckboxPerformancearia-label
functionalcheckboxFunctionalaria-label
audience_measurementcheckboxAudience Measurementaria-label
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
6 form control(s) checked, no input-semantic issues
PASS
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
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
h1 WIRED21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Today’s Picks21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trending Stories21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The UK Government Fa…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI, Tariffs, Rare Mi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 It’s Donald Trump …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 An OpenAI Agent Hack…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meta’s Muse AI Ass…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A New Tool Found Mal…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Data Center Back…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nicotine Is Mounting…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Some Pancreatic Cell…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Appeals Court Lets t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Trump Administra…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The Pope’s AI Guy …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 You Don’t Need to …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 How to Record Your S…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nearly a Decade Late…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The 34 Very Best Gif…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The 10 Best Coffee S…21.00:13.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.

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

Send Feedback