Skip to content
https://theringer.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <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
7 headings
REVIEW
7 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 The Latest
  • H3 Noteworthy Reads
  • H3 Noteworthy Reads
  • H2 La Gata a True Crime Podcast
  • H2 The NBA Playoffs Are Here
  • H2 Great Reads
  • H3 Archive

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
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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA 3 pass AA only
h2 The Latest
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 La Gata
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The NBA Playoffs Are Here
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Great Reads
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Noteworthy Reads
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Noteworthy Reads
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Archive
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
span Discover
4.33:1
#000000
on
#846F41
needs 4.5:1 (normal text)
16px · top of page (header area)
a Videos
2.16:1
#000000
on
#633B0E
needs 4.5:1 (normal text)
16px · above the fold
a Podcasts
1.62:1
#000000
on
#492A0F
needs 4.5:1 (normal text)
16px · above the fold
a The Latest
1.58:1
#000000
on
#482713
needs 4.5:1 (normal text)
16px · above the fold
a The Latest
4.27:1
#000000
on
#866C50
needs 4.5:1 (normal text)
16px · above the fold
a Todd McShay Big Board
3.88:1
#000000
on
#78684B
needs 4.5:1 (normal text)
16px · above the fold
a Todd McShay Big Board
3.35:1
#000000
on
#6E5E45
needs 4.5:1 (normal text)
16px · above the fold
a NBA
2.75:1
#000000
on
#75464F
needs 4.5:1 (normal text)
16px · above the fold
a NBA
2.24:1
#000000
on
#6A364B
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 The Latest1.00:13.0:1
#000000
#000000
Fail
h2 La Gata1.00:13.0:1
#000000
#000000
Fail
h2 The NBA Playoffs Are…1.00:13.0:1
#000000
#000000
Fail
h2 Great Reads1.00:13.0:1
#000000
#000000
Fail
h3 Noteworthy Reads1.00:13.0:1
#000000
#000000
Fail
h3 Noteworthy Reads1.00:13.0:1
#000000
#000000
Fail
h3 Archive1.00:13.0:1
#000000
#000000
Fail
title The Ringer4.51:14.5:1
#000000
#88714A
Pass
span Discover4.33:14.5:1
#000000
#846F41
Fail
span anything6.73:14.5:1
#000000
#A39063
Pass
span Discover6.97:14.5:1
#000000
#AB9164
Pass
span anything8.36:14.5:1
#000000
#B4A182
Pass
a Videos2.16:14.5:1
#000000
#633B0E
Fail
a Podcasts1.62:14.5:1
#000000
#492A0F
Fail
a The Latest1.58:14.5:1
#000000
#482713
Fail
a The Latest4.27:14.5:1
#000000
#866C50
Fail
a Todd McShay Big Boar…3.88:14.5:1
#000000
#78684B
Fail
a Todd McShay Big Boar…3.35:14.5:1
#000000
#6E5E45
Fail
a NBA2.75:14.5:1
#000000
#75464F
Fail
a NBA2.24:14.5:1
#000000
#6A364B
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, 24 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.

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.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8 div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8
div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8 div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8
div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8 div.ui-w-full > div.max-lg:ui-bg-white/20 > div.ui-flex > button.ui-size-8
article.ui-flex-col > a > div.ui-relative > button.ui-inline-flex article.ui-flex-col > a > div.ui-relative > button.ui-inline-flex
div.ui-flex > div.ui-relative > div.ui-absolute > button.ui-flex div.ui-flex > div.ui-relative > div.ui-absolute > button.ui-flex

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.ui-relative > div.ui-flex-col > div.ui-mb-4 > a.ui-inline-flex div.ui-relative > div.ui-flex-col > div.ui-mb-4 > a.ui-inline-flex
div#swiper-wrapper-776fb8a63d282e94 > div.swiper-slide > div.ui-bg-black > a.ui-absolute div#swiper-wrapper-776fb8a63d282e94 > div.swiper-slide > div.ui-bg-black > a.ui-absolute
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex
main.main-grid > section.col-span-full > div.mb-4 > a.ui-inline-flex main.main-grid > section.col-span-full > div.mb-4 > a.ui-inline-flex
article.ui-flex > div > div.ui-relative > a.ui-inline-flex article.ui-flex > div > div.ui-relative > a.ui-inline-flex
article.ui-flex > div > div.ui-relative > a.ui-inline-flex article.ui-flex > div > div.ui-relative > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex
div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex
div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex
div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex
div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex div.md:max-h-[27.5rem] > article.ui-flex > div.ui-my-auto > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex div.ui-relative > div.-ui-mx-6 > div.ui-flex > a.ui-inline-flex
div.gap-large > div.w-full > div.flex > a.ui-inline-flex div.gap-large > div.w-full > div.flex > a.ui-inline-flex

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.

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
Who’s Going First? section.col-span-full > div.mb-4 > p.motion-safe:ui-transition-colors > span.motion-safe:ui-transition-colors
a True Crime Podcast div.w-full > div.flex > h2.text-heading-sm-medium > span.text-black/30

These are opportunities to improve the legibility of your content.

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
NFL Draft article.ui-flex > div.ui-flex > div.ui-flex > a.ui-rounded-5xl

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
Discover div#__next > header#main-header > div.relative > button
○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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●Elements use only permitted ARIA attributes
●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
○`[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
○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
○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.
○Identical links have the same purpose.
○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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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

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

A+
Alt Text Quality
All 199 images OK
PASS
All 199 images OK
Info::
199 decorative image(s) correctly marked
199 images 199 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="EMAIL">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
EMAILemail(Your email)placeholder only

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

<input type="email" name="EMAIL">

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

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

Send Feedback