EVOLIZEDIGITAL RISK INTELLIGENCE
RUN FREE ASSESSMENT
RUN FREE ASSESSMENT
Public accessibility assessment

Accessibility issues detected on mobinest.eu

Evolize inspected 5 public pages on mobinest.eu and detected 19 automatically identifiable accessibility findings.

19Findings detected
6WCAG criteria affected
5Pages inspected
23 Aug 2026Assessment date

Highest detected severity: Critical · 3 high-priority findings · 100% inspected-page coverage

Most widespread issueButtons have no accessible nameDetected on 5 inspected pages
Most affected page/19 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)7 detected findings

Is mobinest.eu your website?

Keep this assessment current and get notified when new accessibility issues are detected.

MONITOR THIS WEBSITERUN A FREE ASSESSMENT
https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 5 public pages on mobinest.eu and detected 19 accessibility findings. The most widespread issue was "Buttons have no accessible name", detected on 5 inspected pages. The most affected inspected page was "/", where 19 findings were detected. The assessment identified findings mapped to 6 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.

02 · Start here

These findings combine the highest severity and broadest reach detected during this assessment.

  1. Critical

    Buttons have no accessible name

    WCAG 4.1.2 (A) · 5 inspected pages · 10 instances
    Why this matters

    Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

    Recommended action

    Add a clear and descriptive text or aria-label attribute to the button element to convey its purpose to assistive technology users.

    View technical evidence →
  2. High

    <video> elements must have captions

    WCAG 1.2.2 (A) · 5 inspected pages · 30 instances
    Why this matters

    <video> elements must have captions

    Recommended action

    Add captions to the video element, for example by including a <track> element with a 'kind' attribute set to 'captions' and a 'src' attribute pointing to a caption file.

    View technical evidence →
  3. High

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 5 inspected pages · 25 instances
    Why this matters

    An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

    Recommended action

    To fix this issue, remove the 'hidden' class from the nav element or adjust the CSS so that the element is not focusable when it's not visible. Alternatively, use 'display: none' or 'visibility: hidden' to remove the element from the tab order when it's not visible.

    View technical evidence →
  4. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 5 inspected pages · 30 instances
    Why this matters

    Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

    Recommended action

    Increase the size of the touch target to at least 24x24 pixels to ensure it can be reliably activated by touch.

    View technical evidence →
  5. Medium

    Text has insufficient colour contrast

    WCAG 1.4.3 (AA) · 5 inspected pages · 25 instances
    Why this matters

    Text and background colours do not meet the minimum contrast ratio, reducing legibility.

    Recommended action

    To improve readability, consider increasing the contrast between the text color and background color of the navigation links. You can achieve this by adjusting the CSS classes 'text-muted-foreground' and 'text-foreground' to use colors with a higher contrast ratio.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA755 / 5
2.5.8Target Size (Minimum)AA655 / 5
1.2.2Captions (Prerecorded)A355 / 5
1.1.1Non-text ContentA155 / 5
2.4.3Focus OrderA155 / 5
4.1.2Name, Role, ValueA155 / 5

Absence of a criterion here does not indicate conformance with it — only that no automatically detectable issue was found for it.

Continuous monitoring

A scan shows today's exposure. Monitoring shows what changes next.

Evolize continuously reassesses public website pages, detects newly introduced or recurring accessibility findings, and tracks remediation over time.

MONITOR MOBINEST.EUSEE PRICING

04 · All detected findings

Critical

Buttons have no accessible name

WCAG 4.1.2 (A)10 instances5 inspected pages

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Why it matters

Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.

Recommended correction

Add a clear and descriptive text or aria-label attribute to the button element to convey its purpose to assistive technology users.

View 10 affected elements
Component · Ref RYV4KN
Affected pagehttps://www.mobinest.eu/
Element.pr-2
Accessible nameChoose your profile
Rolecombobox
Markup
<button type="button" role="combobox" aria-expanded="false" aria-autocomplete="none" dir="ltr" data-state="closed" data-placeholder="" data-slot="select-trigger" data-size="default" class="flex items-center ju...">
Affected pages/ /de /es /fr /ca
High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)25 instances5 inspected pages

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Why it matters

An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.

Recommended correction

To fix this issue, remove the 'hidden' class from the nav element or adjust the CSS so that the element is not focusable when it's not visible. Alternatively, use 'display: none' or 'visibility: hidden' to remove the element from the tab order when it's not visible.

View 25 affected elements
Component · Ref AOMOUJ
Affected pagehttps://www.mobinest.eu/
Elementhtml > body > header > div > nav > a:nth-of-type(1)
Accessible nameWhat it is
Markup
<a href="#what" class="rounded-md px-3 py-2 text-sm text-muted-foreground transition-colors hover:text-foreground">What it is</a>
Affected pages/ /de /es /fr /ca
High

<video> elements must have captions

WCAG 1.2.2 (A)30 instances5 inspected pages

<video> elements must have captions

Why it matters

<video> elements must have captions

Recommended correction

Add captions to the video element, for example by including a <track> element with a 'kind' attribute set to 'captions' and a 'src' attribute pointing to a caption file.

View 30 affected elements
Component · Ref XSHKSO
Affected pagehttps://www.mobinest.eu/
Elementvideo[poster="/img/seq-1-trail.jpg"]
Markup
<video class="h-full w-full object-cover" poster="/img/seq-1-trail.jpg" autoplay="" muted="" loop="" playsinline="" preload="metadata"><source src="/video/seq-trail.mp4" type="video/mp4"></video>
Affected pages/ /de /es /fr /ca
Medium

Text has insufficient colour contrast

WCAG 1.4.3 (AA)85 instances5 inspected pages

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Why it matters

Text and background colours do not meet the minimum contrast ratio, reducing legibility.

Recommended correction

To improve accessibility, consider increasing the contrast between the text color and the background color. You can do this by changing the text color to a darker or lighter shade, or by adding a background image or color with sufficient contrast. For example, you could change the text color from #ffffff (white) with an opacity of 85% to a darker gray or black color.

View 85 affected elements
Component · Ref FQXESO
Affected pagehttps://www.mobinest.eu/
Element.max-w-xl
Accessible nameA modular architecture integrating transport, transformation and sleeping comfort in one compact system designed for travel and good rest.
Markup
<p class="mt-6 max-w-xl text-lg leading-relaxed text-white/85">A modular architecture integrating transport, transformation and sleeping comfort in one compact system designed for travel and good rest.</p>
Affected pages/ /de /es /fr /ca
Component · Ref L6KJVU
Affected pagehttps://www.mobinest.eu/
Elementh1
Accessible nameSleep like you’re at home. Wake up anywhere.
Markup
<h1 class="accent-line mt-7 text-balance text-4xl font-semibold leading-[1.05] tracking-tight sm:text-6xl md:text-7xl">Sleep like you’re at home.<!-- --> <em class="text-white/90">Wake up anywhere.</em></h1>
Affected pages/ /de /es /fr /ca
Component · Ref CD5E3S
Affected pagehttps://www.mobinest.eu/
Element.text-white\/90
Accessible nameWake up anywhere.
Markup
<em class="text-white/90">Wake up anywhere.</em>
Affected pages/ /de /es /fr /ca
Component · Ref J7E6YT
Affected pagehttps://www.mobinest.eu/
Element.\[a\]\:hover\:bg-muted
Accessible nameFinalist · Eurobike Award 2026
Markup
<span data-slot="badge" data-variant="outline" class="group/badge inline-f...">
Affected pages/ /de /es /fr /ca
Component · Ref O2O8ZB
Affected pagehttps://www.mobinest.eu/
Element.h-16 > .gap-2[aria-label="MOBINEST"][href="/"] > .text-base.font-semibold.tracking-tight
Accessible nameMOBINEST®
Markup
<span class="text-base font-semibold tracking-tight">MOBINEST<sup class="ml-0.5 text-[0.42em] font-medium leading-none">®</sup></span>
Affected pages/ /de /es /fr /ca
Component · Ref 4S4Q62
Affected pagehttps://www.mobinest.eu/
Element.bg-white\/5
Accessible nameHow it works
Markup
<a href="#sequence" data-slot="button" data-variant="outline" data-size="lg" class="group/button inline-...">
Affected pages/ /de /es /fr /ca
Component · Ref 8JUR2R
Affected pagehttps://www.mobinest.eu/
Element.px-3.rounded-md[href$="#what"]
Accessible nameWhat it is
Markup
<a href="#what" class="rounded-md px-3 py-2 text-sm text-muted-foreground transition-colors hover:text-foreground">What it is</a>
Affected pages/ /de /es /fr /ca
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)55 instances5 inspected pages

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Why it matters

Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.

Recommended correction

Increase the size of the touch target to at least 24x24px to ensure it can be easily activated by touch. Consider adding padding or increasing the font size of the interactive element.

View 55 affected elements
Component · Ref J8QKN2
Affected pagehttps://www.mobinest.eu/
Elementbody > footer > div > div:nth-of-type(1) > div:nth-of-type(3) > a
Accessible name[email removed]
Markup
<a href="mailto:[email removed]" class="text-sm text-muted-foreground transition-colors hover:text-foreground">[email removed]</a>
Affected pages/ /de /es /fr /ca
Component · Ref JK5LL6
Affected pagehttps://www.mobinest.eu/
Elementdiv > div:nth-of-type(2) > form > div:nth-of-type(2) > div:nth-of-type(2) > select
Accessible nameDistributor / retailerTour operator / campsiteInvestorPress / mediaIndividual customerOther
Markup
<select aria-hidden="true" tabindex="-1" name="role" style="position: absolute; border: 0px; width: 1px; height: 1px; padding: 0px; margin: -1px; overflow: hidden; clip: rect(0px, 0px, 0px, 0px); white-space: nowrap; overflow-wrap: normal;"><option value="" selected=""></option><option value="Distributor / retailer">Distributor / retailer</option><option value="Tour operator / campsite">Tour operator / campsite</option><option value="Investor">Investor</option><option value="Press / media">Press / media</option><option value="Individual customer">Individual customer</option><option value="Othe…
Affected pages/ /de /es /fr /ca
Component · Ref Q7WAD5
Affected pagehttps://www.mobinest.eu/
Elementhtml > body > a
Accessible nameSkip to content
Markup
<a href="#main" class="sr-only focus:not-sr-only focus:fixed focus:left-4 focus:top-4 focus:z-[200] focus:rounded-md focus:bg-primary focus:px-4 focus:py-2 focus:text-primary-foreground">Skip to content</a>
Affected pages/ /de /es /fr /ca
Component · Ref LF8S5U
Affected pagehttps://www.mobinest.eu/
Elementhtml > body > footer > div > div:nth-of-type(3) > a
Accessible nameBack to top
Markup
<a href="#top" class="inline-flex items-center gap-1.5 transition-colors hover:text-foreground">Back to top<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-arrow-up h-3.5 w-3.5" aria-hidden="true"><path d="m5 12 7-7 7 7"></path><path d="M12 19V5"></path></svg></a>
Affected pages/ /de /es /fr /ca
Component · Ref 4P51IZ
Affected pagehttps://www.mobinest.eu/
Elementsection#contact > div > div:nth-of-type(1) > a
Accessible name[email removed]
Markup
<a href="mailto:[email removed]" class="mt-6 inline-block text-sm font-medium underline-offset-4 hover:underline">[email removed]</a>
Affected pages/ /de /es /fr /ca
Component · Ref FHJBME
Affected pagehttps://www.mobinest.eu/
Elementdiv > div:nth-of-type(1) > div:nth-of-type(2) > ul > li:nth-of-type(1) > a
Accessible nameWhat it is
Markup
<a href="#what" class="text-sm text-muted-foreground transition-colors hover:text-foreground">What it is</a>
Affected pages/ /de /es /fr /ca
Medium

Video may be missing captions

WCAG 1.2.2 (A)30 instances5 inspected pages

A video element has no captions or subtitles track. Whether captions are needed depends on the audio content and requires manual review.

Why it matters

A video element has no captions or subtitles track. Whether captions are needed depends on the audio content and requires manual review.

Recommended correction

Add captions or subtitles track to the video element, if the video contains audio content essential for understanding. This can be achieved by adding a 'track' element with a 'kind' attribute set to 'captions' or 'subtitles' and a 'src' attribute pointing to the caption file.

View 30 affected elements
Component · Ref IZANR1
Affected pagehttps://www.mobinest.eu/
Elementsection#gallery > div:nth-of-type(1) > div:nth-of-type(2) > div:nth-of-type(1) > div > video
Markup
<video class="h-full w-full object-cover" poster="/video/mobinest-camp.jpg" controls="" preload="none" playsinline=""><source src="/video/mobinest-camp.mp4" type="video/mp4"></video>
Affected pages/ /de /es /fr /ca
Component · Ref P3FQCI
Affected pagehttps://www.mobinest.eu/
Elementdiv > div:nth-of-type(2) > div > figure:nth-of-type(1) > div > video
Markup
<video class="h-full w-full object-cover" poster="/img/seq-1-trail.jpg" autoplay="" muted="" loop="" playsinline="" preload="metadata"><source src="/video/seq-trail.mp4" type="video/mp4"></video>
Affected pages/ /de /es /fr /ca
Low

Low-quality alternative text

WCAG 1.1.1 (A)100 instances5 inspected pages

Alt text looks like a filename, a generic word ("image", "photo"), or is duplicated across unrelated images — it likely does not describe the content.

Why it matters

Alt text looks like a filename, a generic word ("image", "photo"), or is duplicated across unrelated images — it likely does not describe the content.

Recommended correction

Update the alt text for images to provide a clear description of the content, rather than using generic phrases like 'In real conditions'. This will help users who rely on screen readers to understand the context and meaning of the images.

View 100 affected elements
Component · Ref 100RN6
Affected pagehttps://www.mobinest.eu/
Elementdiv > div:nth-of-type(1) > div > div:nth-of-type(1) > div > img
Markup
<img alt="In real conditions" loading="lazy" decoding="async" data-nimg="fill" class="object-cover" style="position:absolute;height:100%;width:100%;left:0;top:0;right:0;bottom:0;color:transparent" sizes="(max-width:640px) 75vw, (max-width:1024px) 50vw, 33vw" srcset="/_next/image?url=%2Fimg%2Fgallery%2Fg01.jpg&amp;w=256&amp;q=75 256w, /_next/image?url=%2Fimg%2Fgallery%2Fg01.jpg&amp;w=384&amp;q=75 384w, /_next/image?url=%2Fimg%2Fgallery%2Fg01.jpg&amp;w=640&amp;q=75 640w, /_next/image?url=%2Fimg%2Fgallery%2Fg01.jpg&amp;w=750&amp;q=75 750w, /_next/image?url=%2Fimg%2Fgallery%2Fg01.jpg&amp;w=828&amp…
Affected pages/ /de /es /fr /ca

05 · Most affected inspected pages

06 · About this assessment

Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.

  • Publicly accessible surfaces only — no credentials, private systems, or source-code access.
  • Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
  • Results reflect the site at the scan date and may have changed since.

Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment

07 · Continuous monitoring

This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.

MONITOR THIS WEBSITESEE PRICING

Is information in this report inaccurate or outdated? Request a correction or removal.