Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 5 REVIEW 7 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Heading Hierarchy

Action

16 headings, 3 skip(s)

FIX

16 headings, 3 skip(s)

Multiple H1 headings (4 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H1 → H5 (missing H2)

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

Heading level skipped: H1 → H5 (missing H2)

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

H1 Popular Today
H2 Join Our Newsletter
H4 Explore Trending skipped
H1 Discover Events duplicate H1
H5 BCC Membership 2021 skipped
H5 Tidal Basin Run membership
H5 2026 PVTC membership
H5 Muddy Princess - Charlotte, NC
H5 Event Promotions List 2025
H5 2026 Center of the Nation Series - Day 6 (MT)
H5 Lantern Semiquincentennial
H5 FACILITY PRO 24th - 29th May 2026
H1 Discover Articles duplicate H1
H1 Latest duplicate H1
H5 Follow ACTIVE skipped
H5 Mobile Apps

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

Action

15 issue(s) across 63 links and 15 buttons

FIX

15 issue(s) across 63 links and 15 buttons

5 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /; https://www.facebook.com/Activecom; https://twitter.com/active; https://pinterest.com/activecom/boards; https://instagram.com/activedotcom

10 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button[data-testid="mobile-navbar-icon"]; button.featured-card__open-button (#130 on page); button.featured-card__open-button (#165 on page); button.featured-card__open-button (#192 on page); button.featured-card__open-button (#219 on page); button.featured-card__open-button (#682 on page); button.featured-card__open-button (#710 on page); button.featured-card__open-button (#739 on page); button.featured-card__open-button (#767 on page); button.featured-card__open-button (#795 on page)

58 link(s) with descriptive text

63 links

5 empty

0 generic text

0 new tab

10 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/Activecom	(empty)	empty	Add link text or aria-label
https://twitter.com/active	(empty)	empty	Add link text or aria-label
https://pinterest.com/activecom/boards	(empty)	empty	Add link text or aria-label
https://instagram.com/activedotcom	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

63 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/; https://www.facebook.com/Activecom; https://twitter.com/active; https://pinterest.com/activecom/boards; https://instagram.com/activedotcom

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Icon-only buttons need an aria-label so screen readers can announce them.

button[data-testid="mobile-navbar-icon"]; button.featured-card__open-button (#130 on page); button.featured-card__open-button (#165 on page); button.featured-card__open-button (#192 on page); button.featured-card__open-button (#219 on page); button.featured-card__open-button (#682 on page); button.featured-card__open-button (#710 on page); button.featured-card__open-button (#739 on page); button.featured-card__open-button (#767 on page); button.featured-card__open-button (#795 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="email">; <input type="email">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
input	email	(Enter your email)	placeholder only
input	email	(Enter your email)	placeholder only

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title We're unable to find the page you're looking for. ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

8 icon(s) detected

REVIEW

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 6 fail WCAG AA

REVIEW

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

14 pass 6 fail WCAG AA 10 pass AA only

h1 Popular Today

1.81:1

#000000

#333A3D

needs 3.0:1 (large text)

32px · above the fold · over background image/gradient

a Ironman 70.3

2.85:1

#000000

#46595D

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Mud run

2.67:1

#000000

#455459

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Avid 4

3.45:1

#000000

#596469

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a 10K

3.10:1

#000000

#525D61

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Mountain Biking

3.97:1

#000000

#616E70

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

6 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)

Element	Ratio	Required	FG	BG	Result
h1 Popular Today	1.81:1	3.0:1	#000000	#333A3D	Fail
h1 Discover Events	3.14:1	3.0:1	#000000	#5C5C5C	Pass
h1 Discover Articles	3.14:1	3.0:1	#000000	#5C5C5C	Pass
h1 Latest	3.14:1	3.0:1	#000000	#5C5C5C	Pass
h2 Join Our Newsletter	3.14:1	3.0:1	#000000	#5C5C5C	Pass
title Find & Register for …	6.57:1	4.5:1	#000000	#859299	Pass
div Do Something Today	6.01:1	4.5:1	#000000	#7B8C92	Pass
span Everywhere	6.20:1	4.5:1	#000000	#7A8F96	Pass
div Explore events, arti…	6.03:1	4.5:1	#000000	#7C8C93	Pass
span Search	5.65:1	4.5:1	#000000	#74888E	Pass
span Trending	5.15:1	4.5:1	#000000	#6E8186	Pass
a Ironman 70.3	2.85:1	4.5:1	#000000	#46595D	Fail
a Mud run	2.67:1	4.5:1	#000000	#455459	Fail
a Avid 4	3.45:1	4.5:1	#000000	#596469	Fail
a 10K	3.10:1	4.5:1	#000000	#525D61	Fail
a Mountain Biking	3.97:1	4.5:1	#000000	#616E70	Fail
div Apr 23, 2026	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div 2026-04-23T00:00:00-…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div The Cove at the Lake…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Little Elm, TX	21.00:1	4.5: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.

Lighthouse Accessibility Audits

Action

Score 78/100 — 6 failing, 24 passed

REVIEW

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.col-2 > div.nav__mobile-container > div.nav__icon-mobile-container > button.nav__icon-mobile-black `div.col-2 > div.nav__mobile-container > div.nav__icon-mobile-container > button.nav__icon-mobile-black`
div.popular-today__card-wrapper > a.featured-card > div.featured-card__footer > button.featured-card__open-button `div.popular-today__card-wrapper > a.featured-card > div.featured-card__footer > button.featured-card__open-button`
div.popular-today__card-wrapper > a.featured-card > div.featured-card__footer > button.featured-card__open-button `div.popular-today__card-wrapper > a.featured-card > div.featured-card__footer > button.featured-card__open-button`
div.popular-today__card-wrapper > a.featured-card > div.featured-card__footer > button.featured-card__open-button `div.popular-today__card-wrapper > a.featured-card > div.featured-card__footer > button.featured-card__open-button`
div.popular-today__card-wrapper > a.featured-card > div.featured-card__footer > button.featured-card__open-button `div.popular-today__card-wrapper > a.featured-card > div.featured-card__footer > button.featured-card__open-button`
div.newsletter-banner > div.body-fat-email-input > div.input-group > button.btn `div.newsletter-banner > div.body-fat-email-input > div.input-group > button.btn`
div.newsletter__subscription > div.body-fat-email-input > div.input-group > button.btn `div.newsletter__subscription > div.body-fat-email-input > div.input-group > button.btn`
div.popular-trending-articles__wrapper--card-wrapppr-top > a.featured-card > div.featured-card__footer > button.featured-card__open-button `div.popular-trending-articles__wrapper--card-wrapppr-top > a.featured-card > div.featured-card__footer > button.featured-card__open-button`
div.popular-trending-articles__wrapper--card-wrapppr-top > a.featured-card > div.featured-card__footer > button.featured-card__open-button `div.popular-trending-articles__wrapper--card-wrapppr-top > a.featured-card > div.featured-card__footer > button.featured-card__open-button`
div.popular-trending-articles__wrapper--card-wrapppr-bottom > a.featured-card > div.featured-card__footer > button.featured-card__open-button `div.popular-trending-articles__wrapper--card-wrapppr-bottom > a.featured-card > div.featured-card__footer > button.featured-card__open-button`
div.popular-trending-articles__wrapper--card-wrapppr-bottom > a.featured-card > div.featured-card__footer > button.featured-card__open-button `div.popular-trending-articles__wrapper--card-wrapppr-bottom > a.featured-card > div.featured-card__footer > button.featured-card__open-button`
div.popular-trending-articles__wrapper--card-wrapppr-bottom > a.featured-card > div.featured-card__footer > button.featured-card__open-button `div.popular-trending-articles__wrapper--card-wrapppr-bottom > a.featured-card > div.featured-card__footer > button.featured-card__open-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.pw-ad-scroll-container > div.pw-ad-container-logo > a > img `div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img`
div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img `div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img`
div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img `div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img`
div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img `div.pw-ad-scroll-container > div.pw-ad-container-logo > a > img`

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 > div.navbar > div.col-2 > a.logo `div > div.navbar > div.col-2 > a.logo`
div#lead1 > div.pw-ad-scroll-container > div.pw-ad-container-logo > a `div#lead1 > div.pw-ad-scroll-container > div.pw-ad-container-logo > a`
div#lead2 > div.pw-ad-scroll-container > div.pw-ad-container-logo > a `div#lead2 > div.pw-ad-scroll-container > div.pw-ad-container-logo > a`
div#lead3 > div.pw-ad-scroll-container > div.pw-ad-container-logo > a `div#lead3 > div.pw-ad-scroll-container > div.pw-ad-container-logo > a`
div#lead4 > div.pw-ad-scroll-container > div.pw-ad-container-logo > a `div#lead4 > div.pw-ad-scroll-container > div.pw-ad-container-logo > a`
div.container > ul.follow-links > li > a `div.container > ul.follow-links > li > a`
div.container > ul.follow-links > li > a `div.container > ul.follow-links > li > a`
div.container > ul.follow-links > li > a `div.container > ul.follow-links > li > a`
div.container > ul.follow-links > li > a `div.container > ul.follow-links > li > 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.

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
26.2 `div.trending-list > a#trending-type-marathon > div.trending-list__type-logo > label.trending-list__type-label`
13.1 `div.trending-list > a#trending-type-half-marathon > div.trending-list__type-logo > label.trending-list__type-label`
10K `div.trending-list > a#trending-type-10k > div.trending-list__type-logo > label.trending-list__type-label`
5K `div.trending-list > a#trending-type-5k > div.trending-list__type-logo > label.trending-list__type-label`
Reject All `div#onetrust-button-group-parent > div#onetrust-button-group > div.onetrust-banner-options > button#onetrust-reject-all-handler`
Accept Cookies `div#onetrust-button-group-parent > div#onetrust-button-group > div.onetrust-banner-options > button#onetrust-accept-btn-handler`

These are opportunities to improve the legibility of your content.

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
Explore Trending `div.homepage > div.homepage__container > div.homepage__explore-trending-section > h4.homepage__explore-trending-section__heading`
BCC Membership 2021 `a.link > div.event-card__content > div.event-card__main > h5.event-card__title`
Follow ACTIVE `footer > div.mobile-footer > div.container > h5.title`

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

●Form elements have associated labels

●`button`, `link`, and `menuitem` elements have accessible names

●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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○Links are distinguishable without relying on color.

○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+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 decorative image(s) correctly marked

1 images 1 decorative

All images have appropriate alt text.

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