Skip to content
https://dyacys-l.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
5
REVIEW
6
PASS
13
INFO
0
Checks
24
13 PASS 6 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
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
No navigation patterns
FIX
No navigation patterns
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
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
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark 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 MAIN ASIDE "Product information" 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

B
Heading Hierarchy
6 headings
REVIEW
6 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Nos Produits Dyacys-Lمنتجاتنا
  • H2 Nos Créationsإبداعاتنا
  • H2 Qui sommes-nous Dyacys-Lمن نحن
  • H2 .Meilleurs Ventesالأكثر مبيعًا
  • H2 Dyacys-L
  • H2 Pourquoi Dyacys-L لماذا Dyacys-L

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 63 controls have issues
REVIEW
2 of 63 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" name="q">; <input type="text" name="q">
Info::
61 control(s) properly labeled
63 controls
61 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
المقاس // Taille_1370radioS/Mnone
المقاس // Taille_1370radioL/XLnone
اللون // Couleur_1808radionone
اللون // Couleur_1808radionone
المقاس // Taille_1713radioS/Mnone
المقاس // Taille_1713radioL/XLnone
اللون // Couleur_1718radionone
المقاس // Taille_1102radioS/Mnone
المقاس // Taille_1102radioL/XLnone
اللون // Couleur_1622radionone
اللون // Couleur_1622radionone
اللون // Couleur_1622radionone
اللون // Couleur_1622radionone
المقاس // Taille_572radioS/Mnone
المقاس // Taille_572radioL/XLnone
اللون // Couleur_255radionone
اللون // Couleur_255radionone
اللون // Couleur_255radionone
المقاس // Taille_1454radioS/Mnone
المقاس // Taille_1454radioL/XLnone
اللون // Couleur_1796radionone
اللون // Couleur_1796radionone
اللون // Couleur_1796radionone
اللون // Couleur_1796radionone
اللون // Couleur_1796radionone
اللون // Couleur_1796radionone
اللون // Couleur_1796radionone
المقاس // Taille_1351radioS/Mnone
المقاس // Taille_1351radioL/XLnone
اللون // Couleur_984radionone
اللون // Couleur_984radionone
اللون // Couleur_984radionone
Taille_737radioS/Mnone
Taille_737radioL/XLnone
Couleur_1503radionone
Couleur_1503radionone
Couleur_1503radionone
المقاس // Taille_441radioS/Mnone
المقاس // Taille_441radioL/XLnone
اللون // Couleur_269radionone
المقاس // Taille_1924radioS/Mnone
المقاس // Taille_1924radioL/XLnone
اللون // Couleur_1569radionone
اللون // Couleur_1569radionone
اللون // Couleur_1569radionone
اللون // Couleur_1569radionone
اللون // Couleur_1569radionone
اللون // Couleur_1569radionone
اللون // Couleur_1569radionone
المقاس // Taille_902radioS/Mnone
المقاس // Taille_902radioL/XLnone
اللون // Couleur_786radionone
اللون // Couleur_786radionone
#1radionone
#2radionone
#3radionone
#4radionone
المقاس // Taille_1964radioS/Mnone
المقاس // Taille_1964radioL/XLnone
اللون // Couleur_381radionone
اللون // Couleur_381radionone
qtext(ابحث..)placeholder only
qtext(ابحث..)placeholder only

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

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

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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
title Dyacys-L | vêtements Femmes moderne
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a تجاوز إلى المحتوى
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
p Paiement à la livraison Livraison part…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Nos Produits Dyacys-…8.04:13.0:1
#000000
#AF9D8F
Pass
h2 منتجاتنا8.04:13.0:1
#000000
#AF9D8F
Pass
h2 Nos Créations8.04:13.0:1
#000000
#AF9D8F
Pass
h2 إبداعاتنا8.04:13.0:1
#000000
#AF9D8F
Pass
h2 Qui sommes-nous Dyac…8.04:13.0:1
#000000
#AF9D8F
Pass
h2 من نحن8.04:13.0:1
#000000
#AF9D8F
Pass
h2 .Meilleurs Ventes8.04:13.0:1
#000000
#AF9D8F
Pass
h2 الأكثر مبي…8.04:13.0:1
#000000
#AF9D8F
Pass
h2 Dyacys-L8.04:13.0:1
#000000
#AF9D8F
Pass
h2 Pourquoi Dyacys-L8.04:13.0:1
#000000
#AF9D8F
Pass
h2 لماذا Dyacys-L8.04:13.0:1
#000000
#AF9D8F
Pass
title Dyacys-L | vêtement…1.00:14.5:1
#000000
#000000
Fail
a تجاوز إلى ا…1.00:14.5:1
#000000
#000000
Fail
p Paiement à la livra…1.00:14.5:1
#000000
#000000
Fail
p الدفع عند ا…21.00:14.5:1
#000000
#FFFFFF
Pass
a الرئيسية21.00:14.5:1
#000000
#FFFFFF
Pass
a Accueil21.00:14.5:1
#000000
#FFFFFF
Pass
a المجموعات8.33:14.5:1
#000000
#B79F88
Pass
a Collections8.25:14.5:1
#000000
#B49F87
Pass
a من نحن8.49:14.5:1
#000000
#B7A18C
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+
Heading Text Quality
All 6 heading(s) have substantive, well-formed text
PASS
All 6 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 47 images OK
PASS
All 47 images OK
Info::
8 decorative image(s) correctly marked
Info::
39 image(s) with good alt text
47 images 39 good alt text 8 decorative
All images have appropriate alt text.
A+
Form Input Types
63 form control(s) checked, no type mismatches
PASS
63 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
63 form control(s) checked, no input-semantic issues
PASS
63 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 "ar"
PASS
Lang attribute set to "ar"
Info::
<html lang="ar"> is set and valid
Got: ar
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
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 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
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 23 passed
PASS
91

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

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.variant > yc-variant > label.variant-item > input div.variant > yc-variant > label.variant-item > input
div.variant > yc-variant > label.variant-item > input div.variant > yc-variant > label.variant-item > input

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ensemble Col Montant طقم بياقة عالية 360 درهم حدد الخيارات Ensemble Zippé طقم ب… section#youcan-section--section_1fqn362ai98y51h > yc-section > div.products-by-collection > ul.items-grid
Haut Kimono توب كيمونو 390 درهم حدد الخيارات Pull Classique بولوفر كلاسيكي 240 … section#youcan-section--section_65dcf68424fe9c > yc-section > div.products-by-collection > ul.items-grid

These are opportunities to improve the experience of reading tabular or list data using 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
Pulls | Hauts بولوفر div.collections > ul.items-grid > li > a.collection-card
Sport & Fitness رياضة ولياقة div.collections > ul.items-grid > li > a.collection-card
Nos Ensembles الأطقم div.collections > ul.items-grid > li > a.collection-card
Casual à Hijab Intégré كاجوال بحجاب مدمج div.collections > ul.items-grid > li > a.collection-card
Chemises قمصان div.collections > ul.items-grid > li > a.collection-card
Robes فساتين div.collections > ul.items-grid > li > a.collection-card
○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
●`[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
●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
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○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
○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.
○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.
○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