Skip to content
https://sheknows.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Heading Hierarchy
Action
67 headings, 4 skip(s)
FIX
67 headings, 4 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 SheKnows
  • H2 optional screen reader
  • H2 optional screen reader
  • H1 SheKnows duplicate H1
  • H2 The New Home Economics
  • H2 When Everyone in the House Is Hormonal: Navigating Menopause While Raising Teens
  • H2 Here’s Why Teens Want to Join the U.S. Military Right Now (Yes, Now)
  • H2 Trending Stories
  • H3 Sydney Sweeney Went Nude For Euphoria. It's Exactly What Gen Z Fans Didn't Ask For.
  • H3 Patrick Muldoon's Cause Of Death Revealed
  • H3 How to Watch Euphoria Season 3 for Free
  • H3 The Reason Barron Trump 'Lays Low'
  • H2 Latest News
  • H3 Why Gen Z Can’t Get Enough Of Clowns
  • H3 15 Best Mother’s Day Gifts for Sporty Moms, From Ultra-Comfy Running Shoes to Recovery Essentials
  • H3 Here’s The Exact Time ENHYPEN ‘Blood Saga’ Presale Tickets Go Live *Today* For U.S. Tour Dates
  • H3 Here’s Your Sneak Peek of Crumbl’s New Limited-Edition Mother’s Day Bundle
  • H3 What Do Moms Really Want for Mother’s Day? (Hint: Not Flowers)
  • H3 See Photos Of Michael Jackson’s 3 Kids, Prince, Paris & Bigi Jackson Through The Years
  • H2 Shopping
  • H3 65 Genius Mother’s Day Gift Ideas for Literally Every Kind of Mom in Your Life
  • H3 Bath & Body Works’ Stunning Limited-Edition Vera Bradley Collab Is the Ultimate Mother’s Day Gift
  • H3 These Are the Cutest Graduation Dresses for Class of 2026 (So Far) & Where To Buy Them
  • H2 How I Outsmarted Life360: A Teen’s Guide to (Temporarily) Reclaiming Freedom
  • H2 Health
  • H3 How the CEO of a Contraceptive Company Talked to Her Teen About Sex
  • H3 If You’re Emotionally Exhausted From Your Relationship, It Might Be Marriage Burnout
  • H3 The CDC’s Controversial Vaccine Guidelines Got Struck Down in Court. What Does It Mean For Your Family?
  • H2 Parenting
  • H3 What Do Moms Really Want for Mother’s Day? (Hint: Not Flowers)
  • H3 When Everyone in the House Is Hormonal: Navigating Menopause While Raising Teens
  • H3 Here’s Why Teens Want to Join the U.S. Military Right Now (Yes, Now)
  • H2 Living
  • H3 Found: A Tory Burch Bag That Looks So Similar to Chanel’s Iconic Vanity Case (& It’s 30% Off)
  • H3 Missed Out on the Zendaya x On Drop? Here’s Where We Found Her Limited-Edition Ballet Sneakers Still in Stock
  • H3 Parke x Target Is on the Way — Here Are Parke’s Most Iconic Collabs So Far (& What’s Still in Stock)
  • H2 Watch
  • H3 Teens at a Table: How Gen Z Really Feels About Curfews, Location Tracking & Gaining Independence
  • H2 (empty)
  • H3 100+ Baby Names Beginning With the Letter “D” That Are Darling & Daring
  • H3 100+ Cute & Creative Baby Names Beginning With ‘C’
  • H3 90+ Baby Names Beginning With ‘B’ That Are Beautiful & Brilliant
  • H3 100+ Amazingly Adorable Baby Names Beginning With ‘A’
  • H3 Radiant Baby Names Beginning With ‘R’ For Your Little Rascal
  • H3 Quintessential Baby Names Beginning With ‘Q’ for Your New Cutie
  • H3 Practically Perfect ‘P’ Baby Names For Your Precious New Addition
  • H3 Outstanding & Original Baby Names Beginning With ‘O’
  • H3 Noteworthy Baby Names Beginning With ‘N’ For Your Noble Newborn
  • H3 60+ Elegant & Effortless ‘E’ Names Every Baby Will Enjoy
  • H2 Find the perfect baby name!
  • H2 Newswire
  • H3 The Truth to Rumors Robert Irwin Allegedly Snubbed Harry & Meghan & if He Has ‘Ill Will’ Toward the Sussexes
  • H3 A ‘Michael’ Sequel? A Thriller of a Proposition for Biopic Filmmakers
  • H2 optional screen reader
  • H4 SheKnows skipped
  • H3 Connect with us
  • H2 optional screen reader
  • H4 Legal skipped
  • H3 Newsletter Signup
  • H2 optional screen reader
  • H4 SheKnows Family: skipped
  • H2 optional screen reader
  • H4 Our Sites skipped
  • H3 Follow Us
  • H3 Alerts & Newsletters
  • H2 optional screen reader
  • H3 Stay Informed and Inspired: Subscribe to Our Newsletter

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 ▾

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 ▾

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 ▾

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Form Accessibility
Action
9 of 12 controls have issues
FIX
9 of 12 controls have issues
Critical::
4 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">; <input type="submit">; <input type="submit">
Warning::
5 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">; <input type="text" name="q" id="small_search_form">; <input type="text" name="q" id="small_search_form">; <input type="text">
Info::
3 control(s) properly labeled
12 controls
3 labeled
5 placeholder only
4 unlabeled
ControlTypeLabelMethod
#EmailAddressemailYour Emailfor/id
#EmailAddressemailYour Emailfor/id
inputtextnone
#small_search_formtext(Search)placeholder only
#small_search_formtext(Search)placeholder only
#small_search_formtext(Search)placeholder only
inputtext(Email Address)placeholder only
#small_search_formtext(Search)placeholder only
inputsubmit(none)none
inputsubmit(none)none
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">; <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">; <input type="text" name="q" id="small_search_form">; <input type="text" name="q" id="small_search_form">; <input type="text">

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
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::
9 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 9 <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.
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 – SheKnows ✓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
A
Landmark Structure
14 landmarks
PASS
14 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
5 of 9 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
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

A+
Alt Text Quality
All 43 images OK
PASS
All 43 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
6 decorative image(s) correctly marked
Info::
35 image(s) with good alt text
43 images 35 good alt text 6 decorative
IssueCount
too long2 image(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 optional screen read…10.59:13.0:1
#000000
#B8B8B8
Pass
h2 optional screen read…10.59:13.0:1
#000000
#B8B8B8
Pass
h2 Trending Stories10.59:13.0:1
#000000
#B8B8B8
Pass
h2 Latest News10.59:13.0:1
#000000
#B8B8B8
Pass
h2 Shopping10.59:13.0:1
#000000
#B8B8B8
Pass
h2 Watch10.59:13.0:1
#000000
#B8B8B8
Pass
h2 Newswire10.59:13.0:1
#000000
#B8B8B8
Pass
h2 optional screen read…10.59:13.0:1
#000000
#B8B8B8
Pass
h2 optional screen read…10.59:13.0:1
#000000
#B8B8B8
Pass
h2 optional screen read…10.59:13.0:1
#000000
#B8B8B8
Pass
h2 optional screen read…10.59:13.0:1
#000000
#B8B8B8
Pass
h2 optional screen read…10.59:13.0:1
#000000
#B8B8B8
Pass
h3 The Truth to Rumors …10.59:13.0:1
#000000
#B8B8B8
Pass
h3 A ‘Michael’ Sequ…10.59:13.0:1
#000000
#B8B8B8
Pass
h3 Connect with us10.59:13.0:1
#000000
#B8B8B8
Pass
h3 Newsletter Signup10.59:13.0:1
#000000
#B8B8B8
Pass
h3 Follow Us10.59:13.0:1
#000000
#B8B8B8
Pass
h3 Alerts & Newsletters10.59:13.0:1
#000000
#B8B8B8
Pass
h3 Stay Informed and In…10.59:13.0:1
#000000
#B8B8B8
Pass
title SheKnows – All Thi…10.59:14.5:1
#000000
#B8B8B8
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.

A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 24 passed
PASS
91

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
Stay Informed and Inspired: Subscribe to Our Newsletter div.aI8fZlpv > div._6Tt4x1jq > div._1U8keQ4i > h3._8O9Z-ltD

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
SHEKNOWS div.lrv-u-flex@desktop > div.lrv-u-padding-a-1 > nav.o-nav > h4#sheknows-footer
LEGAL div.lrv-u-flex@desktop > div.lrv-u-border-color-grey-light > nav.o-nav > h4#sheknows-footer-legal
SHEKNOWS FAMILY: footer.footer > div.lrv-u-background-color-brand-accent-dark > nav.o-nav > h4#sheknows-family
OUR SITES div.lrv-u-flex > div.lrv-u-margin-l-auto@tablet > nav.o-nav > h4#pmc-footer

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
TV & MOVIES article.o-card > div.o-card__content > span.c-span > a.c-span__link
ENTERTAINMENT NEWS article.o-card > div.o-card__content > span.c-span > a.c-span__link
CULTURE article.o-card > div.o-card__content > span.c-span > a.c-span__link
SHOPPING GUIDES article.o-card > div.o-card__content > span.c-span > a.c-span__link
BOOKS & MUSIC article.o-card > div.o-card__content > span.c-span > a.c-span__link
FOOD NEWS article.o-card > div.o-card__content > span.c-span > a.c-span__link
PARENTING NEWS article.o-card > div.o-card__content > span.c-span > a.c-span__link
CELEBRITIES article.o-card > div.o-card__content > span.c-span > a.c-span__link
div.lrv-u-text-align-center > div.expandable-menu-search > form.search-form > input div.lrv-u-text-align-center > div.expandable-menu-search > form.search-form > input

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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
●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
●Skip links are focusable.
●Document has a main landmark.
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○`[role]` values are valid
○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
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback