Skip to content
https://lifehack.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
D
Heading Hierarchy
Action
18 headings, 3 skip(s)
FIX
18 headings, 3 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 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (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.
  • H1 Achieve Goals That Matter, In Time That You Control.
  • H2 Chart your Roadmap to Success
  • H2 Get Focused Daily Action Plans
  • H5 AI COACH:9:00 AM MORNING CALL skipped
  • H3 Join LifeHack Today
  • H2 Bust Through Mental Roadblocks
  • H2 Level Up Your Expertise
  • H5 AI COACH: skipped
  • H3 Ready For A Transformation?
  • H4 Curious About Your Hidden Potential?
  • H2 Explore Our Free Tools and Ignite Your Growth
  • H3 Insight Awaits You
  • H4 What we do
  • H2 A Path to Progress Without Compromising Time-Life Harmony
  • H2 Get a Sneak Peek: Our Best Advice
  • H4 What Experts Say About Us skipped
  • H2 Let’s Transform Your Time
  • H1 Achieve Goals That Matter, In Time You Can Control duplicate H1

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

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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 - LifeHack ✓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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 4 pass AA only
title LifeHack - Get the most out of life. Fas…
3.77:1
#000000
on
#686868
needs 4.5:1 (normal text)
16px · top of page (header area)
span 🎯 Find Your Perfect Goals
3.77:1
#000000
on
#686868
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Achieve Goals That M…12.44:13.0:1
#000000
#DCC682
Pass
h2 Get Focused Daily Ac…12.44:13.0:1
#000000
#DCC682
Pass
title LifeHack - Get the m…3.77:14.5:1
#000000
#686868
Fail
span 🎯 Find Your Perfe…3.77:14.5:1
#000000
#686868
Fail
a Get My Plan →6.84:14.5:1
#000000
#7D9992
Pass
a Skip to content6.84:14.5:1
#000000
#7D9992
Pass
span Menu6.84:14.5:1
#000000
#7D9992
Pass
span Menu6.84:14.5:1
#000000
#7D9992
Pass
a Start Here16.98:14.5:1
#000000
#E7E7E7
Pass
a The Time/Life Assess…9.57:14.5:1
#000000
#9DB4AE
Pass
a The Time Flow System21.00:14.5:1
#000000
#FFFFFF
Pass
a Time Flow in Motion21.00:14.5:1
#000000
#FFFFFF
Pass
a Mastering Your Time21.00:14.5:1
#000000
#FFFFFF
Pass
a Resources21.00:14.5:1
#000000
#FFFFFF
Pass
a Procrastination21.00:14.5:1
#000000
#FFFFFF
Pass
a Focus21.00:14.5:1
#000000
#FFFFFF
Pass
a Distraction21.00:14.5:1
#000000
#FFFFFF
Pass
a Prioritization21.00:14.5:1
#000000
#FFFFFF
Pass
a Planning & Schedulin…21.00:14.5:1
#000000
#FFFFFF
Pass
a Delegation18.59:14.5:1
#000000
#F1F1F1
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
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <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 "Mobile Toggle" MAIN ASIDE 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 34 images OK
PASS
All 34 images OK
Info::
34 image(s) with good alt text
34 images 34 good alt text
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" id="email">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#emailemail(Enter your email address here...)placeholder only

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

<input type="email" id="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

A+
Lighthouse Accessibility Audits
Score 96/100 — 2 failing, 29 passed
PASS
96

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
Settings div.cmpboxbtns > span#cmpwelcomebtncustom > a.cmpboxbtn > span#cmpbntcustomtxt
Get My Plan → div.flex > div.flex-1 > div.flex > a.bg-[#EBCC5E]
Get My Custom Goal Plan div.gb-inside-container > div.gb-button-wrapper > a.gb-button > strong
Sarah, let’s figure how to help you feel more fulfilled both as a leader and a … div.gb-inside-container > p.gb-headline > em > mark.has-inline-color
Sarah p.gb-headline > em > mark.has-inline-color > strong
leader and a parent p.gb-headline > em > mark.has-inline-color > strong
Here’s my recommended 3-month blueprint for you: p.gb-headline > em > mark.has-inline-color > strong
AI COACH: div.gb-inside-container > h5.gb-headline > mark.has-inline-color > strong
9:00 AM MORNING CALL div.gb-container > div.gb-inside-container > h5.gb-headline > mark.has-inline-color
I’ve planned 3 easy actions for you today to help you move the needle. div.gb-inside-container > p.gb-headline > em > mark.has-inline-color
3 easy actions p.gb-headline > em > mark.has-inline-color > strong
Try these! div.gb-inside-container > p.gb-headline > em > mark.has-inline-color
confidence div.gb-container > div.gb-inside-container > p.gb-headline > a
Start Achieving Your Goals → div.gb-inside-container > div.gb-button-wrapper > a.gb-button > strong
Do you need more help, Sarah p.gb-headline > em > mark.has-inline-color > strong
Let me give you some personalized actions strategies to try this week. div.gb-inside-container > p.gb-headline > em > mark.has-inline-color
online courses p.gb-headline > mark.has-inline-color > strong > a
AI COACH: div.gb-inside-container > h5.gb-headline > mark.has-inline-color > strong
Sarah, review this lesson this week. p.gb-headline > em > mark.has-inline-color > strong
Let’s break down where your time sinks are really coming from. div.gb-inside-container > p.gb-headline > em > mark.has-inline-color
Start Your Journey → div.gb-inside-container > div.gb-button-wrapper > a.gb-button > strong
Start Your Journey → div.gb-inside-container > div.gb-button-wrapper > a.gb-button > strong
Subscribe for Free Weekly Insights div.bg-[#2A6354] > div.max-w-[800px] > form.cta-form > button.text-white

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
AI COACH: 9:00 AM MORNING CALL div.gb-grid-column > div.gb-container > div.gb-inside-container > h5.gb-headline
AI COACH: div.gb-grid-column > div.gb-container > div.gb-inside-container > h5.gb-headline
WHAT EXPERTS SAY ABOUT US div.gb-grid-column > div.gb-container > div.gb-inside-container > h4.gb-headline

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>`
●`[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.
●`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
●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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○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.
○`<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