Skip to content
https://vanelia.shop

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
7
PASS
11
INFO
0
Checks
24
11 PASS 7 REVIEW 6 FIX
D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
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" name="email">
Warning::
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" name="email">
D
Mobile-Readable Font Sizes
Action
48% of visible text renders at >= 12 CSS px (48 below threshold)
FIX
48% of visible text renders at >= 12 CSS px (48 below threshold)
Warning::
48 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> 9.0px ("30% OFF"); <span> 8.5px ("NEW"); <span> 11.0px ("৳2,129"); <span> 11.5px ("(3)"); <span> 11.0px ("ADD TO BAG").
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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 Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <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.
B
Heading Hierarchy
32 headings
REVIEW
32 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 New Arrival
  • H4 Cotton Gauze Sleeveless Nightgown
  • H4 Elegant Lace Camisole Nightdress – Wine Red
  • H4 Elegant Lace Camisole Nightdress – Pink
  • H4 Luxury Ice Silk Satin Nightgown – Champagne
  • H4 Padded Butt Lift & Tummy Control Shaping Shorts – Black
  • H4 Seamless Full Body Shaping Bodysuit – Brown
  • H4 Seamless Full Body Shaping Bodysuit – Black
  • H4 High-Waisted Tummy Control Shaping Panty – Brown
  • H3 Best Selling
  • H4 Cotton Gauze Sleeveless Nightgown
  • H4 Elegant Lace Camisole Nightdress – Wine Red
  • H4 Luxury Ice Silk Satin Nightgown – Champagne
  • H4 Padded Butt Lift & Tummy Control Shaping Shorts – Black
  • H4 Seamless Full Body Shaping Bodysuit – Brown
  • H4 Seamless Full Body Shaping Bodysuit – Black
  • H4 High-Waisted Tummy Control Shaping Panty – Brown
  • H4 High-Waisted Tummy Control Shaping Panty – Skin Color
  • H3 Bras
  • H4 Petite Lift Wireless Push-Up Bra – Pink
  • H4 Petite Lift Wireless Push-Up Bra – Light Skin Tone
  • H4 Petite Lift Wireless Push-Up Bra – Fleshy Skin Tone
  • H4 Petite Lift Wireless Push-Up Bra – Black
  • H4 Peach Lift Wireless Push-Up Bra – Red
  • H4 Peach Lift Wireless Push-Up Bra – Skin
  • H4 Peach Lift Wireless Push-Up Bra – Champagne
  • H4 Peach Lift Wireless Push-Up Bra – Black
  • H4 Quick Links
  • H4 Customer Service
  • H4 Get In Touch
  • H4 Stay Connected
  • H3 Shopping Cart 0

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text">
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailemailEmail addressaria-label
inputtext(Search)placeholder only
inputtext(Search products...)placeholder only

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

<input type="text">; <input type="text">

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

B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 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.
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 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 2 pass AA only
a Offers
1.13:1
#000000
on
#19120E
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 New Arrival20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Best Selling20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Bras20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Shopping Cart20.12:13.0:1
#000000
#FAFAFA
Pass
title VANELIA.shop | Women…19.17:14.5:1
#000000
#F6F4F4
Pass
a Login10.78:14.5:1
#000000
#D0B4A9
Pass
a Register5.61:14.5:1
#000000
#AD7859
Pass
a Home7.29:14.5:1
#000000
#B99070
Pass
a New Arrival10.35:14.5:1
#000000
#E6A97F
Pass
a Best Selling6.45:14.5:1
#000000
#C67D50
Pass
a Offers1.13:14.5:1
#000000
#19120E
Fail
a Bras8.62:14.5:1
#000000
#CF9B7A
Pass
a Panties19.09:14.5:1
#000000
#F4F4F4
Pass
a Bra & Panty Sets19.09:14.5:1
#000000
#F4F4F4
Pass
a Nightwear19.09:14.5:1
#000000
#F4F4F4
Pass
a Shapewear19.09:14.5:1
#000000
#F4F4F4
Pass
a Tops19.09:14.5:1
#000000
#F4F4F4
Pass
a Home19.09:14.5:1
#000000
#F4F4F4
Pass
a New Arrival19.09:14.5:1
#000000
#F4F4F4
Pass
a Best Selling19.09:14.5:1
#000000
#F4F4F4
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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN ASIDE CONTENTINFO footer

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

A+
Heading Text Quality
All 32 heading(s) have substantive, well-formed text
PASS
All 32 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
2 of 112 images have issues
PASS
2 of 112 images have issues
Warning::
2 image(s) with generic alt text
Info::
110 image(s) with good alt text
112 images 110 good alt text 2 generic
IssueCount
generic2 image(s)
A
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
Info::
Input "Search products..." should use type="search" (currently type="text")
Field name "Search products..." suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "Search" should use type="search" (currently type="text")
Field name "Search" 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
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
3 explicit tabindex attribute(s) checked, no anti-patterns
PASS
3 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 23 passed
PASS
90

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.

ARIA

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
Shopping Cart 0 Loading cart... Subtotal ৳0.00 Shipping & taxes calculated a… body > aside#cpPanel

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
৳2,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,986 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,986 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳3,986 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳2,700 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳2,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳2,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,843 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳2,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,986 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳3,986 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳2,700 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳2,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳2,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,843 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,843 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,129 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,271 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,271 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,271 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
৳1,271 div.pg-body > div.pg-price-row > div.pg-price-wrap > span.pg-old
(3) div.pg-body > div.pg-price-row > span.pg-review > span.pg-review-count
CATEGORY ul.list-unstyled > li.mobile-topbar > button#hfBurger > span
SEARCH ul.list-unstyled > li > button.mobile_search_icon > span
CART ul.list-unstyled > li > a#mobileNavCart > span
ACCOUNT ul.list-unstyled > li > a > span
Subtotal aside#cpPanel > div#cpFooter > div.cp-total-row > span.cp-total-label
Shipping & taxes calculated at checkout body > aside#cpPanel > div#cpFooter > p.cp-note

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
1 section.banner_area > ul.slick-dots > li.slick-active > button#slick-slide-control00

These items highlight common accessibility best practices.

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
0 div.container > div.hf-mobile-inner > div.hf-mobile-right > a#hfMobileCartTrigger
○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
●`[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 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
●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
○`[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 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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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.

Send Feedback