Skip to content
https://lifehacker.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Alt Text Quality
Action
2 of 41 images have issues
FIX
2 of 41 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
2 image(s) with alt text over 125 characters
Info::
37 image(s) with good alt text
41 images 37 good alt text 2 missing
IssueCount
missing2 image(s)
too long2 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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 ✗
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 | Lifehacker ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 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 Present
✓ Multiple Sizes Present
C
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA 9 pass AA only
h1 Top Stories
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Latest
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Watch Now
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trending Now
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured: The Out-of-Touch Adults’ Gui…
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Deals
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
24px · bottom of viewport
h2 News/Opinions
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hacks
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How-To's
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We Care About Your Privacy
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
24px · bottom of viewport
h3 We and our partners process data to prov…
2.82:1
#000000
on
#555555
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Top Stories2.82:13.0:1
#000000
#555555
Fail
h2 Latest2.82:13.0:1
#000000
#555555
Fail
h2 Watch Now2.82:13.0:1
#000000
#555555
Fail
h2 Trending Now2.82:13.0:1
#000000
#555555
Fail
h2 Featured: The Out-of…2.82:13.0:1
#000000
#555555
Fail
h2 Deals2.82:13.0:1
#000000
#555555
Fail
h2 News/Opinions2.82:13.0:1
#000000
#555555
Fail
h2 Hacks2.82:13.0:1
#000000
#555555
Fail
h2 How-To's2.82:13.0:1
#000000
#555555
Fail
h2 We Care About Your P…2.82:13.0:1
#000000
#555555
Fail
h3 We and our partners …2.82:13.0:1
#000000
#555555
Fail
title Lifehacker | Do ever…5.24:14.5:1
#000000
#7F7F7F
Pass
a Skip to Main Content5.24:14.5:1
#000000
#7F7F7F
Pass
span View our Bluesky Pag…5.24:14.5:1
#000000
#7F7F7F
Pass
span View our Instagram P…4.96:14.5:1
#000000
#7B7B7B
Pass
span View on Facebook Pag…4.96:14.5:1
#000000
#7B7B7B
Pass
span View our Youtube Pag…4.96:14.5:1
#000000
#7B7B7B
Pass
span View our Twitter Pag…4.96:14.5:1
#000000
#7B7B7B
Pass
a Latest4.96:14.5:1
#000000
#7B7B7B
Pass
a Tech4.96:14.5:1
#000000
#7B7B7B
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
14 landmarks
PASS
14 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Social, Newsletter, & Hamburger Links" SEARCH MAIN CONTENTINFO footer
A+
Heading Hierarchy
11 headings
PASS
11 headings
Info::
Single H1 present
  • H1 Top Stories
  • H2 Latest
  • H2 Watch Now
  • H2 Trending Now
  • H2 Featured: The Out-of-Touch Adults’ Guide to Kid Culture
  • H2 Deals
  • H2 News/Opinions
  • H2 Hacks
  • H2 How-To's
  • H2 We Care About Your Privacy
  • H3 We and our partners process data to provide:
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputinputSearch Lifehackeraria-label
#emailemailLifehacker Newsletteraria-label
#g-recaptcha-responsetextarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<textarea name="g-recaptcha-response" id="g-recaptcha-response">

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

A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Lifehacker
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Lifehacker ✓192×192 icon ✓512×512 icon ✗Start URL . ✓Display Mode standalone ✓
Name Lifehacker Display Mode standalone Theme Color #028858 Background Color #FFF Icons 2 icon(s)
A
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 29 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.

Names and labels

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.md:grid-cols-2 > div > a.relative > img.aspect-video div.md:grid-cols-2 > div > a.relative > img.aspect-video
div.md:grid-cols-2 > div > a.relative > img.aspect-video div.md:grid-cols-2 > div > a.relative > img.aspect-video

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-full > div.w-full > form#homepage_newsletter_form > input div.w-full > div.w-full > form#homepage_newsletter_form > input

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SEE MORE div.mt-6 > div.mx-auto > div.flex > a.custom-gradient-text
SEE MORE section.relative > div.mt-12 > div.flex > a.custom-gradient-text
SEE MORE div.flex > div.flex-1 > div.flex > a.custom-gradient-text
SEE MORE div.flex > div.flex-1 > div.flex > a.custom-gradient-text
SEE MORE section.relative > div.mt-12 > div.flex > a.custom-gradient-text
SEE MORE section.relative > div.mt-12 > div.flex > a.custom-gradient-text
SEE MORE section.relative > div.mt-12 > div.flex > a.custom-gradient-text
SEE MORE section.relative > div.mt-12 > div.flex > a.custom-gradient-text
About Ziff Davis (Opens in a new tab) div.w-full > ul.grid > li.md:mr-4 > a.text-sm
Our Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●`<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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○`<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.
○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.
○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