Skip to content
https://rollingstone.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
8
REVIEW
6
PASS
10
INFO
0
Checks
24
10 PASS 6 REVIEW 8 FIX
D
Form Accessibility
Action
4 of 6 controls have issues
FIX
4 of 6 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="small_search_form">; <input type="text" name="q" id="small_search_form">
Info::
2 control(s) properly labeled
6 controls
2 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#EmailAddress-1emailEnter Your Emailfor/id
#EmailAddress-2emailEmail Addressfor/id
#small_search_formtext(Search)placeholder only
#small_search_formtext(Search)placeholder only
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">

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

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q" id="small_search_form">; <input type="text" name="q" id="small_search_form">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

D
Tabindex Anti-Patterns
Action
0 positive, 22 -1-on-focusable
FIX
0 positive, 22 -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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
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.)
D
Iframe Accessibility
Action
9/10 iframe(s) missing title; 0 placeholder(s)
FIX
9/10 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="javascript:false")
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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…")
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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…")
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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…")
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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…")
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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…")
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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…")
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://vx.rollingstone.com/checkout/template/cacheableShow.html?aid=nm2OCspCpu…")
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="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.
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
5 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <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::
5 <nav> landmark(s) found
Warning::
2 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #pagetop
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
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

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

C
Mobile-Readable Font Sizes
Action
89% of visible text renders at >= 12 CSS px (10 below threshold)
REVIEW
89% of visible text renders at >= 12 CSS px (10 below threshold)
Warning::
10 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: <li> 11.0px ("By"); <a> 11.0px ("Jon Blistein"); <li> 11.0px ("By"); <a> 11.0px ("Emily Zemler"); <li> 11.0px ("By").
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 – Rolling Stone ✓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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA
title Rolling Stone – Music, Film, TV and Po…
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

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
h2 Rolling Stone21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Reports21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Most Popular21.00:13.0:1
#000000
#FFFFFF
Pass
h2 You might also like21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The 100 Greatest Pun…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Best New Music: Beyo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Geese Remind Us Why …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Rosario Dawson Confi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Perez Hilton Hospita…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 David Ellison Says H…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Brad Pitt Is Alleged…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Method Man Drops Lim…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ‘Wandering Trees…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The Best Online Stor…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Inside the Noah Wyle…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 No ‘Mo Romo? Not S…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Follow Us21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Newsletter Signup21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Got a Hot News Tip?21.00:13.0:1
#000000
#FFFFFF
Pass
title Rolling Stone – Mu…3.66:14.5:1
#000000
#666666
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 25 passed
REVIEW
85

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
Click here div#main-wrapper > div#pmc-reg-rd-overlay-banner > div.message > a
Cliquez ici div#pmc-reg-rd-overlay-banner > div.message > span.u-symbol > a
List of Partners (vendors) div.ot-dpd-container > div.ot-dpd-content > p.ot-dpd-desc > button.ot-link-btn

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header-links-secondary-inner > div#piano-header-mobile-subscribe-button > div.tp-container-inner > iframe#offer_d884501c7a6b6d8756a5-0 div.header-links-secondary-inner > div#piano-header-mobile-subscribe-button > div.tp-container-inner > iframe#offer_d884501c7a6b6d8756a5-0
div.footer-button-list > div#pmc-piano-footer-sub-button > div.tp-container-inner > iframe#offer_8097f47fb233bffd4cde-0 div.footer-button-list > div#pmc-piano-footer-sub-button > div.tp-container-inner > iframe#offer_8097f47fb233bffd4cde-0

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.

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
Amy Helm Allegedly Caused $2 Million in Damages to Levon Helm Studios, Lawsuit … div.story > div > div.lrv-a-span2 > h3#c-title-amy-helm-levon-studio-lawsuit-1235606741

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
America’s Toughest Workout Isn’t In A Gym — It’s On The Street By JASON MOTLAGH section#story-featured-quote > div.story > div.// > ul.lrv-a-unstyle-list
‘Wandering Trees’ Review: Iconoclastic Director Salvatore Mereu Tries a Newly M… div.lrv-a-wrapper > div.lrv-a-span2 > section.newswire > ul.lrv-a-unstyle-list

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
‘Wandering Trees’ Review: Iconoclastic Director Salvatore Mereu Tries a Newly M… ul.lrv-a-unstyle-list > div.flickity-viewport > div.flickity-slider > li.js-Flickity-cell

These are opportunities to improve the experience of reading tabular or list data using 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
●`[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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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 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
○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.
A
Heading Hierarchy
61 headings, 1 skip(s)
PASS
61 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 .RS-logo-filigree-cls-1{fill:#e60019}.RS-logo-filigree-cls-2{fill:#fff}.RS-logo-filigree-cls-3{fill:#929497}.RS-logo-filigree-cls-4{fill:#e60019}.RS-logo-filigree-cls-5{fill:#231f20} Rollingstone Log
  • H3 Amy Helm Allegedly Caused $2 Million in Damages to Levon Helm Studios, Lawsuit Claims skipped
  • H3 Is ‘Tony’ a True Story? Sort Of
  • H3 Why Was It So Hard for Sam Cooke’s Grandkids to Drop a Soul Album?
  • H3 Biggie’s Manager Wins Legal Battle Against Faith Evans Over Rapper’s Catalog Cash
  • H3 A True-Crime Producer Posed as an Heiress — Then Allegedly Stole $30 Million
  • H3 Charli XCX Sang With the Strokes? Cool
  • H3 ZZ Top Drummer Frank Beard Facing Health Issues After Show Cancellation
  • H3 The 100 Greatest Punk Albums of All Time
  • H3 Best New Music: Beyoncé and Jay-Z, Karol G, More
  • H3 Geese Remind Us Why Real Bands Matter
  • H3 Rosario Dawson Confirms Her Cameo Was Cut From ‘Spider-Man: Brand New Day’
  • H3 Rosario Dawson Confirms Her Cameo Was Cut From 'Spider-Man: Brand New Day'
  • H3 Jason Sudeikis Joins Mumford and Sons Onstage to Sing ‘Ted Lasso’ Theme Song
  • H3 Jenna Ortega Reveals the Surprising Fact Behind Sabrina Carpenter's 'Taste' Video
  • H3 Tiffany Haddish Pleads Guilty to Driving Under the Influence, Gets 12 Months of Probation
  • H3 Rod Stewart Undergoes Successful Heart Procedure, Cancels Tour Dates to Recover
  • H3 John Oliver Begins His Slap-Happy Stint on the Soap Opera 'Days of Our Lives'
  • H3 What Exactly Is Going on With the Outrage Over Fauci and Miscarriages?
  • H3 Gracie Abrams Built a Career on Honesty. She’s Going Even Deeper Now
  • H3 The 100 Greatest Guitar Solos of All Time
  • H3 The 500 Greatest Songs of All Time
  • H3 Zohran Mamdani: ‘If You Aren’t Willing to Fight, You Will Never Win’
  • H3 Trump Is Turning D.C. Into a Theme Park for the American Century
  • H3 Shania Twain: ‘People Know I’m Inclusive’
  • H3 Inside the Desperate Search for Nolan Wells
  • H3 Rolling Stone Travel Awards 2026: Best Hotels, Resorts, Getaways, Gear
  • H3 Noah Continues Love Affair With Seventies and Eighties Rock With INXS Merch Drop
  • H3 Rick Ross on New Book, NA Spirits, and Exercising With a Joint and Luc Belaire
  • H3 Taylor Stitch’s Grateful Dead Collection Is a Throwback to the Band’s Formative Years
  • H3 Molly Shannon and Ashley Padilla Talk ‘SNL’ and Shinola’s Gilda Radner-Inspired Collection
  • H3 America’s Toughest Workout Isn’t in a Gym — It’s on the Street
  • H2 Rolling Stone
  • H2 Reports
  • H3 The Bookie at the Center of the Ohtani Betting Scandal Is Ready to Talk
  • H3 Inside the Battle Over ‘Napalm Girl’
  • H3 He Stole George Jones’ Widow’s Heart. Then He Allegedly Stole Her Millions
  • H3 My Best Friend’s Murder Was a Tabloid Circus. Now, I’m Looking for the Truth
  • H3 More News
  • H3 John Oliver Begins His Slap-Happy Stint on the Soap Opera 'Days of Our Lives'
  • H3 What Exactly Is Going on With the Outrage Over Fauci and Miscarriages?
  • H3 ‘The Office’ U.K. Star Lucy Davis Reveals ‘Incurable’ Cancer Diagnosis
  • H3 50 Years Ago Today: The Ramones Took on the Punk Skeptics at Their West Coast Debut
  • H3 Kennedy Center to Cover $250,000 Legal Fees of Jazz Musician Who Protested Trump Takeover
  • H3 All the Artists Who Don’t Want Donald Trump Using Their Music
  • H2 Most Popular
  • H3 Perez Hilton Hospitalized After Appearing to Harm Himself on Livestream
  • H3 David Ellison Says He’ll Pull Paramount Out of California Starting Oct. 1 if States Refuse to Negotiate Settlement in Antitrust Suit
  • H3 Brad Pitt Is Allegedly 'Bracing Himself' For His Kids' Next Move Which Sources Say Is His 'Worst Possible Nightmare'
  • H3 Method Man Drops Limited-Edition Hat Collection with TWNTY-TWO and TICAL Athletics
  • H2 You might also like
  • H3 ‘Wandering Trees’ Review: Iconoclastic Director Salvatore Mereu Tries a Newly Minted Fairyale, but Only Fitfully Finds Magic
  • H3 The Best Online Stores for Back-to-School Shopping for Teens This Year
  • H3 Inside the Noah Wyle and Shawn Hatosy Relationship That Anchors ‘The Pitt’ Season 2
  • H3 No ‘Mo Romo? Not So Fast, Says CBS Sports
  • H4 Rolling Stone
  • H4 Legal
  • H3 Follow Us
  • H3 Newsletter Signup
  • H3 Got a Hot News Tip?
  • H4 Our Sites

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
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H1: 200 chars - H3: 132 chars - H3: 124 chars
Got: 3 >120-char heading(s)
A
Alt Text Quality
All 34 images OK
PASS
All 34 images OK
Info::
10 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
22 image(s) with good alt text
34 images 22 good alt text 2 decorative
IssueCount
too long10 image(s)
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
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+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback