Skip to content
https://LorientHaus.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
6
REVIEW
3
PASS
15
INFO
0
Checks
24
15 PASS 3 REVIEW 6 FIX
D
Tap Target Adequacy
Action
18 tap target(s) too small or too close together
FIX
18 tap target(s) too small or too close together
Warning::
18 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.
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: rgb(255, 255, 255)
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
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 4 <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
Mobile-Readable Font Sizes
96% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
96% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
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> 10.0px ("Total items in cart: 0").
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 – L'Orient Haus Custom Styling Navigation Homepage Link Search Form
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 18 pass AA only
h2 Country/Region
1.90:1
#000000
on
#4A3832
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient

1 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
h1 L'Orient Haus21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Country/Region1.90:13.0:1
#000000
#4A3832
Fail
h2 Country/Region3.96:13.0:1
#000000
#047499
Pass
h2 Account3.96:13.0:1
#000000
#047499
Pass
h2 Account3.96:13.0:1
#000000
#047499
Pass
h2 Your cart is empty3.96:13.0:1
#000000
#047499
Pass
h2 New Arrivals3.96:13.0:1
#000000
#047499
Pass
h2 Ao Dai3.96:13.0:1
#000000
#047499
Pass
h2 Ao Ba-Ba3.96:13.0:1
#000000
#047499
Pass
h2 Fine Silver Jewelry3.96:13.0:1
#000000
#047499
Pass
h2 Orient Inspired Fash…3.96:13.0:1
#000000
#047499
Pass
h2 Embroidery Clothing3.96:13.0:1
#000000
#047499
Pass
h2 Home Decor3.96:13.0:1
#000000
#047499
Pass
h2 Customer Favorites3.96:13.0:1
#000000
#047499
Pass
h2 Best Sellers3.96:13.0:1
#000000
#047499
Pass
h2 Search3.96:13.0:1
#000000
#047499
Pass
h3 Featured Items3.96:13.0:1
#000000
#047499
Pass
h3 “Yên Ninh” Ba-b…3.96:13.0:1
#000000
#047499
Pass
h3 “Midnight Tide” …3.96:13.0:1
#000000
#047499
Pass
h3 “Blush Harmony” …3.96:13.0:1
#000000
#047499
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
28 landmarks
PASS
28 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
3 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH 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
53 headings
PASS
53 headings
Info::
Single H1 present
  • H1 L'Orient Haus
  • H2 Country/Region
  • H2 Country/Region
  • H2 Account
  • H2 Account
  • H2 Your cart is empty
  • H2 New Arrivals
  • H2 Ao Dai
  • H2 Ao Ba-Ba
  • H2 Fine Silver Jewelry
  • H2 Orient Inspired Fashion
  • H2 Embroidery Clothing
  • H2 Home Decor
  • H3 Featured Items
  • H3 “Yên Ninh” Ba-ba Set – Hand-Embroidered Wormsilk in Golden Moonstone
  • H3 “Midnight Tide” – Wormsilk Modern Ba Ba Set in Deep Ocean Blue
  • H3 “Blush Harmony” – Wormsilk Modern Ba Ba Set in Rose Mist
  • H3 “Rosewood Dusk” – Wormsilk Modern Pajama Set in Burnished Rosewood
  • H3 “Celadon Whisper” Set – Hand-beaded Modern Ba Ba Set in Wormsilk
  • H3 "Tra My" - Mandarin-neck Top - Natural wormsilk in Golden Peach
  • H3 "Tra My" - Mandarin-neck Top - Natural wormsilk in Deep Magenta
  • H3 "Moc Tra" Bà Ba Set - Tencel in Rosy Sunlight
  • H2 Customer Favorites
  • H3 "Cong Vu" Ao Dai set - Wormsilk in Dark Jade
  • H3 "Loc Tho" Ao Dai set - Wormsilk in Light Moss [Modern cut]
  • H3 Giai Nhan Premium Ao Dai - White Wormsilk [Traditional cut]
  • H3 Giao Mien Ao Dai Set - Red Silk Embroidered
  • H3 Feng Shui Lacquer Arowana
  • H3 "Van Sa" Ao Dai set - Premium Hangzhou Silk in Red [Traditional cut]
  • H3 "Van Sa" Ao Dai set - Premium Hangzhou Silk in Blush Rose [Traditional Cut]
  • H3 "Vang Long Minh" Torque Necklace in Fine-silver in Dragon pattern
  • H3 "Thy Loan" Ao dai Set - Wormsilk Organza in Magenta
  • H3 "Zoya" - Embroidered Linen shirt in White (Green tone Embroidery)
  • H3 "Loc Tho" Ao Dai set - Wormsilk in Light Pink [Modern Cut]
  • H3 "Terra" - Embroidered Linen Cardigan in Black
  • H3 "Ngu Than" Ao Dai set - Silkworm Silk in Yellow [Traditional cut]
  • H3 "Yen Chi" Set - Mandarin-neck and Jacquard weave in Green
  • H3 "Loc Tho" Ao Dai for Men - Wormsilk in Teal
  • H3 “Bạch Ngọc” - Wormsilk Ao Dai Set in Ivory Grey
  • H3 "Loc Tho" Ao Dai set - Wormsilk in Peacock [Modern Cut]
  • H3 "Lien Hoa" Ao Dai set - Wormsilk in Purple [Traditional cut]
  • H2 Best Sellers
  • H3 "Luc Uyen" Ao Dai Set in Metallic Green with Red Metallic Pants [Modern cut]
  • H3 "Yen Hoa" Ao-dai Set – Embroidered on Velvet on Brick Crimson
  • H3 "Xuân Ba" Áo Dài Set - Double-Layered Tencel with Velvet Embroidered Pants
  • H3 "Lan Đình" Ao-dai Set – Embroidered in Tranquil Teal [Traditional Cut]
  • H3 "Ngọc Như Ý" Ao-dai Set – Embroidered Áo Dài Set in Soft Ivory
  • H3 "Hoa Mộc Lan" Ao-dai Set - Tencel Silk with Magnolia pattern Indigo Lotus [Modern Cut]
  • H3 "Hoa Mộc Lan" Ao-dai Set - Tencel Silk with Magnolia pattern in Moss [Modern Cut]
  • H3 "Hoa Mộc Lan" Ao-dai Set - Tencel Silk with Magnolia pattern in Purple [Modern Cut]
  • H3 Connect
  • H2 Search
  • H2 Add to cart
A+
Heading Text Quality
All 53 heading(s) have substantive, well-formed text
PASS
All 53 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
All 110 images OK
PASS
All 110 images OK
Info::
10 image(s) with alt text over 125 characters
Info::
100 image(s) with good alt text
110 images 100 good alt text
IssueCount
too long10 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#EmailInput-AUFJXOW9Bclkwa3Z0Y__connect_sectionemailEmailfor/id
#cmdk-inputsearchSearchfor/id
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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
37 explicit tabindex attribute(s) checked, no anti-patterns
PASS
37 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://lorienthaus.com/web-pixels@81a24193wb0bf602apf85b30fcm71c6b379/custom/w…")
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+
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.
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 29 passed
PASS
94

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
10% off your first order subscribe to our emails to get 10% off your first ord… div#app-embed > div._container_3eyaa_70 > div#form-container-ref > section.withImage

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.

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
Go to review 1 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 2 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 3 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 4 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 5 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 6 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 7 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 8 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 9 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 10 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 11 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 12 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 13 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 14 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 15 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 16 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 17 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot
Go to review 18 div.section__content > div.product-reviews-carousel > div.product-reviews-carousel__dots > button.product-reviews-carousel__dot

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>`
`[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
Image elements have `[alt]` attributes
Form elements have associated labels
`[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
`[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
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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
Identical links have the same purpose.
`[accesskey]` values are unique
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
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.
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback