Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 10 -1-on-focusable

FIX

0 positive, 10 -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>

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

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.

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

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 1 <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.

C

Heading Hierarchy

Action

31 headings, 2 skip(s)

REVIEW

31 headings, 2 skip(s)

Single H1 present

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: H2 → H5 (missing H3)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 Popular Products
H3 Example product title
H3 Example product title
H3 Example product title
H3 Popular Products
H3 Example product title
H3 Example product title
H3 Example product title
H1 Aarvana
H3 NAILS skipped
H3 New Arrivals
H3 BEAUTY TOOLS
H3 HAIR CARE
H3 Beauty Devices
H3 aarvana product Gallery
H3 Latest Posts
H2 Contact Us
H2 Policies
H2 Shop the look
H2 Choose Options
H5 (empty)
H5 Edit Option
H5 Back In Stock Notification
H3 Popular Products
H3 Example product title
H3 Example product title
H3 Example product title
H3 Popular Products
H3 Example product title
H3 Example product title
H3 Example product title

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B

Link & Button Quality

153 links, 24 buttons — all OK

REVIEW

153 links, 24 buttons — all OK

12 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/nails"]; a[href="/collections/nails"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"] (+2 more)

1 link(s) open in new tab without warning

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

Got: https://wa.me/923293918349?text=Hello%20I%20want%20to%20order

140 link(s) with descriptive text

153 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/collections/beauty-devices	Aarvana	img no alt	Add alt attribute to the image
/collections/nails	Aarvana	img no alt	Add alt attribute to the image
/collections/beauty-tools	Aarvana	img no alt	Add alt attribute to the image
/collections/hair-care	Aarvana	img no alt	Add alt attribute to the image
/collections/all-beauty-tools-and-device…	Aarvana	img no alt	Add alt attribute to the image
/collections/all-beauty-tools-and-device…	Aarvana	img no alt	Add alt attribute to the image
/collections/all-beauty-tools-and-device…	Aarvana	img no alt	Add alt attribute to the image
/collections/all-beauty-tools-and-device…	Aarvana	img no alt	Add alt attribute to the image
/collections/nails	Aarvana	img no alt	Add alt attribute to the image
/collections/nails	Aarvana	img no alt	Add alt attribute to the image
/collections/all-beauty-tools-and-device…	Aarvana	img no alt	Add alt attribute to the image
/collections/all-beauty-tools-and-device…	Aarvana	img no alt	Add alt attribute to the image
/collections/all-beauty-tools-and-device…	Aarvana	img no alt	Add alt attribute to the image
/collections/all-beauty-tools-and-device…	Aarvana	img no alt	Add alt attribute to the image
/collections/bundles-kits	Aarvana	img no alt	Add alt attribute to the image
/collections/bundles-kits	Aarvana	img no alt	Add alt attribute to the image
https://wa.me/923293918349?text=Hello%20…	Chat with us	new tab	Add '(opens in new tab)' to text

164 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/nails"]; a[href="/collections/nails"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"]; a[href="/collections/all-beauty-tools-and-devices"] (+2 more)

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://wa.me/923293918349?text=Hello%20I%20want%20to%20order

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

B

Form Input Quality

2 input-semantic issue(s) across 6 form control(s)

REVIEW

2 input-semantic issue(s) across 6 form control(s)

1 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="customer[password]">.

2 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="contact[email]">, <input type="email" name="customer[email]">.

C

Tap Target Adequacy

Action

4 tap target(s) too small or too close together

REVIEW

4 tap target(s) too small or too close together

4 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

B

Mobile-Readable Font Sizes

98% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (1 below threshold)

1 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> 0.0px ("Cart").

C

Lighthouse Accessibility Audits

Action

Score 73/100 — 8 failing, 25 passed

REVIEW

73

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2 `div.container-full > div.slideshow > ul.slick-dots > li#slick-slide11`
1 `div.halo-block-content > div.products-carousel > ul.slick-dots > li#slick-slide20`

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
123 `div#slideshow-wrapper-template--21263729229982__16321237356a896dad > div.container-full > div.slideshow > ul.slick-dots`
12 `div.container-full > div.halo-block-content > div.products-carousel > ul.slick-dots`

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 `div.halo-block-content > div.products-carousel > ul.slick-dots > li#slick-slide20`

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
div.slideshow > div.slick-list > div.slick-track > div#block-image_z3AtBd `div.slideshow > div.slick-list > div.slick-track > div#block-image_z3AtBd`
1 `div.container-full > div.slideshow > ul.slick-dots > li#slick-slide10`
3 `div.container-full > div.slideshow > ul.slick-dots > li#slick-slide12`
2 `div.halo-block-content > div.products-carousel > ul.slick-dots > li#slick-slide21`

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Beauty Device Artificial Nails Beauty Tools Hair Care `div.container-full > div.halo-row > div.slick-list > div.slick-track`
div.container-full > div.slideshow > div.slick-list > div.slick-track `div.container-full > div.slideshow > div.slick-list > div.slick-track`
Sale Add to wishlist Quick View VENDOR: AARVANA Pack Of 2 Handle Grip Nail Brus… `div.halo-block-content > div.products-carousel > div.slick-list > div.slick-track`

When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.slideshow > div.slick-list > div.slick-track > div#block-image_RJFb7x `div.slideshow > div.slick-list > div.slick-track > div#block-image_RJFb7x`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Sale `div.card-product > div.card-product__wrapper > div.card__badge > span.badge`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
Rs.599.00 `dl > div.price__sale > dd.price__last > span.price-item`
Sale `div.card-product > div.card-product__wrapper > div.card__badge > span.badge`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
Rs.799.00 `dl > div.price__sale > dd.price__last > span.price-item`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
Rs.399.00 `dl > div.price__sale > dd.price__last > span.price-item`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
Rs.499.00 `dl > div.price__sale > dd.price__last > span.price-item`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
Rs.799.00 `dl > div.price__sale > dd.price__last > span.price-item`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
Rs.1,699.00 `dl > div.price__sale > dd.price__last > span.price-item`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
Rs.1,499.00 `dl > div.price__sale > dd.price__last > span.price-item`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
Rs.799.00 `dl > div.price__sale > dd.price__last > span.price-item`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
Rs.749.00 `dl > div.price__sale > dd.price__last > span.price-item`
AARVANA `div.card-information__wrapper > div.card-information__group > div.card-vendor > a`
From Rs.799.00 `dl > div.price__sale > dd.price__last > span.price-item`
From `div.price__sale > dd.price__last > span.price-item > span.text`
Chat with us `section#shopify-section-sections--21263730147486__custom_liquid_YpT9jp > a.wa-btn > div.wa-chat > span`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Beauty Device `div.slick-track > div#block-image_CzJ8UE > div.wrapper-content > a.text`
Artificial Nails `div.slick-track > div#block-image_a7Gtc7 > div.wrapper-content > a.text`
Beauty Tools `div.slick-track > div#block-image_Px9XXW > div.wrapper-content > a.text`
2 `div.slideshow > ul.slick-dots > li#slick-slide11 > button`

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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 use only permitted ARIA attributes

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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 `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○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

○Form elements have associated labels

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

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

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 3 all-caps heading(s)

A+

Alt Text Quality

All 25 images OK

PASS

All 25 images OK

16 decorative image(s) correctly marked

9 image(s) with good alt text

25 images 9 good alt text 16 decorative

All images have appropriate alt text.

A

Form Accessibility

1 of 6 controls have issues

PASS

1 of 6 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

5 control(s) properly labeled

6 controls

5 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#Search-In-Modal-Utility	search	Search entire store here...	for/id
#halo-notify-email	email	Leave your email and we will notify as soon as the product / variant is back in stock	for/id
#customer_email	email	Email Address *	for/id
#customer_password	password	Password *	for/id
#Search-In-Modal-Sidebar	search	Search	for/id
input	submit	(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

A+

Form Input Types

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

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

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found – Aarvana ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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 Aarvana	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Contact Us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Policies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Aarvana	16.14:1	4.5:1	#000000	#F4DCDE	Pass
a Skip to content	17.34:1	4.5:1	#000000	#FDE3E9	Pass
p 🚚FREE DELIVERY ON…	17.34:1	4.5:1	#000000	#FDE3E9	Pass
p 🚚FREE DELIVERY ON…	19.49:1	4.5:1	#000000	#FEF4F6	Pass
p 🚚FREE DELIVERY ON…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p 🚚FREE DELIVERY ON…	20.65:1	4.5:1	#000000	#FDFDFD	Pass
p 🚚FREE DELIVERY ON…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p 🚚FREE DELIVERY ON…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p 🚚FREE DELIVERY ON…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p 🚚FREE DELIVERY ON…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p 🚚FREE DELIVERY ON…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p 🚚FREE DELIVERY ON…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p 🚚FREE DELIVERY ON…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p 🚚FREE DELIVERY ON…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Search entire store …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Popular Products	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Vendor:	21.00:1	4.5:1	#000000	#FFFFFF	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.