Skip to content
https://feshionz.com/?srsltid=AfmBOoqZppqG1g1ffxbM8Rz7vF8ViCHeqH8cVZbTB2kdtgWCxSFHYr7d

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
6
REVIEW
3
PASS
15
INFO
0
Checks
24
15 PASS 3 REVIEW 6 FIX
D
Iframe Accessibility
Action
6/7 iframe(s) missing title; 0 placeholder(s)
FIX
6/7 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
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.
Warning::
<iframe> missing title attribute (src="about:blank")
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.
Warning::
<iframe> missing title attribute (src="about:blank")
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.
Warning::
<iframe> missing title attribute (src="about:blank")
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.
Warning::
<iframe> missing title attribute (src="https://www.google.com/recaptcha/api2/aframe")
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.
Warning::
<iframe> missing title attribute (src="https://googleads.g.doubleclick.net/pagead/html/r20261023/r20190131/zrt_lookup.…")
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.
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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark 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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <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
Heading Hierarchy
41 headings, 1 skip(s)
REVIEW
41 headings, 1 skip(s)
Warning::
Multiple H1 headings (11 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Low price
  • H1 Hair clip duplicate H1
  • H2 Facebook
  • H2 Whatsapp
  • H2 YouTube
  • H2 Our best products
  • H1 Narkins & J. duplicate H1
  • H1 Original duplicate H1
  • H1 Low price duplicate H1
  • H2 WhatsApp
  • H2 YouTube
  • H2 with
  • H2 Facebook
  • H2 Cheap in price and best
  • H1 Bin Seed duplicate H1
  • H1 Embroidered duplicate H1
  • H1 Lawn Dupatta duplicate H1
  • H2 YouTube
  • H2 WhatsApp
  • H2 Facebook
  • H1 & duplicate H1
  • H1 Prefumes duplicate H1
  • H1 Fragrances duplicate H1
  • H2 Oils, Pefume, & Fragrance
  • H2 WhatsAp
  • H2 Facebook
  • H2 YouTube
  • H2 Embroidered Silk
  • H2 Special Edition
  • H4 You can choose your design from the dresses with you chaise skipped
  • H5 Nationwide Shipping
  • H5 Original Brands
  • H5 Best Quality
  • H5 Best Offers
  • H5 Fragrances
  • H5 Replacement & Returns
  • H5 Stitching Facility
  • H5 Secure Payments
  • H3 Get your offer now!
  • H2 For Her
  • H2 Our Policies

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – Feshionz ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
13 landmarks
PASS
13 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV "Primary Site Navigation" MAIN CONTENTINFO footer

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H1: "&"
Got: 1 ≤2-char heading(s)
A+
Alt Text Quality
All 19 images OK
PASS
All 19 images OK
Info::
17 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
19 images 2 good alt text 17 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
5 explicit tabindex attribute(s) checked, no anti-patterns
PASS
5 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 57 visible text node(s) render at >= 12 CSS pixels
PASS
All 57 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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+
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)
ElementRatioRequiredFGBGResult
h1 Low price20.12:13.0:1
#000000
#FAFAFA
Pass
h1 Hair clip20.12:13.0:1
#000000
#FAFAFA
Pass
h1 Narkins & J.19.92:13.0:1
#000000
#F8F9FA
Pass
h1 Original19.55:13.0:1
#000000
#F5F7F9
Pass
h1 Low price19.55:13.0:1
#000000
#F5F7F9
Pass
h1 Bin Seed19.55:13.0:1
#000000
#F5F7F9
Pass
h1 Embroidered19.55:13.0:1
#000000
#F5F7F9
Pass
h1 Lawn Dupatta19.55:13.0:1
#000000
#F5F7F9
Pass
h1 Prefumes19.55:13.0:1
#000000
#F5F7F9
Pass
h1 Fragrances19.55:13.0:1
#000000
#F5F7F9
Pass
h2 Facebook12.75:13.0:1
#000000
#D4C7C2
Pass
h2 Whatsapp12.75:13.0:1
#000000
#D4C7C2
Pass
h2 YouTube12.75:13.0:1
#000000
#D4C7C2
Pass
h2 Our best products16.97:13.0:1
#000000
#EBE6E4
Pass
h2 WhatsApp19.55:13.0:1
#000000
#F5F7F9
Pass
h2 YouTube19.55:13.0:1
#000000
#F5F7F9
Pass
h2 with19.55:13.0:1
#000000
#F5F7F9
Pass
h2 Facebook19.55:13.0:1
#000000
#F5F7F9
Pass
h2 Cheap in price and b…19.55:13.0:1
#000000
#F5F7F9
Pass
h2 YouTube19.55:13.0:1
#000000
#F5F7F9
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 90/100 — 4 failing, 21 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.

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
Our best products div.depicter-layers-fold > div.depicter-layer-frame > div.depicter-animation-wrap > h2#depicter-3-element-71
Low price div.depicter-layers-fold > div.depicter-layer-frame > div.depicter-animation-wrap > h1#depicter-3-element-81
with div.depicter-layers-fold > div.depicter-layer-frame > div.depicter-animation-wrap > h2#depicter-3-element-128
Lawn (Ladies, Unstitch) nav.menu-for-her-container > ul#menu-for-her > li#menu-item-2457 > a.menu-link
Tops and Shirts nav.menu-for-her-container > ul#menu-for-her > li#menu-item-2458 > a.menu-link
Women Jewels nav.menu-for-her-container > ul#menu-for-her > li#menu-item-2459 > a.menu-link
Heels and Flats nav.menu-for-her-container > ul#menu-for-her > li#menu-item-2460 > a.menu-link
Women Accessories nav.menu-for-her-container > ul#menu-for-her > li#menu-item-2461 > a.menu-link

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
You can choose your design from the dresses with you chaise div.uagb-container-inner-blocks-wrap > div.wp-block-group > div.wp-block-uagb-advanced-heading > h4.uagb-heading-text

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.depicter-view > div.depicter-sections > div#depicter-3-section-1 > a.depicter-section-link div.depicter-view > div.depicter-sections > div#depicter-3-section-1 > a.depicter-section-link
div.depicter-layers-wrapper > div.depicter-layers-fold > div.depicter-layer-frame > a div.depicter-layers-wrapper > div.depicter-layers-fold > div.depicter-layer-frame > a
div.depicter-view > div.depicter-sections > div#depicter-3-section-64 > a.depicter-section-link div.depicter-view > div.depicter-sections > div#depicter-3-section-64 > a.depicter-section-link
div.depicter-view > div.depicter-sections > div#depicter-3-section-102 > a.depicter-section-link div.depicter-view > div.depicter-sections > div#depicter-3-section-102 > a.depicter-section-link

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
0₨ div.ast-builder-layout-element > div.ast-site-header-cart > div.ast-site-header-cart-li > a.cart-container
○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
●`[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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●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 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
○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.
○No element has a `[tabindex]` value greater than 0
○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