Skip to content
https://runnersworld.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ 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
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: #000000
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
No navigation patterns
FIX
No navigation patterns
Info::
2 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 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
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
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 (missing!) NAV MAIN CONTENTINFO footer

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

Why this matters

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

Learn more ▾

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

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
Heading Hierarchy
Action
111 headings, 1 skip(s)
REVIEW
111 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 ‘I Kept Going’: How the Final Official Finisher of the Boston Marathon Motivated Herself to End Strong
  • H3 How a 2:09 Marathoner Trained Only on a Treadmill
  • H3 These Small Habits Actually Lead to Run Progress
  • H3 Why Your Long Run Matters More Than Weekly Mileage
  • H3 The 8 Best Garmin Running Watches
  • H2 How to Start Running
  • H3 The Runner’s World Guide on How to Start Running
  • H3 Unlock the Benefits of Running
  • H3 Start With Run/Walk Intervals
  • H3 Improve Form, Warmup, and Recover Well
  • H3 Progress Gradually With Safe Habits
  • H3 With Her Olympic Dream on the Line, Sara Hall Found a Superpower She Didn’t Know She Had
  • H3 The Best Cushioned Running Shoes
  • H3 Fast and Flat Boston Qualifying Marathons
  • H3 What to Know About Macronutrients
  • H3 5 Essential Habits I’ve Embraced as I Approach 50
  • H3 Download Your Runner’s World+ Training Plans
  • H2 JOIN US
  • H4 Are you looking to run the best race of your life? skipped
  • H2 Marathon Training
  • H3 How to Pick a Marathon Training Plan That Meets Your Current Fitness—and Why That’s Crucial.
  • H3 How to Avoid Feeling Wiped After Long Runs
  • H3 How I Finally Earned My BQ
  • H3 Experts Debate the 3-Hour Long-Run Rule
  • H3 Mistakes to Avoid When Tweaking Your Training Plan
  • H2 Complete Training Guides
  • H3 Guide to 3-Day-a-Week Training
  • H3 Run Longer: Break New Barriers
  • H3 Your Complete Guide to Conquering 13.1
  • H3 Start Running: The Best Way to Begin
  • H2 Shoe Reviews
  • H3 The Brooks Adrenaline GTS 25 Keeps Your Stride in Check—Gently
  • H3 This Shoe Brand Is Great for Overpronation
  • H3 The Best Shoes for Runners on a Budget
  • H3 Brooks Glycerin Max 2 Review
  • H3 The 6 Best Running Shoes for Beginners in 2026
  • H2 Treadmills
  • H3 8 Best Treadmills
  • H3 Best Amazon Spring Sale Treadmill Deals
  • H3 Urevo Strol 2E Review
  • H3 These 3 Treadmill Workouts Build Run/Walk Speed
  • H2 Running Gear
  • H3 The 10 Best Massage Guns of 2025
  • H3 lululemon Run Times Bra Review
  • H3 Recovery Slides Are The Easiest Step of R&R
  • H3 The Best Basic Running Watches for Minimalists
  • H2 Running Watches
  • H3 The Best Running Watches for Mapping and Pacing
  • H3 Garmin Enduro 3 Review
  • H3 Why My GPS Watch Must Have Maps and Directions
  • H3 The 6 Best Advanced GPS Watches
  • H2 The Amazing Runner’s World Show
  • H3 One Extra Run per Week During Base Training Can Save 3 Minutes in a Marathon
  • H3 Tricks We Play When a Race Gets Tough
  • H3 How to Avoid the Wall and Build Real Endurance
  • H3 How Running Just 3 Miles Preps You for a Marathon
  • H3 The Minimum Half Marathon Weekly Mileage Is Lower Than You Think.
  • H2 Train Smarter. Run Stronger.
  • H2 Health & Injuries
  • H3 Running Injury Red Flags Every Runner Should Know
  • H3 RW Guide to Stretching and Mobility
  • H3 How Your Running Shoes May Affect Your Foot Strike
  • H3 How You Can Treat (and Prevent) Bunions
  • H2 Training
  • H3 How to Chunk Your Long Runs or Races
  • H3 Cole Hocker’s Go-To Cross-Training Method
  • H3 How to Pace the Boston Marathon
  • H3 Why Strength Training Is Crucial for Older Women
  • H2 Nutrition
  • H3 Which Supplements Are Worth Your Money
  • H3 What Exactly Is Matcha and What Are It’s Benefits?
  • H3 How Courtney Dauwalter Fuels Her Miles
  • H3 3 Fueling Mistakes Uncovered by a Glucose Monitor
  • H2 Check Out Our Running Playlists
  • H3 A 90-Minute Playlist for Zone 2 Runs
  • H3 A 90-Minute Playlist to Maintain a Faster Pace
  • H3 A 90-Minute Winter Running Mix
  • H3 A 3-Hour Playlist for Long Runs
  • H2 Beginner
  • H3 How Long Does It Take to Get Ready for a 5K?
  • H3 Ditch the Data for Better Pacing as a Beginner
  • H3 Train to Run One Mile in Eight Easy Weeks
  • H3 5 Pacing Tips Every New Runner Should Know
  • H2 Races
  • H3 2027 Boston Marathon Registration FAQs
  • H3 How to Run Your Best Boston Marathon
  • H3 Professional Pacer Shares the Best Marathon Plan
  • H3 It’s Time to Dial Back Our Boston Marathon Worship
  • H2 Runner's Stories
  • H3 Why—and How—You Should Run Doubles
  • H3 The Story Behind Boston's Heartbreak Hill
  • H3 When Can You Start Calling Yourself a Runner?
  • H3 How I’m Still Running My Best Races at 44
  • H2 Stay in the Know
  • H3 Calli Hauger-Thackery Runs 2:43:58 at Boston
  • H3 Des Linden Finishes 30th at the Boston Marathon
  • H3 Chelsea Clinton Runs 3:40:52 at Boston Marathon
  • H3 Top American Women at 2026 the Boston Marathon
  • H2 The Latest
  • H3 The Final Finisher of the Boston Marathon
  • H3 How a 2:09 Marathoner Trained Only on a Treadmill
  • H3 The Top Americans at the 2026 Boston Marathon
  • H3 Lokedi Wins 2026 Boston Marathon
  • H3 John Korir Wins 2026 Boston Marathon
  • H3 Here Are the Results from the 2026 Boston Marathon
  • H3 How to Watch the 2026 Boston Marathon
  • H3 No, Influencers Aren’t Ruining the Boston Marathon
  • H3 Ashley Paulson Breaks 100-Mile World Record
  • H3 Astronaut Suni Williams Returns to Boston
  • H3 Why The Toughest Hill at Boston Isn’t Heartbreak
  • H3 2026 Boston Marathon Men’s Preview

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

B
Alt Text Quality
5 of 161 images have issues
REVIEW
5 of 161 images have issues
Warning::
5 image(s) with generic alt text
Info::
2 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
152 image(s) with good alt text
161 images 152 good alt text 2 decorative 5 generic
IssueCount
generic5 image(s)
too long2 image(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA 2 pass AA only
h2 JOIN US
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Train Smarter. Run Stronger.
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
a Subscribe
3.87:1
#000000
on
#9D5740
needs 4.5:1 (normal text)
16px · above the fold
a Amazing Runner's World Show
4.29:1
#000000
on
#A75D42
needs 4.5:1 (normal text)
16px · above the fold
a Health - Injuries
1.29:1
#000000
on
#13241A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Nutrition - Weight Loss
1.19:1
#000000
on
#0C1C14
needs 4.5:1 (normal text)
16px · above the fold
a Running Gear
1.36:1
#000000
on
#112921
needs 4.5:1 (normal text)
16px · above the fold
a Beginner
1.40:1
#000000
on
#0E2C24
needs 4.5:1 (normal text)
16px · above the fold
a Advanced
1.36:1
#000000
on
#0C2922
needs 4.5:1 (normal text)
16px · above the fold
a Tools
1.26:1
#000000
on
#04231B
needs 4.5:1 (normal text)
16px · mid-page
a Races - Places
1.39:1
#000000
on
#142A25
needs 4.5:1 (normal text)
16px · mid-page
a News
2.55:1
#000000
on
#4B504C
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Runners' Stories
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Trail Running
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page

2 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 JOIN US1.00:13.0:1
#000000
#000000
Fail
h2 Train Smarter. Run S…1.00:13.0:1
#000000
#000000
Fail
title Runner's World14.08:14.5:1
#000000
#59E7ED
Pass
span Search21.00:14.5:1
#000000
#FFFFFF
Pass
a Newsletter21.00:14.5:1
#000000
#FFFFFF
Pass
a Runner's World+7.37:14.5:1
#000000
#999999
Pass
a Subscribe3.87:14.5:1
#000000
#9D5740
Fail
a My Bookmarks5.59:14.5:1
#000000
#A67A64
Pass
a Amazing Runner's Wor…4.29:14.5:1
#000000
#A75D42
Fail
a Training5.17:14.5:1
#000000
#8E7B65
Pass
a Health - Injuries1.29:14.5:1
#000000
#13241A
Fail
a Nutrition - Weight L…1.19:14.5:1
#000000
#0C1C14
Fail
a Running Gear1.36:14.5:1
#000000
#112921
Fail
a Beginner1.40:14.5:1
#000000
#0E2C24
Fail
a Advanced1.36:14.5:1
#000000
#0C2922
Fail
a Tools1.26:14.5:1
#000000
#04231B
Fail
a Races - Places1.39:14.5:1
#000000
#142A25
Fail
a News2.55:14.5:1
#000000
#4B504C
Fail
a Runners' Stories1.00:14.5:1
#000000
#000000
Fail
a Trail Running1.00:14.5:1
#000000
#000000
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+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#global-nav-search-input-inputtextSearchfor/id
#EmailemailEmail*for/id
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | Runner's World ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 28 passed
PASS
95

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.

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
Are you looking to run the best race of your life? section > div.css-16rytbi > div.css-vn3aqv > h4.css-n8v6xh

These are opportunities to improve keyboard navigation in your application.

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
BOSTON MARATHON a.ee4ms354 > div.css-1ogcqtu > div.css-1sfzy4a > a.css-1o9os3o
MARATHON TRAINING a.ee4ms354 > div.css-b6s0n0 > div.css-11xuo59 > a.css-1o9os3o
RUNNING TIPS a.ee4ms354 > div.css-b6s0n0 > div.css-11xuo59 > a.css-1o9os3o
PRODUCT REVIEWS a.ee4ms354 > div.css-b6s0n0 > div.css-11xuo59 > a.css-1o9os3o

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
●`[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
●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.
●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
●`<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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●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
○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
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback