Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 2 REVIEW 6 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email">

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

1 navigation landmark(s) detected

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 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Mobile-Readable Font Sizes

Action

87% of visible text renders at >= 12 CSS px (13 below threshold)

REVIEW

87% of visible text renders at >= 12 CSS px (13 below threshold)

13 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.0px ("Made for everyday life"); <span> 11.0px ("curated picks"); <span> 10.0px ("Home & Living"); <button> 10.0px ("Add to cart"); <span> 10.0px ("−53%").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title ProfitToLife — Products for a Better Life ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

16 headings, 1 skip(s)

PASS

16 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Products for a Better Life.
H2 Shop by category
H2 Trending Now
H3 Desk Organizer Kit (sample)
H3 Winning Products Playbook (sample)
H3 Noise-cancelling headphones (recommended)
H2 Why ProfitToLife?
H3 Curated picks
H3 Smart value
H3 Real-world useful
H3 Honest money
H2 Questions, answered
H2 Get the week's best products.
H4 Explore skipped
H4 Categories
H4 Legal

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

A+

Heading Text Quality

All 16 heading(s) have substantive, well-formed text

PASS

All 16 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	input	Search products	aria-label
q	input	Search products	aria-label
input	email	Your email	aria-label

Link & Button Quality

1 issue(s) across 40 links and 4 buttons

PASS

1 issue(s) across 40 links and 4 buttons

1 link(s) with no accessible text

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

Got: /p/kit-organizador-escritorio

1 link(s) open in new tab without warning

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

Got: https://www.amazon.com/

38 link(s) with descriptive text

40 links

1 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/p/kit-organizador-escritorio	(empty)	empty	Add link text or aria-label
https://www.amazon.com/	View	new tab	Add '(opens in new tab)' to text

42 links and buttons have descriptive text

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

/p/kit-organizador-escritorio

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

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

https://www.amazon.com/

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

Form Input Types

2 input(s) using type=text where a specific type would help

PASS

2 input(s) using type=text where a specific type would help

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "q" should use type="search" (currently type="text")

Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

Tabindex Anti-Patterns

0 positive, 3 -1-on-focusable

PASS

0 positive, 3 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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)

Element	Ratio	Required	FG	BG	Result
h1 Products for a	18.60:1	3.0:1	#000000	#F7F1DF	Pass
h2 Shop by category	17.81:1	3.0:1	#000000	#EAEDEB	Pass
h2 Trending Now	17.74:1	3.0:1	#000000	#E8EDEB	Pass
h2 Why ProfitToLife?	17.74:1	3.0:1	#000000	#E8EDEB	Pass
h2 Questions, answered	17.74:1	3.0:1	#000000	#E8EDEB	Pass
h2 Get the week's best …	17.74:1	3.0:1	#000000	#E8EDEB	Pass
h3 Curated picks	17.74:1	3.0:1	#000000	#E8EDEB	Pass
h3 Smart value	17.74:1	3.0:1	#000000	#E8EDEB	Pass
h3 Real-world useful	17.74:1	3.0:1	#000000	#E8EDEB	Pass
h3 Honest money	17.74:1	3.0:1	#000000	#E8EDEB	Pass
title ProfitToLife — Pro…	20.41:1	4.5:1	#000000	#FBFCFA	Pass
b Profit	20.41:1	3.0:1	#000000	#FBFCFA	Pass
strong Life	18.66:1	3.0:1	#000000	#F8F1E1	Pass
a All products	18.65:1	4.5:1	#000000	#F8F1E0	Pass
a Categories	18.61:1	4.5:1	#000000	#F7F1E0	Pass
a Trending Now	18.61:1	4.5:1	#000000	#F7F1E0	Pass
a Best Under $25	18.61:1	4.5:1	#000000	#F7F1E0	Pass
div Curated finds, refre…	18.61:1	4.5:1	#000000	#F7F1E0	Pass
span Better Life.	18.60:1	4.5:1	#000000	#F7F1DF	Pass
p Skip the endless scr…	19.23:1	4.5:1	#000000	#F7F5EC	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

Score 94/100 — 2 failing, 22 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.

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
Curated finds, refreshed weekly `section.hero > div.container > div.heroCopy > div.eyebrow`
Browse everything `section#categories > div.container > div.sectionHead > a`
HOME & LIVING `div.trendRow > article.productCard > div.productBody > span.productCategory`
−53% `div.trendRow > article.productCard > a.productImage > span.badge`
DIGITAL DOWNLOADS `div.trendRow > article.productCard > div.productBody > span.productCategory`
$19.00 `div.productBody > div.productBottom > div > del`
TECH & GADGETS `div.trendRow > article.productCard > div.productBody > span.productCategory`
View `article.productCard > div.productBody > div.productBottom > a.miniCta`
To `div > a.logo > span > em`
Life `div > a.logo > span > strong`
Hand-picked, genuinely useful products that make everyday life a little better. `footer#disclosure > div.container > div > p.footerText`
Home `footer#disclosure > div.container > div > a`
All products `footer#disclosure > div.container > div > a`
Trending Now `footer#disclosure > div.container > div > a`
Home & Living `footer#disclosure > div.container > div > a`
Tech & Gadgets `footer#disclosure > div.container > div > a`
Kitchen `footer#disclosure > div.container > div > a`
Tools & DIY `footer#disclosure > div.container > div > a`
Auto `footer#disclosure > div.container > div > a`
Fitness & Wellness `footer#disclosure > div.container > div > a`
Affiliate disclosure `footer#disclosure > div.container > div > a`
Privacy policy `footer#disclosure > div.container > div > a`
Shipping & returns `footer#disclosure > div.container > div > a`
Terms of service `footer#disclosure > div.container > div > a`
As an Amazon Associate, ProfitToLife may earn from qualifying purchases. `footer#disclosure > div.footerBottom > div.container > span`
© 2026 ProfitToLife. All rights reserved. `footer#disclosure > div.footerBottom > div.container > span`

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 `footer#disclosure > div.container > div > h4`

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.

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

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○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

○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

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

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

○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

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

○Identical links have the same purpose.

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