Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 11 -1-on-focusable

FIX

0 positive, 11 -1-on-focusable

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

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 <button>

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 <button>

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 <button>

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 <button>

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 <button>

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>

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>

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>

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 <button id="lhAmTabRegister">

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 <input id="lh-chat-company">

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

F

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

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #a05513

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

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)

Skip navigation link detected

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

B

Form Accessibility

2 of 10 controls have issues

REVIEW

2 of 10 controls have issues

1 control(s) without accessible label

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

Got: <select id="bucksSelector">

1 control(s) rely on placeholder only

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

Got: <input type="text" name="discount">

8 control(s) properly labeled

10 controls

8 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#MobileSearchInput	search	Search	for/id
#NewsletterEmail-template--27329754530159__newsletter	email	Email	for/id
#LhSearchInput	search	Search	for/id
input	number	Quantity	aria-label
#lh-chat-text	textarea	Type your question	for/id
#lh-chat-name	text	Name *	for/id
#lh-chat-email	email	Email *	for/id
#lh-chat-code	text	6-digit code	for/id
discount	text	(Discount code)	placeholder only
#bucksSelector	select	(none)	none

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

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.

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

C

Link & Button Quality

Action

7 issue(s) across 205 links and 80 buttons

REVIEW

7 issue(s) across 205 links and 80 buttons

1 link(s) with no accessible text

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

Got: #

6 link(s) open in new tab without warning

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

Got: https://lovelyhair.shop/policies/privacy-policy; https://www.instagram.com/lovelyhairplus; https://www.facebook.com/profile.php?id=100076688292549; https://www.tiktok.com/@lovelyhair.shop; https://www.linkedin.com/in/lovely-hair-extensions-aa27a3428; https://wa.me/13192178250

6 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.lh-carousel-dot (#1845 on page); button.lh-carousel-dot (#1846 on page); button.lh-carousel-dot (#1847 on page); button.lh-carousel-dot (#1848 on page); button.lh-carousel-dot (#1849 on page); button.lh-carousel-dot (#1850 on page)

198 link(s) with descriptive text

205 links

1 empty

0 generic text

6 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://lovelyhair.shop/policies/privacy…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/collections/kinky-curly	Kinky Curly	img no alt	Add alt attribute to the image
/collections/yaki-straight	Yaki Straight	img no alt	Add alt attribute to the image
/collections/water-wave-wigs	Water Wave	img no alt	Add alt attribute to the image
/collections/deep-wave	Deep Wave	img no alt	Add alt attribute to the image
/collections/body-wave	Body Wave	img no alt	Add alt attribute to the image
/collections/bob-wig	Bob Wig	img no alt	Add alt attribute to the image
/collections/everyday	EverydayShop now	img no alt	Add alt attribute to the image
/collections/travel	TravelShop now	img no alt	Add alt attribute to the image
/collections/special-events	Special EventsShop now	img no alt	Add alt attribute to the image
/collections/bridal	WeddingShop now	img no alt	Add alt attribute to the image
https://www.instagram.com/lovelyhairplus	Follow us on Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/profile.php?id=…	Follow us on Facebook	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@lovelyhair.shop	Follow us on TikTok	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/lovely-hair-…	Follow us on LinkedIn	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://wa.me/13192178250	Talk to a person on WhatsApp	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

272 links and buttons have descriptive text

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

#

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://lovelyhair.shop/policies/privacy-policy; https://www.instagram.com/lovelyhairplus; https://www.facebook.com/profile.php?id=100076688292549; https://www.tiktok.com/@lovelyhair.shop; https://www.linkedin.com/in/lovely-hair-extensions-aa27a3428; https://wa.me/13192178250

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.lh-carousel-dot (#1845 on page); button.lh-carousel-dot (#1846 on page); button.lh-carousel-dot (#1847 on page); button.lh-carousel-dot (#1848 on page); button.lh-carousel-dot (#1849 on page); button.lh-carousel-dot (#1850 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

C

Mobile Keyboard & Autofill

Action

4/7 eligible field(s) missing autocomplete or inputmode

REVIEW

4/7 eligible field(s) missing autocomplete or inputmode

4 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: search, email.

Got: <input type="search" name="q" id="MobileSearchInput">, <input type="email" name="contact[email]" id="NewsletterEmail-template--27329754530159__newsletter">, <input type="search" name="q" id="LhSearchInput">, <input type="email" name="email" id="lh-chat-email">

C

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found · Lovelyhair ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

A+

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

25 headings

PASS

25 headings

Single H1 present

H2 Cookie consent
H1 Real Hair. Real Confidence.
H2 Best Sellers
H2 Trending Now
H2 Real Reviews from Real Customers
H2 Shop by Occasion
H2 Real Hair. Real Hands.
H3 Braiding & Natural Styling
H3 Glueless Wig Installation
H3 Sew-In Weave
H2 Why Choose Us
H3 Free Shipping
H3 Customer Service
H3 Quality Products
H3 30-Day Returns
H2 Join the LovelyHair Family
H2 Shop
H2 Customer Care
H2 Explore
H2 Policies
H2 Trending searches
H2 Recently viewed
H2 Popular right now
H2 Your cart 0
H2 Welcome to LovelyHair

A+

Heading Text Quality

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

PASS

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

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

A

Alt Text Quality

All 76 images OK

PASS

All 76 images OK

7 image(s) with alt text over 125 characters

16 decorative image(s) correctly marked

53 image(s) with good alt text

76 images 53 good alt text 16 decorative

Issue	Count
too long	7 image(s)

A+

Form Input Types

10 form control(s) checked, no type mismatches

PASS

10 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

10 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

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+

Mobile-Readable Font Sizes

All 65 visible text node(s) render at >= 12 CSS pixels

PASS

All 65 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

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 Real Hair. Real Conf…	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Cookie consent	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Best Sellers	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Trending Now	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Real Reviews from Re…	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Shop by Occasion	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Real Hair. Real Hand…	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Why Choose Us	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Join the LovelyHair …	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Shop	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Customer Care	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Explore	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Policies	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Trending searches	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Recently viewed	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Popular right now	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Your cart	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h2 Welcome to LovelyHai…	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h3 Free Shipping	20.11:1	3.0:1	#000000	#FAFAF9	Pass
h3 Customer Service	20.11:1	3.0:1	#000000	#FAFAF9	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 100/100 — 0 failing, 30 passed

PASS

100

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.

○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

●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

●`[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

●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

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

●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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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