Skip to content
https://voglastore.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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
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
Theme color only
FIX
Theme color only
Info::
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.
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 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
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::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <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
Alt Text Quality
1 of 54 images have issues
REVIEW
1 of 54 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
7 decorative image(s) correctly marked
Info::
46 image(s) with good alt text
54 images 46 good alt text 7 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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 404 Not Found – Vogla Store ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA 1 pass AA only
h2 Cookie consent
1.58:1
#000000
on
#372E23
needs 3.0:1 (large text)
24px · top of page (header area)
title Vogla Store | Clothing Store | Elegance …
1.58:1
#000000
on
#372E23
needs 4.5:1 (normal text)
16px · top of page (header area)
p We and our partners, including Shopify, …
1.62:1
#000000
on
#4F2703
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Privacy Policy
2.09:1
#000000
on
#5E3A16
needs 4.5:1 (normal text)
16px · top of page (header area)
span Manage preferences
1.57:1
#000000
on
#482707
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button Accept
2.11:1
#000000
on
#593D18
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button Decline
3.17:1
#000000
on
#6F593E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Skip to content
3.29:1
#000000
on
#735B3B
needs 4.5:1 (normal text)
16px · above the fold
a Continue shopping
3.25:1
#000000
on
#6E5B46
needs 4.5:1 (normal text)
16px · above the fold
p Have an account?
3.38:1
#000000
on
#6C5F4E
needs 4.5:1 (normal text)
16px · above the fold
a Log in
4.15:1
#000000
on
#736E66
needs 4.5:1 (normal text)
16px · above the fold

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Cookie consent1.58:13.0:1
#000000
#372E23
Fail
h2 Your cart is empty3.49:13.0:1
#000000
#765F43
Pass
h2 Your cart4.66:13.0:1
#000000
#7B766E
Pass
h2 Estimated total4.85:13.0:1
#000000
#7D7972
Pass
h2 Country/region4.93:13.0:1
#000000
#7F7A73
Pass
h2 Language4.93:13.0:1
#000000
#7F7A73
Pass
h2 Language4.93:13.0:1
#000000
#7F7A73
Pass
h2 Elegance. Distinctio…4.93:13.0:1
#000000
#7F7A73
Pass
h2 Country/region4.93:13.0:1
#000000
#7F7A73
Pass
h2 Language4.93:13.0:1
#000000
#7F7A73
Pass
title Vogla Store | Clothi…1.58:14.5:1
#000000
#372E23
Fail
p We and our partners,…1.62:14.5:1
#000000
#4F2703
Fail
a Privacy Policy2.09:14.5:1
#000000
#5E3A16
Fail
span Manage preferences1.57:14.5:1
#000000
#482707
Fail
button Accept2.11:14.5:1
#000000
#593D18
Fail
button Decline3.17:14.5:1
#000000
#6F593E
Fail
a Skip to content3.29:14.5:1
#000000
#735B3B
Fail
a Continue shopping3.25:14.5:1
#000000
#6E5B46
Fail
p Have an account?3.38:14.5:1
#000000
#6C5F4E
Fail
a Log in4.15:14.5:1
#000000
#736E66
Fail

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.

B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 28 passed
REVIEW
88

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
Subscribe and elevate your glamour with a 15% discount. div.image-with-text__text-item > div#ImageWithText--template--25022553293106__image_with_text_rTrR3c > div.image-with-text__text > p
SUBSCRIBE div.image-with-text__grid > div.image-with-text__text-item > div#ImageWithText--template--25022553293106__image_with_text_rTrR3c > a.button
Holiday Collection div.card__content > div.card__information > h3.card__heading > a.full-unstyled-link
Vogla Luxe div.card__content > div.card__information > h3.card__heading > a.full-unstyled-link
IN THEIR WORDS div.page-width > div.title-wrapper-with-link > h2.title > strong
Follow on div.relative > button.group > span.cursor-pointer
Country/region localization-form > form#FooterCountryForm > div > h2#FooterCountryLabel
Language localization-form > form#FooterLanguageForm > div > h2#FooterLanguageLabel
© 2026, Vogla Store div.footer__content-bottom > div.footer__content-bottom-wrapper > div.footer__copyright > small.copyright__content
Vogla Store div.footer__content-bottom-wrapper > div.footer__copyright > small.copyright__content > a
Powered by Shopify div.footer__content-bottom-wrapper > div.footer__copyright > small.copyright__content > a
Privacy policy ul.policies > li > small.copyright__content > a
Refund policy ul.policies > li > small.copyright__content > a
Terms of service ul.policies > li > small.copyright__content > a
Shipping policy ul.policies > li > small.copyright__content > a
Contact information ul.policies > li > small.copyright__content > a
Cookie preferences ul.policies > li > small.copyright__content > a
Sign Up div#signUpModal-template--25022553293106__tybo_modal_4nCC7K-text-box > div#signUpModal-template--25022553293106__tybo_modal_4nCC7K-button-wrapper > center > a#signUpModal-template--25022553293106__tybo_modal_4nCC7K-button

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#tyboFooter > center > a > img div#tyboFooter > center > a > img

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#tybo-slideshow-mobile--template--25022553293106__tybo_slideshow_B3gm6G > div#tybo-slideshow-slider-mobile--template--25022553293106__tybo_slideshow_B3gm6G > div#tybo-slideshow-slide-mobile--tybo_slideshow_slide_3QLWpY > a.tybo-slideshow-slide-content-container__link div#tybo-slideshow-mobile--template--25022553293106__tybo_slideshow_B3gm6G > div#tybo-slideshow-slider-mobile--template--25022553293106__tybo_slideshow_B3gm6G > div#tybo-slideshow-slide-mobile--tybo_slideshow_slide_3QLWpY > a.tybo-slideshow-slide-content-container__link
section#custom-homepage-instagram-feed-container > blockquote.instagram-media > div > a section#custom-homepage-instagram-feed-container > blockquote.instagram-media > div > a
body.gradient > div#tyboFooter > center > a body.gradient > div#tyboFooter > center > a

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.

○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]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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
●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.
●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
●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
●ARIA IDs are unique
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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
○`[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
○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
○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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A+
Heading Hierarchy
92 headings
PASS
92 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Cookie consent
  • H2 Your cart is empty
  • H2 Your cart
  • H2 Estimated total
  • H2 Country/region
  • H2 Language
  • H1 (empty)
  • H2 Language
  • H2 SHOP BY COLLECTION
  • H3 Jumpsuits
  • H3 Jumpsuits
  • H3 Dresses
  • H3 Dresses
  • H3 Sets
  • H3 Sets
  • H3 Vogla ESCAPE
  • H3 Vogla ESCAPE
  • H2 NEW IN
  • H3 The Monaco trench skirt set
  • H3 The Monaco trench skirt set
  • H3 Starlight Denim Bermuda
  • H3 Starlight Denim Bermuda
  • H3 Santorini Breeze Midi Dress
  • H3 Santorini Breeze Midi Dress
  • H3 Valencia Crochet Linen Pants Set
  • H3 Valencia Crochet Linen Pants Set
  • H3 Casual Off-Shoulder Polka Dot Two-Piece Outfit
  • H3 Casual Off-Shoulder Polka Dot Two-Piece Outfit
  • H3 Celeste Gold Button Pant Set
  • H3 Celeste Gold Button Pant Set
  • H3 Monroe belted Bermuda
  • H3 Monroe belted Bermuda
  • H3 Monroe vest
  • H3 Monroe vest
  • H3 Isabella Ruffle Halter Romper
  • H3 Isabella Ruffle Halter Romper
  • H3 Sofia Ruffle Breeze Mini Dress
  • H3 Sofia Ruffle Breeze Mini Dress
  • H3 Azure Flow Pleated Maxi Skirt
  • H3 Azure Flow Pleated Maxi Skirt
  • H3 A solid woven top - FT1771-B
  • H3 A solid woven top - FT1771-B
  • H2 GET 15% DISCOUNT
  • H2 SHOP BY COLLECTION
  • H3 Holiday Collection
  • H3 Holiday Collection
  • H3 Vogla Luxe
  • H3 Vogla Luxe
  • H3 Vogla Curve
  • H3 Vogla Curve
  • H3 Accesories
  • H3 Accesories
  • H3 Casual Chic
  • H3 Casual Chic
  • H3 Shoes
  • H3 Shoes
  • H3 Skirts
  • H3 Skirts
  • H3 Blazers
  • H3 Blazers
  • H2 MOST-LOVED PIECES
  • H3 Mercedita Lace Sheer Mesh Top Collection
  • H3 Mercedita Lace Sheer Mesh Top Collection
  • H3 Women’s Satin Lace Trim Halter Neck Asymmetrical Top
  • H3 Women’s Satin Lace Trim Halter Neck Asymmetrical Top
  • H3 Asymmetric Lace Trim Short Sleeve Satin Top
  • H3 Asymmetric Lace Trim Short Sleeve Satin Top
  • H3 Cotton Crew Neck T-Shirt Short Sleeve Casual Top
  • H3 Cotton Crew Neck T-Shirt Short Sleeve Casual Top
  • H3 Carina Set
  • H3 Carina Set
  • H3 Lorena FRINGE SKIRT
  • H3 Lorena FRINGE SKIRT
  • H3 Felicia Chic Ruffle Skirt
  • H3 Felicia Chic Ruffle Skirt
  • H3 Élise Sovereign Halter Blouse
  • H3 Élise Sovereign Halter Blouse
  • H3 VOGUE Muse Tee
  • H3 VOGUE Muse Tee
  • H3 Camila Dress
  • H3 Camila Dress
  • H3 LAS Asymmetric Lace Trim Short Sleeve Satin Top (S-XL)
  • H3 LAS Asymmetric Lace Trim Short Sleeve Satin Top (S-XL)
  • H3 Flower Color-Block Poplin Top
  • H3 Flower Color-Block Poplin Top
  • H2 IN THEIR WORDS
  • H3 Cris Cabrera
  • H3 Mary Luz Rodríguez
  • H3 Cindy Flores
  • H2 Elegance. Distinction. Class.
  • H2 Country/region
  • H2 Language

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
6 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: 6 all-caps heading(s)
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#country-filter-inputsearchSearchfor/id
#Search-In-ModalsearchSearchfor/id
#country-filter-inputsearchSearchfor/id
A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
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+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
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"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
511 explicit tabindex attribute(s) checked, no anti-patterns
PASS
511 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+
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 7 visible text node(s) render at >= 12 CSS pixels
PASS
All 7 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::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback