Public accessibility assessment

Accessibility issues detected on onestrada.com

Evolize inspected 4 public pages on onestrada.com and detected 23 automatically identifiable accessibility findings.

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

Highest detected severity: Medium · 0 high-priority findings · 80% inspected-page coverage

Most widespread issueTouch targets are too small on mobileDetected on 4 inspected pages
Most affected page/18 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)15 detected findings

Is onestrada.com your website?

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

https://

Not your website? Scan your own site →

01 · Accessibility summary

Evolize inspected 4 public pages on onestrada.com and detected 23 accessibility findings. The most widespread issue was "Touch targets are too small on mobile", detected on 4 inspected pages. The most affected inspected page was "/", where 18 findings were detected. The assessment identified findings mapped to 4 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. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 4 inspected pages · 27 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 targets to at least 24x24px to ensure they are easily accessible by touch. Consider using CSS to adjust the padding or size of the interactive elements.

    View technical evidence →
  2. Medium

    No skip link to main content

    WCAG 2.4.1 (A) · 4 inspected pages · 8 instances
    Why this matters

    The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.

    Recommended action

    Add a skip link at the top of the page that allows users to bypass the navigation and directly access the main content. This link should be visible to screen readers and keyboard users, and should be the first item in the page's tab order.

    View technical evidence →
  3. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 4 inspected pages · 8 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 for the 'Rentals' link to at least 24×24px to make it easier to activate by touch.

    View technical evidence →
  4. Medium

    Touch targets are too small on mobile

    WCAG 2.5.8 (AA) · 3 inspected pages · 12 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 interactive controls to at least 24x24px to make them easier to tap on mobile devices. Consider using CSS to adjust the padding or size of the elements.

    View technical evidence →
  5. Medium

    Hidden elements can still receive keyboard focus

    WCAG 2.4.3 (A) · 1 inspected page · 4 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

    Ensure that all interactive elements are visible when they receive focus, or remove them from the tab order if they are not meant to be interacted with. Consider using CSS to hide elements that should not be focused, or use JavaScript to remove the `tabindex` attribute from elements that should not receive keyboard focus.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA1544 / 4
2.5.8Target Size (Minimum)AA644 / 4
2.4.1Bypass BlocksA144 / 4
2.4.3Focus OrderA111 / 4

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.

04 · All detected findings

Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)60 instances4 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 for the 'Rentals' link to at least 24×24px to make it easier to activate by touch.

View 60 affected elements
Component · Ref 61LZUC
Affected pagehttps://onestrada.com/contact/
Elementheader > div > nav > ul > li:nth-of-type(1) > a
Accessible nameRentals
Markup
<a href="/luxury-car-rental/" class="transition-colors duration-200 hover:text-ink">Rentals</a>
Affected pages/ /contact /inquiry /how-bookings-work
Component · Ref 418U99
Affected pagehttps://onestrada.com/inquiry/
Elementdiv > div:nth-of-type(1) > div:nth-of-type(2) > ul > li:nth-of-type(1) > a
Accessible nameLuxury car rental
Markup
<a href="/luxury-car-rental/" class="transition-colors hover:text-ink"> Luxury car rental </a>
Affected pages/ /contact /inquiry /how-bookings-work
Component · Ref 56185W
Affected pagehttps://onestrada.com/
Elementdiv > ul > li:nth-of-type(1) > article > h3 > a
Accessible nameMonaco Grand Prix
Markup
<a href="/events/monaco-grand-prix/" class="after:absolute after:inset-0 after:content-['']"> Monaco Grand Prix </a>
Affected pages/ /contact /how-bookings-work
Component · Ref JZSM68
Affected pagehttps://onestrada.com/inquiry/
Elementsection#inquiry > div > div > div:nth-of-type(1) > p:nth-of-type(3) > a
Accessible name[email removed]
Markup
<a href="mailto:[email removed]" class="link-underline text-ink" data-astro-cid-v56yoci2="">
[email removed]
</a>
Affected pages/ /inquiry
Component · Ref AR3330
Affected pagehttps://onestrada.com/contact/
Elementmain > section:nth-of-type(3) > div > div > p:nth-of-type(3) > a:nth-of-type(1)
Accessible namehow bookings work
Markup
<a href="/how-bookings-work/" class="underline decoration-mist-strong underline-offset-[0.3em] hover:decoration-ink">how bookings work</a>
Affected pages/contact /how-bookings-work
Component · Ref ISSKR9
Affected pagehttps://onestrada.com/
Elementsection:nth-of-type(3) > div > ul > li:nth-of-type(1) > h3 > a
Accessible nameGrand tour
Markup
<a href="/luxury-car-rental/" class="after:absolute after:inset-0 after:content-['']"> Grand tour </a>
Medium

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)4 instances1 inspected page

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

Ensure that all interactive elements are visible when they receive focus, or remove them from the tab order if they are not meant to be interacted with. Consider using CSS to hide elements that should not be focused, or use JavaScript to remove the `tabindex` attribute from elements that should not receive keyboard focus.

View 4 affected elements
Component · Ref N9PMYY
Affected pagehttps://onestrada.com/inquiry/
Elementdiv > div > div:nth-of-type(2) > div:nth-of-type(2) > p:nth-of-type(3) > a
Accessible name[email removed]
Markup
<a href="mailto:[email removed]" class="link-underline text-ink" data-astro-cid-v56yoci2="">
[email removed]
</a>
Low

Text has insufficient colour contrast

WCAG 1.4.3 (AA)106 instances4 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

Increase the contrast between the text and background colors by adjusting either the text color or the background color to meet the minimum contrast ratio requirements.

View 106 affected elements
Component · Ref G0IAB4
Affected pagehttps://onestrada.com/contact/
Element.inline-block.ease-out.transition-transform
Accessible name
Markup
<span aria-hidden="true" class="inline-block transition-transform duration-200 ease-out group-hover:translate-x-1">
→
</span>
Affected pages/contact /how-bookings-work
Component · Ref O1AHNY
Affected pagehttps://onestrada.com/contact/
Element.h-full:nth-child(1) > article > .justify-between.gap-3.flex > .transition-transform.group-hover\:translate-x-1.text-accent-deep
Accessible name
Markup
<span class="text-accent-deep transition-transform duration-200 group-hover:translate-x-1" aria-hidden="true">
→
</span>
Affected pages/contact /how-bookings-work
Component · Ref CSKFQK
Affected pagehttps://onestrada.com/
Elementsection[aria-label="Featured routes"] > .sm\:py-28.py-20.mx-auto > .gap-6.lg\:grid-cols-3.lg\:gap-7 > .h-full:nth-child(1) > article > .flex-1.p-7.sm\:p-8 > .pt-7.mt-auto.gap-2 > .group-hover\:translate-x-1.text-accent-deep.transition-transform
Accessible name
Markup
<span class="text-accent-deep transition-transform duration-200 group-hover:translate-x-1">
→
</span>
Component · Ref FYF5PM
Affected pagehttps://onestrada.com/
Element.p-6.sm\:p-7.hover\:bg-ivory-warm:nth-child(1) > .justify-between.items-center.flex > .group-hover\:translate-x-0\.5.text-accent-deep.transition-transform
Accessible name
Markup
<span class="text-accent-deep transition-transform duration-200 group-hover:translate-x-0.5" aria-hidden="true">
→
</span>
Component · Ref FBZFZ8
Affected pagehttps://onestrada.com/
Element.hover\:bg-graphite.bg-ink[href$="inquiry/"] > .inline-block.ease-out.group-hover\:translate-x-1
Accessible name
Markup
<span aria-hidden="true" class="inline-block transition-transform duration-200 ease-out group-hover:translate-x-1">
→
</span>
Component · Ref 9942Y0
Affected pagehttps://onestrada.com/inquiry/
Element.transition-transform
Accessible name
Markup
<span aria-hidden="true" class="inline-block transition-transform duration-200 ease-out group-hover:translate-x-1">
→
</span>
Component · Ref HDEUFW
Affected pagehttps://onestrada.com/
Elementa[data-strada-loc="hero_primary"] > .inline-block.ease-out.group-hover\:translate-x-1
Accessible name
Markup
<span aria-hidden="true" class="inline-block transition-transform duration-200 ease-out group-hover:translate-x-1">
→
</span>
Component · Ref 5CNACL
Affected pagehttps://onestrada.com/
Element.h-full:nth-child(1) > .p-6.sm\:p-7[data-qa="related-card"] > .justify-between.gap-3.items-center > .group-hover\:translate-x-1.text-accent-deep.transition-transform
Accessible name
Markup
<span class="text-accent-deep transition-transform duration-200 group-hover:translate-x-1" aria-hidden="true">
→
</span>
Component · Ref H9GY8I
Affected pagehttps://onestrada.com/
Element.max-w-xl > .text-ivory\/80.eyebrow
Accessible nameAcross the network
Markup
<p class="eyebrow text-ivory/80"> Across the network </p>
Component · Ref 3M95C1
Affected pagehttps://onestrada.com/
Element.bg-champagne-dark.hover\:bg-ink[href$="luxury-car-rental/"] > .inline-block.ease-out.group-hover\:translate-x-1
Accessible name
Markup
<span aria-hidden="true" class="inline-block transition-transform duration-200 ease-out group-hover:translate-x-1">
→
</span>
Component · Ref 7GP76A
Affected pagehttps://onestrada.com/
Element.space-y-4.text-ivory\/80.leading-relaxed > p
Accessible nameWherever the trip begins — a terminal stand, a hotel forecourt, a villa gate — the car is prepared, fuelled, and waiting. One concierge sets the meeting point in writing before the day.
Markup
<p>Wherever the trip begins — a terminal stand, a hotel forecourt, a villa gate — the car is prepared, fuelled, and waiting. One concierge sets the meeting point in writing before the day.</p>
Component · Ref BAO9DM
Affected pagehttps://onestrada.com/
Elementli[data-search="italy milan rome lake como"] > .flex-1.p-7.sm\:p-8 > .pt-7.mt-auto.gap-2 > .group-hover\:translate-x-1.text-accent-deep.transition-transform
Accessible name
Markup
<span class="text-accent-deep transition-transform duration-200 group-hover:translate-x-1">
→
</span>
Component · Ref G80SYO
Affected pagehttps://onestrada.com/
Element.h-full:nth-child(7) > article > .flex-1.p-7.sm\:p-8 > .pt-7.mt-auto.gap-2 > .group-hover\:translate-x-1.text-accent-deep.transition-transform
Accessible name
Markup
<span class="text-accent-deep transition-transform duration-200 group-hover:translate-x-1">
→
</span>
Component · Ref 4FKN8V
Affected pagehttps://onestrada.com/
Element.md\:text-\[2\.75rem\].text-ivory
Accessible nameDelivered to hotels, villas, airports, and private addresses across Europe.
Markup
<h2 class="font-display font-normal tracking-tight text-ivory text-3xl leading-tight sm:text-4xl md:text-[2.75rem] mt-5">Delivered to hotels, villas, airports, and private addresses across Europe.</h2>
Component · Ref I42P54
Affected pagehttps://onestrada.com/
Elementli[data-search="italy milan rome lake como"] > .flex-1.p-7.sm\:p-8 > .gap-x-3.gap-y-1\.5.text-\[13px\] > .gap-3:nth-child(1) > .text-mist[aria-hidden="true"]
Accessible name·
Markup
<span class="text-mist" aria-hidden="true">
·
</span>

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.

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