Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 6 REVIEW 5 FIX

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

11 landmarks

REVIEW

11 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

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

Heading Hierarchy

Action

21 headings, 2 skip(s)

REVIEW

21 headings, 2 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

H1 Homepage Content
H1 Get Planning! These Foods Are So Easy to Grow in Your Garden duplicate H1
H3 by LoveToKnow Editorial skipped
H1 Get Planning! These Foods Are So Easy to Grow in Your Garden duplicate H1
H3 by LoveToKnow Editorial skipped
H2 New & Popular Topics
H2 Top Reads
H2 Life
H2 Life
H2 Parenting
H2 Parenting
H2 Home
H2 Home
H2 Food & Drink
H2 Food & Drink
H2 Celebrations
H2 Celebrations
H2 Quotes & Quips
H2 Quotes & Quips
H2 The Catalog
H2 The Catalog

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

Alt Text Quality

3 of 51 images have issues

REVIEW

3 of 51 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with generic alt text

12 decorative image(s) correctly marked

36 image(s) with good alt text

51 images 36 good alt text 12 decorative 1 generic 2 missing

Issue	Count
missing	2 image(s)
generic	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Form Accessibility

2 of 16 controls have issues

REVIEW

2 of 16 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="text">

14 control(s) properly labeled

16 controls

14 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#q	search	search input	aria-label
input	submit	search button	aria-label
#q	search	search input	aria-label
input	submit	search button	aria-label
#q	search	search input	aria-label
input	submit	search button	aria-label
#home-page-newsletternewsletter-agree	checkbox	I agree to receive email communications from LoveToKnow.com	for/id
#newsletter-footernewsletter-agree	checkbox	I agree to receive email communications from LoveToKnow.com	for/id
#q	search	search input	aria-label
input	submit	search button	aria-label
#q	search	search input	aria-label
input	submit	search button	aria-label
#q	search	search input	aria-label
input	submit	search button	aria-label
input	text	(Type your email here...)	placeholder only
input	email	(Type your email here...)	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

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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, 13 fail WCAG AA

REVIEW

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

7 pass 13 fail WCAG AA 2 pass AA only

h1 Homepage Content

1.66:1

#000000

#333333

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Get Planning! These Foods Are So Easy to…

1.66:1

#000000

#333333

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Get Planning! These Foods Are So Easy to…

1.66:1

#000000

#333333

needs 3.0:1 (large text)

32px · bottom of viewport

h2 New & Popular Topics

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Top Reads

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h3 by LoveToKnow Editorial

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 by LoveToKnow Editorial

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

a Lifestyle

4.37:1

#000000

#3B8132

needs 4.5:1 (normal text)

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

a Wellness

3.67:1

#000000

#5C6B4E

needs 4.5:1 (normal text)

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

a Aging

1.48:1

#000000

#083216

needs 4.5:1 (normal text)

16px · above the fold

a Style

1.25:1

#000000

#112111

needs 4.5:1 (normal text)

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

a Work Life

1.52:1

#000000

#173038

needs 4.5:1 (normal text)

16px · above the fold

a Grief & Loss

1.19:1

#000000

#181914

needs 4.5:1 (normal text)

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

4 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 Homepage Content	1.66:1	3.0:1	#000000	#333333	Fail
h1 Get Planning! These …	1.66:1	3.0:1	#000000	#333333	Fail
h1 Get Planning! These …	1.66:1	3.0:1	#000000	#333333	Fail
h2 New & Popular Topics	1.66:1	3.0:1	#000000	#333333	Fail
h2 Top Reads	1.66:1	3.0:1	#000000	#333333	Fail
h3 by LoveToKnow Editor…	1.66:1	3.0:1	#000000	#333333	Fail
h3 by LoveToKnow Editor…	1.66:1	3.0:1	#000000	#333333	Fail
title LoveToKnow - Live a …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div ALL TOPICS	17.14:1	4.5:1	#000000	#E8E8E8	Pass
div Know	8.54:1	4.5:1	#000000	#77B46F	Pass
a Life	7.58:1	4.5:1	#000000	#67AA75	Pass
a Lifestyle	4.37:1	4.5:1	#000000	#3B8132	Fail
a Relationships	11.30:1	4.5:1	#000000	#DBB895	Pass
a Wellness	3.67:1	4.5:1	#000000	#5C6B4E	Fail
a Aging	1.48:1	4.5:1	#000000	#083216	Fail
a Astrology	5.50:1	4.5:1	#000000	#568F61	Pass
a Style	1.25:1	4.5:1	#000000	#112111	Fail
a Work Life	1.52:1	4.5:1	#000000	#173038	Fail
a Grief & Loss	1.19:1	4.5:1	#000000	#181914	Fail
a Diversity & Inclusio…	6.47:1	4.5:1	#000000	#A28B71	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.

Link & Button Quality

189 links, 9 buttons — all OK

PASS

189 links, 9 buttons — all OK

3 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.facebook.com/LoveToKnow; https://twitter.com/lovetoknow; https://www.pinterest.com/lovetoknow/

186 link(s) with descriptive text

189 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/LoveToKnow	Follow us on Facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/lovetoknow	Follow us on Twitter	new tab	Add '(opens in new tab)' to text
https://www.pinterest.com/lovetoknow/	Follow us on Pinterest	new tab	Add '(opens in new tab)' to text

195 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.facebook.com/LoveToKnow; https://twitter.com/lovetoknow; https://www.pinterest.com/lovetoknow/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 21 passed

PASS

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
by LoveToKnow Editorial `a.hero-link > section.hero-outer-mobile > div > h3`

These are opportunities to improve keyboard navigation in your application.

○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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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 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.

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[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-hidden="true"]` elements do not contain focusable descendents

○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

○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 type="image">` elements have `[alt]` text

○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

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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