Skip to content
https://adoredvintage.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
39
GRADE
F
FIX
9
REVIEW
2
PASS
2
INFO
0
Checks
13
2 PASS 2 REVIEW 9 FIX
D
Heading Hierarchy
Action
30 headings, 2 skip(s)
FIX
30 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
4 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Adored Vintage
  • H2 New!
  • H2 Dresses
  • H2 Tops
  • H2 Bottoms
  • H4 Reformation Smocked Dress skipped
  • H4 Apricot Bloom Dress
  • H4 Bramblewood Cardigan
  • H4 Fleur Noire Dress
  • H4 Rosette Whisper Hair Comb
  • H4 Wildflower Needlepoint Bag
  • H4 Quiet Radiance Ring
  • H4 Clementine Quilted Tote Bag
  • H4 Springtime Keepsake Dress
  • H4 Faded Maritime Jacket
  • H4 Cloudlight Pintuck Top
  • H4 Coastal Breeze Dress
  • H2 Timeless, Feminine, & Effortlessly Romantic
  • H5 Shop skipped
  • H5 Info
  • H5 Hours & Location
  • H5 Follow us
  • H5 MY BAG (0)
  • H5 MY ACCOUNT
  • H5 SIGN UP
  • H5 SIGN UP
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)

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

F
Alt Text Quality
Action
4 of 25 images have issues
FIX
4 of 25 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
4 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
3 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
25 images 18 good alt text 3 decorative 4 missing
IssueCount
missing4 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

F
Form Accessibility
Action
11 of 16 controls have issues
FIX
11 of 16 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">; <input type="submit" name="commit">; <input type="submit" name="commit">
Warning::
7 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q" id="Search">; <input type="text" name="customer[first_name]" id="PopupFirstName">; <input type="text" name="customer[last_name]" id="PopupLastName">; <input type="email" name="customer[email]" id="PopupEmail">; <input type="password" name="customer[password]" id="PopupCreatePassword">; <input type="email" name="contact[email]">; <input type="email" name="contact[email]">
Info::
5 control(s) properly labeled
16 controls
5 labeled
7 placeholder only
4 unlabeled
ControlTypeLabelMethod
#PopupCustomerEmailemailEMAILfor/id
#PopupCustomerPasswordpasswordPASSWORDfor/id
#Popup-Subscription-Confirmation-checkboxcheckboxI agree with the Privacy Policyfor/id
#Popup-Subscription-checkboxcheckboxI agree with the Privacy Policyfor/id
#aca-enlarge-togglecheckboxLarge Widgetnone
#PopupEmailemail(Enter please your email address)placeholder only
#PopupCreatePasswordpassword(••••••)placeholder only
#Searchsearch(Search products...)placeholder only
contact[email]email(E-Mail Address)placeholder only
#PopupFirstNametext(Enter please your first name)placeholder only
contact[email]email(E-Mail Address)placeholder only
#PopupLastNametext(Enter please your last name)placeholder only
inputsubmit(none)none
inputsubmit(none)none
commitsubmit(none)none
commitsubmit(none)none

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

<input type="submit">; <input type="submit">; <input type="submit" name="commit">; <input type="submit" name="commit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="search" name="q" id="Search">; <input type="text" name="customer[first_name]" id="PopupFirstName">; <input type="text" name="customer[last_name]" id="PopupLastName">; <input type="email" name="customer[email]" id="PopupEmail">; <input type="password" name="customer[password]" id="PopupCreatePassword">; <input type="email" name="contact[email]">; <input type="email" name="contact[email]">

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

F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 429 Page Title Just a moment... Custom Styling Navigation Homepage Link Search Form
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.
Got: rgba(0,0,0,0)
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Lighthouse Accessibility Audits
Score 81/100 — 4 failing, 16 passed
REVIEW
81

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.chat-app > button.chat-toggle div.chat-app > button.chat-toggle

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.header__line-top > div.container > div.header__sidebar > a.header__btn-account div.header__line-top > div.container > div.header__sidebar > a.header__btn-account
div.container > div.header__sidebar > div.ml-25 > a.header__btn-cart div.container > div.header__sidebar > div.ml-25 > a.header__btn-cart
div.row > div.home-builder-block-id-template--17930745118948__1586279708879-1 > div.promobox > a.d-block div.row > div.home-builder-block-id-template--17930745118948__1586279708879-1 > div.promobox > a.d-block
div.row > div.home-builder-block-id-template--17930745118948__1586279708879-2 > div.promobox > a.d-block div.row > div.home-builder-block-id-template--17930745118948__1586279708879-2 > div.promobox > a.d-block
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch div.d-flex > div.product-collection__image > div.product-image__overlay-top > a.absolute-stretch
div.d-lg-none > div.footer__social-media-mobile > div.social-media > a.social-media__instagram div.d-lg-none > div.footer__social-media-mobile > div.social-media > a.social-media__instagram
div.d-lg-none > div.footer__social-media-mobile > div.social-media > a.social-media__pinterest div.d-lg-none > div.footer__social-media-mobile > div.social-media > a.social-media__pinterest

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.

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
Reformation Smocked Dress div.d-flex > div.product-collection__content > div.product-collection__title > h4.m-0
SHOP div.col-lg > div.footer__section > div.footer__section-head > h5.py-10

These are opportunities to improve keyboard navigation in your application.

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
Preloved div.d-flex > div.product-collection__content > span.grid-vendor > a
Reformation Smocked Dress div.product-collection__content > div.product-collection__title > h4.m-0 > a
Vintage div.d-flex > div.product-collection__content > span.grid-vendor > a
Apricot Bloom Dress div.product-collection__content > div.product-collection__title > h4.m-0 > a
Vintage div.d-flex > div.product-collection__content > span.grid-vendor > a
Bramblewood Cardigan div.product-collection__content > div.product-collection__title > h4.m-0 > a
Vintage div.d-flex > div.product-collection__content > span.grid-vendor > a
Fleur Noire Dress div.product-collection__content > div.product-collection__title > h4.m-0 > a
Vintage div.d-flex > div.product-collection__content > span.grid-vendor > a
Rosette Whisper Hair Comb div.product-collection__content > div.product-collection__title > h4.m-0 > a
Vintage div.d-flex > div.product-collection__content > span.grid-vendor > a
Wildflower Needlepoint Bag div.product-collection__content > div.product-collection__title > h4.m-0 > a
Vintage div.d-flex > div.product-collection__content > span.grid-vendor > a
Quiet Radiance Ring div.product-collection__content > div.product-collection__title > h4.m-0 > a
Vintage div.d-flex > div.product-collection__content > span.grid-vendor > a
Clementine Quilted Tote Bag div.product-collection__content > div.product-collection__title > h4.m-0 > a
Modern div.d-flex > div.product-collection__content > span.grid-vendor > a
Springtime Keepsake Dress div.product-collection__content > div.product-collection__title > h4.m-0 > a
Vintage div.d-flex > div.product-collection__content > span.grid-vendor > a
Faded Maritime Jacket div.product-collection__content > div.product-collection__title > h4.m-0 > a
Modern div.d-flex > div.product-collection__content > span.grid-vendor > a
Cloudlight Pintuck Top div.product-collection__content > div.product-collection__title > h4.m-0 > a
Modern div.d-flex > div.product-collection__content > span.grid-vendor > a
Coastal Breeze Dress div.product-collection__content > div.product-collection__title > h4.m-0 > a

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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
Background and foreground colors have a sufficient contrast ratio
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Document has a main landmark.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
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
`[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
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.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
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.
Identical links have the same purpose.
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
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 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+
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
title Adored Vintage | Tim…20.63:14.5:1
#000000
#FFFDF6
Pass
i Rooted in nostalgia …20.63:14.5:1
#000000
#FFFDF6
Pass
a Adored Vintage20.63:14.5:1
#000000
#FFFDF6
Pass
a Adored Vintage20.63:14.5:1
#000000
#FFFDF6
Pass
span Bag (0)20.63:14.5:1
#000000
#FFFDF6
Pass
a Adored Vintage20.63:14.5:1
#000000
#FFFDF6
Pass
span Bloom Forth20.63:14.5:1
#000000
#FFFDF6
Pass
p New arrivals thought…20.63:14.5:1
#000000
#FFFDF6
Pass
a See What's New20.63:14.5:1
#000000
#FFFDF6
Pass
span Shop In Person20.63:14.5:1
#000000
#FFFDF6
Pass
p Visit our romantic, …20.63:14.5:1
#000000
#FFFDF6
Pass
a See Hours20.63:14.5:1
#000000
#FFFDF6
Pass
span New!20.63:14.5:1
#000000
#FFFDF6
Pass
span Dresses20.63:14.5:1
#000000
#FFFDF6
Pass
span Tops20.63:14.5:1
#000000
#FFFDF6
Pass
span Bottoms20.63:14.5:1
#000000
#FFFDF6
Pass
div 25% Off Taken at Che…20.63:14.5:1
#000000
#FFFDF6
Pass
div Preloved20.63:14.5:1
#000000
#FFFDF6
Pass
div Pre-order20.63:14.5:1
#000000
#FFFDF6
Pass
div Sold Out20.63:14.5:1
#000000
#FFFDF6
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback