Skip to content
https://enjoycbd.es

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
5
REVIEW
9
PASS
10
INFO
0
Checks
24
10 PASS 9 REVIEW 5 FIX
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::
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)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
9 landmarks
REVIEW
9 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 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

C
Heading Hierarchy
Action
30 headings, 1 skip(s)
REVIEW
30 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 CBD premium en España. productos que marcan la diferencia
  • H2 Calidad real en cada producto.
  • H2 Todos Nuestros Productos
  • H2 TOP ventas
  • H2 Static - 2g
  • H2 Piatella - 2g
  • H2 Orange Scar - 10g
  • H2 Amnesia Toad - 5g
  • H2 packs ahorro
  • H2 Pack Sweet Selection
  • H2 Pack Power Mix
  • H2 Pack Golden Selection
  • H2 Pack Full Experience
  • H2 Guía rápida Para elegir tu CBD ideal
  • H2 Si tienes dudas sobre qué producto se adapta mejor a ti, aquí te dejamos algunos consejos útiles.
  • H3 Relájate, ¡Pero con descuentos!
  • H2 Suscríbete y llévate un 10% en tu primer pedido.
  • H2 Descubre Nuestras Ventajas
  • H2 Nuestra comunidad: ¿Por qué nos prefieren?
  • H2 tienda de cbd en españa de alta calidad
  • H2 Check out our blog
  • H2 What makes Piatella-type hash special?
  • H2 How to choose your first CBD flower without making a mistake
  • H2 CBD and nighttime routine: how to create your relaxation time
  • H2 What makes a resin have a creamy or dry texture?
  • H4 About Us skipped
  • H4 Our Products
  • H4 Our Policies
  • H2 Age Verification
  • H2 The content of this site is for sale exclusively to people over 18 years of age.

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

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

B
Alt Text Quality
4 of 53 images have issues
REVIEW
4 of 53 images have issues
Warning::
4 image(s) with filename as alt text
Info::
10 decorative image(s) correctly marked
Info::
39 image(s) with good alt text
53 images 39 good alt text 10 decorative 4 generic
IssueCount
filename4 image(s)
C
Form Accessibility
Action
5 of 8 controls have issues
REVIEW
5 of 8 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">
Info::
3 control(s) properly labeled
8 controls
3 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#form-field-nametextNombrefor/id
#form-field-emailemailEmailfor/id
selectselectLanguage Translate Widgetaria-label
#goog-gt-votingInputSrcLangtext(none)none
#goog-gt-votingInputTrgLangtext(none)none
#goog-gt-votingInputSrcTexttext(none)none
#goog-gt-votingInputTrgTexttext(none)none
#goog-gt-votingInputVotetext(none)none

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

<input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

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

B
Tabindex Anti-Patterns
0 positive, 4 -1-on-focusable
REVIEW
0 positive, 4 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-730890942">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-730890943">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-730890944">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-730890945">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
B
Iframe Accessibility
2/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/4 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="")
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.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Calidad real en cada producto.
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Static - 2g
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Piatella - 2g
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Orange Scar - 10g
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Amnesia Toad - 5g
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pack Sweet Selection
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pack Power Mix
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pack Golden Selection
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Pack Full Experience
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Si tienes dudas sobre qué producto se a…
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 aquí te dejamos algunos consejos útile…
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Suscríbete y llévate un 10% en tu prim…
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Relájate,
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ¡Pero con descuentos!
1.01:1
#000000
on
#020202
needs 3.0:1 (large text)
19px · bottom of viewport
title Buy CBD Online | Enjoy CBD: Premium Flow…
1.01:1
#000000
on
#020202
needs 4.5:1 (normal text)
16px · top of page (header area)
a Ir al contenido
1.01:1
#000000
on
#020202
needs 4.5:1 (normal text)
16px · top of page (header area)
span Flores
1.01:1
#000000
on
#020202
needs 4.5:1 (normal text)
16px · top of page (header area)
span Resinas
1.01:1
#000000
on
#020202
needs 4.5:1 (normal text)
16px · top of page (header area)
span Aceites
1.01:1
#000000
on
#020202
needs 4.5:1 (normal text)
16px · above the fold
span Vaper
1.01:1
#000000
on
#020202
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Calidad real en cada…1.01:13.0:1
#000000
#020202
Fail
h2 Static - 2g1.01:13.0:1
#000000
#020202
Fail
h2 Piatella - 2g1.01:13.0:1
#000000
#020202
Fail
h2 Orange Scar - 10g1.01:13.0:1
#000000
#020202
Fail
h2 Amnesia Toad - 5g1.01:13.0:1
#000000
#020202
Fail
h2 Pack Sweet Selection1.01:13.0:1
#000000
#020202
Fail
h2 Pack Power Mix1.01:13.0:1
#000000
#020202
Fail
h2 Pack Golden Selectio…1.01:13.0:1
#000000
#020202
Fail
h2 Pack Full Experience1.01:13.0:1
#000000
#020202
Fail
h2 Si tienes dudas sobr…1.01:13.0:1
#000000
#020202
Fail
h2 aquí te dejamos alg…1.01:13.0:1
#000000
#020202
Fail
h2 Suscríbete y lléva…1.01:13.0:1
#000000
#020202
Fail
h3 Relájate,1.01:13.0:1
#000000
#020202
Fail
h3 ¡Pero con descuento…1.01:13.0:1
#000000
#020202
Fail
title Buy CBD Online | Enj…1.01:14.5:1
#000000
#020202
Fail
a Ir al contenido1.01:14.5:1
#000000
#020202
Fail
span Flores1.01:14.5:1
#000000
#020202
Fail
span Resinas1.01:14.5:1
#000000
#020202
Fail
span Aceites1.01:14.5:1
#000000
#020202
Fail
span Vaper1.01:14.5:1
#000000
#020202
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.

A+
Heading Text Quality
All 30 heading(s) have substantive, well-formed text
PASS
All 30 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "query" should use type="search" (currently type="text")
Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
8 form control(s) checked, no input-semantic issues
PASS
8 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+
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 81 visible text node(s) render at >= 12 CSS pixels
PASS
All 81 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 93/100 — 3 failing, 28 passed
PASS
93

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
Flowers button#e-n-tab-title-730890941 > span.e-n-tab-title-text > font > font

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
About Us div.heading > div.sub-style > div.head-title > h4.heading-title

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.e-con-inner > div.elementor-element > div.elementor-element > a div.e-con-inner > div.elementor-element > div.elementor-element > a
div.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-element > div.elementor-icon-wrapper > a.elementor-icon

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]`s are contained by their required parent element
●`[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
●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
●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.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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.
○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