Skip to content
https://www.theverge.com

Accessibility

· 22 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
5
REVIEW
6
PASS
11
INFO
0
Checks
22
11 PASS 6 REVIEW 5 FIX
D
Mobile-Readable Font Sizes
Action
51% of visible text renders at >= 12 CSS px (99 below threshold)
FIX
51% of visible text renders at >= 12 CSS px (99 below threshold)
Warning::
99 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: <span> 11.0px ("Skip to main content"); <a> 11.0px ("Subscribe"); <span> 11.0px ("Andrew Webster"); <time> 11.0px ("May 8"); <span> 11.0px ("89").
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::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Heading Hierarchy
14 headings
REVIEW
14 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 The latest Quick Posts
  • H2 The incredible rising price of everything / The Switch 2 is the latest hardware to get hit by global price hikes. Is there a ceiling?
  • H2 Musk v. Altman: Week 2 / Drama and revelations from the biggest trial in the AI world.
  • H2 Most Popular
  • H2 Tiny tech / An ode to miniature gadgets that still pack a punch.
  • H2 Who wants a robot friend? / The only things these robots are trying to take over is our hearts.
  • H2 Most Discussed
  • H2 Your feed is overrun with clips — this is the cutthroat community of “clippers” behind it
  • H2 Latest from Tech
  • H2 Latest from Reviews
  • H2 Latest from AI
  • H2 Latest from Policy
  • H2 Latest from Science
  • H2 Latest from Entertainment

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 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
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 RSS ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Most Popular
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Most Discussed
1.13:1
#000000
on
#131313
needs 3.0:1 (large text)
24px · bottom of viewport
title The Verge
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · top of page (header area)
span Skip to main content
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · top of page (header area)
a Subscribe
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · top of page (header area)
span Sign In
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · top of page (header area)
span Tech
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · above the fold
span Reviews
1.12:1
#000000
on
#121212
needs 4.5:1 (normal text)
16px · above the fold
span Science
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold
span Entertainment
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold
span Policy
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold
a Subscribe
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold
div Navigation Drawer
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold
a Login
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold
a Sign Up
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · above the fold
span close
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · mid-page
label Search
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · mid-page
button Tech
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · mid-page
a Amazon
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · mid-page
a Apple
1.13:1
#000000
on
#131313
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Most Popular1.13:13.0:1
#000000
#131313
Fail
h2 Most Discussed1.13:13.0:1
#000000
#131313
Fail
title The Verge1.13:14.5:1
#000000
#131313
Fail
span Skip to main content1.13:14.5:1
#000000
#131313
Fail
a Subscribe1.12:14.5:1
#000000
#121212
Fail
span Sign In1.12:14.5:1
#000000
#121212
Fail
span Tech1.12:14.5:1
#000000
#121212
Fail
span Reviews1.12:14.5:1
#000000
#121212
Fail
span Science1.13:14.5:1
#000000
#131313
Fail
span Entertainment1.13:14.5:1
#000000
#131313
Fail
span Policy1.13:14.5:1
#000000
#131313
Fail
a Subscribe1.13:14.5:1
#000000
#131313
Fail
div Navigation Drawer1.13:14.5:1
#000000
#131313
Fail
a Login1.13:14.5:1
#000000
#131313
Fail
a Sign Up1.13:14.5:1
#000000
#131313
Fail
span close1.13:14.5:1
#000000
#131313
Fail
label Search1.13:14.5:1
#000000
#131313
Fail
button Tech1.13:14.5:1
#000000
#131313
Fail
a Amazon1.13:14.5:1
#000000
#131313
Fail
a Apple1.13:14.5:1
#000000
#131313
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+
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
2 <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 "Top Navigation" MAIN CONTENTINFO footer
A+
Alt Text Quality
All 153 images OK
PASS
All 153 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
152 image(s) with good alt text
153 images 152 good alt text
IssueCount
too long1 image(s)
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#:Rkqgr96:textSearchfor/id
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "query" should use type="search" (currently type="text")
Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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.)
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
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.
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 28 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.

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
Cookie Settings div._1twvhsd0 > ul._1twvhsd1 > li._1twvhsd2 > button#ot-sdk-btn
Cookie Policy div._1twvhsd0 > ul._1twvhsd1 > li._1twvhsd2 > a._1twvhsd3
Platform Status div._1twvhsd0 > ul._1twvhsd1 > li._1twvhsd2 > a._1twvhsd3

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