Public accessibility assessment

Accessibility issues detected on ionian-ilios.com

Evolize inspected 5 public pages on ionian-ilios.com and detected 28 automatically identifiable accessibility findings.

28Findings detected
8WCAG criteria affected
5Pages inspected
23 Aug 2026Assessment date

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

Most widespread issueLinks lack accessible textDetected on 5 inspected pages
Most affected page/23 findings detected
Most represented WCAG criterionWCAG 1.4.3 — Contrast (Minimum)10 detected findings

Is ionian-ilios.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 5 public pages on ionian-ilios.com and detected 28 accessibility findings. The most widespread issue was "Links lack accessible text", detected on 5 inspected pages. The most affected inspected page was "/", where 23 findings were detected. The assessment identified findings mapped to 8 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) · 1 inspected page · 6 instances
    Why this matters

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

    Recommended action

    Add a text label or aria-label attribute to each button to describe its purpose, ensuring that assistive technology can announce the button's function to users.

    View technical evidence →
  2. Critical

    Embedded frames lack descriptive titles

    WCAG 4.1.2 (A) · 1 inspected page · 2 instances
    Why this matters

    An <iframe> has no title, so its purpose is not announced to assistive technology.

    Recommended action

    Add a concise title attribute that describes the frame's actual purpose — for example "Store locator" for a location search or "Promotional campaign" for a marketing embed. The affected frame loads https://www.google.c..., which can help identify its purpose. Avoid generic values such as "Embedded content", "iframe", or "frame".

    View technical evidence →
  3. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 2 instances
    Why this matters

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    This link's only content is an image with no text alternative. Provide meaningful alternative text on the linked image (its alt attribute) that identifies the link's destination or purpose. The link points to /fr.

    View technical evidence →
  4. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 2 instances
    Why this matters

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    Add accessible text to the link, such as the logo text, or provide an alternative text description for screen reader users. For example, add a span element with the text 'Ionian Ilios Logo' inside the link: <a href="/el" class="logo-link"><span>Ionian Ilios Logo</span> <img src="/static/assets/Logo_512x512.png" alt="Ionian Ilios Logo" role="presentation" loading="lazy"></a>

    View technical evidence →
  5. Critical

    Links lack accessible text

    WCAG 2.4.4 (A) · 1 inspected page · 2 instances
    Why this matters

    Links expose no accessible name, so their destination is unknown to screen reader users.

    Recommended action

    This link's only content is an image with no text alternative. Provide meaningful alternative text on the linked image (its alt attribute) that identifies the link's destination or purpose. The link points to /en.

    View technical evidence →

03 · WCAG criteria affected

CriterionNameLevelFindingsPagesReach
1.4.3Contrast (Minimum)AA1055 / 5
2.4.4Link Purpose (In Context)A555 / 5
2.5.8Target Size (Minimum)AA555 / 5
2.4.3Focus OrderA355 / 5
4.1.2Name, Role, ValueA211 / 5
1.2.2Captions (Prerecorded)A111 / 5
1.3.1Info and RelationshipsA155 / 5
2.4.1Bypass BlocksA155 / 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.

04 · All detected findings

Critical

Buttons have no accessible name

WCAG 4.1.2 (A)6 instances1 inspected page

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 text label or aria-label attribute to each button to describe its purpose, ensuring that assistive technology can announce the button's function to users.

View 6 affected elements
Component · Ref 8VL2C8
Affected pagehttps://ionian-ilios.com/
Elementbutton[data-slide="0"]
Markup
<button class="bullet active" data-slide="0"></button>
Critical

Embedded frames lack descriptive titles

WCAG 4.1.2 (A)2 instances1 inspected page

An <iframe> has no title, so its purpose is not announced to assistive technology.

Why it matters

An <iframe> has no title, so its purpose is not announced to assistive technology.

Recommended correction

Add a concise title attribute that describes the frame's actual purpose — for example "Store locator" for a location search or "Promotional campaign" for a marketing embed. The affected frame loads https://www.google.c..., which can help identify its purpose. Avoid generic values such as "Embedded content", "iframe", or "frame".

View 2 affected elements
Component · Ref C0LWJT
Affected pagehttps://ionian-ilios.com/
Elementiframe
Markup
<iframe src="https://www.google.c..." allowfullscreen="" loading="lazy" referrerpolicy="no-referrer-when-dow...">
High

Text has insufficient colour contrast

WCAG 1.4.3 (AA)37 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 fix this issue, increase the contrast between the text and background colors. You can do this by changing the text color, background color, or both, to meet the minimum contrast ratio thresholds as defined in WCAG 2.1 SC 1.4.3. A contrast ratio of at least 4.5:1 for normal text is recommended.

View 37 affected elements
Component · Ref 62FKQ5
Affected pagehttps://ionian-ilios.com/
Element.disabled > span:nth-child(1)
Accessible nameFunctional (Always active)
Markup
<span>Functional (Always active)</span>
Affected pages/ /en/about /en/contact /el/contact /fr/contact
Component · Ref WJEPMD
Affected pagehttps://ionian-ilios.com/en/contact
Element#cookie-consent > p:nth-child(2)
Accessible nameTo provide the best experience, we use technologies like cookies to store and/or access device information.
Markup
<p>To provide the best experience, we use technologies like cookies to store and/or access device information. </p>
Affected pages/ /en/about /en/contact /el/contact /fr/contact
Component · Ref 6F7IBC
Affected pagehttps://ionian-ilios.com/
Elementh1
Accessible nameDiscover the true meaning of mediterranean living.
Markup
<h1 class="index-hero-heading">Discover the <br>true meaning of <br>mediterranean living.</h1>
Component · Ref QJC53E
Affected pagehttps://ionian-ilios.com/
Element.index-hero-scroll
Accessible nameMore ↓
Markup
<div class="index-hero-scroll" tabindex="0">More ↓</div>
Component · Ref MLJN9Z
Affected pagehttps://ionian-ilios.com/
Element.next
Accessible name
Markup
<button class="arrow next">❯</button>
Component · Ref M2Q83Y
Affected pagehttps://ionian-ilios.com/
Element.btn-primary-header
Accessible nameReservations
Markup
<a href="/en/contact" class="btn-primary-header">Reservations</a>
Component · Ref 89FKP9
Affected pagehttps://ionian-ilios.com/
Element#suite-epano > article > .suite-overlay > h3
Accessible nameEpano
Markup
<h3>Epano</h3>
Component · Ref A7GIKU
Affected pagehttps://ionian-ilios.com/
Element.prev
Accessible name
Markup
<button class="arrow prev">❮</button>
Component · Ref UPH7X3
Affected pagehttps://ionian-ilios.com/
Element#suite-epano > article > .suite-overlay > p
Accessible nameElevated living designed for calm, privacy, and seamless indoor-outdoor flow.
Markup
<p>Elevated living designed for calm, privacy, and seamless indoor-outdoor flow.</p>
Component · Ref VOIL3G
Affected pagehttps://ionian-ilios.com/en/about
Elementlabel[for="cookie-statistics"] > .cookie-toggle-label
Accessible nameEnable Statistics
Markup
<span class="cookie-toggle-label">Enable Statistics</span>
High

Hidden elements can still receive keyboard focus

WCAG 2.4.3 (A)65 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, you should remove the hidden element from the tab order or make it visible when focused. You can achieve this by adding the 'tabindex="-1"' attribute to the element or by adjusting its CSS to make it visible when focused.

View 65 affected elements
Component · Ref RH9E6X
Affected pagehttps://ionian-ilios.com/en/contact
Elementbutton#scrollToTop
Accessible name
Markup
<button id="scrollToTop" class="scroll-top-btn">↑</button>
Affected pages/ /en/about /en/contact /el/contact /fr/contact
Component · Ref WMJ4HK
Affected pagehttps://ionian-ilios.com/
Elementnav#mainNav > a:nth-of-type(1)
Accessible nameHome
Markup
<a href="/en">Home</a>
Affected pages/ /en/about /en/contact /el/contact /fr/contact
Component · Ref OX7CFK
Affected pagehttps://ionian-ilios.com/
Elementinput#cookie-preferences
Markup
<input type="checkbox" id="cookie-preferences" data-cookie="preferences">
Affected pages/ /en/about /en/contact /el/contact /fr/contact
Medium

Content sits outside any landmark region

WCAG 1.3.1 (A)10 instances5 inspected pages

Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.

Why it matters

Meaningful content is not contained in a landmark (header/nav/main/footer/aside), so assistive-technology users cannot reach it via landmark navigation.

Recommended correction

Wrap the content in a landmark region such as a 'main' or 'section' element to enable assistive technology users to navigate to it via landmark navigation. For example: <main><p class="construction-popup-text">Summer rates now available. Contact us for availability, and prices.</p></main>

View 10 affected elements
Component · Ref 6KHVA8
Affected pagehttps://ionian-ilios.com/en/contact
Elementdiv#cookie-consent > p:nth-of-type(1)
Accessible nameTo provide the best experience, we use technologies like cookies to store and/or access device information.
Markup
<p>To provide the best experience, we use technologies like cookies to store and/or access device information. </p>
Affected pages/ /en/about /en/contact /el/contact /fr/contact
Medium

Touch targets are too small on mobile

WCAG 2.5.8 (AA)51 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 touch target size of the 'Legal' link to at least 24x24px to make it easier for users to activate by touch on mobile devices. Consider adding padding or increasing the font size of the link text to achieve this minimum size.

View 51 affected elements
Component · Ref SW84E3
Affected pagehttps://ionian-ilios.com/
Elementnav#mainNav > p > a:nth-of-type(1)
Accessible nameLegal
Markup
<a href="/en/legal">Legal</a>
Affected pages/ /en/about /en/contact /el/contact /fr/contact
Component · Ref BW13GJ
Affected pagehttps://ionian-ilios.com/
Elementbody > footer > div > div:nth-of-type(2) > p:nth-of-type(1) > a:nth-of-type(1)
Accessible nameLegal
Markup
<a href="/en/legal">Legal</a>
Affected pages/ /en/about /en/contact /el/contact /fr/contact
Component · Ref 5O7GCG
Affected pagehttps://ionian-ilios.com/
Elementhtml > body > section > div:nth-of-type(3) > button
Accessible namePause background video
Markup
<button class="video-pause" aria-label="Pause background video">||</button>
Component · Ref GHPT46
Affected pagehttps://ionian-ilios.com/
Elementsection#reservations-click > div:nth-of-type(1) > a
Accessible nameDiscover more
Markup
<a href="https://lefkadaslowguide.gr/en/" class="btn-experiences" target="_blank" rel="noopener noreferrer">Discover more</a>
Medium

Touch targets are too small

WCAG 2.5.8 (AA)20 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 this <a>'s rendered area to at least 24 × 24 CSS pixels, or provide sufficient spacing from adjacent targets. Prefer increasing padding on the existing control (for example the button or link) rather than adding a separate non-interactive wrapper.

View 20 affected elements
Component · Ref Y88L6E
Affected pagehttps://ionian-ilios.com/en/contact
Element.small-text:nth-child(1) > a[href$="legal"]
Accessible nameLegal
Markup
<a href="/en/legal">Legal</a>
Affected pages/ /en/about /en/contact /el/contact /fr/contact
Low

Video may be missing captions

WCAG 1.2.2 (A)6 instances1 inspected page

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 to the video, or provide an alternative way for users to access the audio content, such as a transcript.

View 6 affected elements
Component · Ref RSDHS6
Affected pagehttps://ionian-ilios.com/
Elementhtml > body > section > div:nth-of-type(1) > video:nth-of-type(1)
Markup
<video class="slide active" autoplay="" muted="" loop="" playsinline="" aria-hidden="true" poster="/static/assets/pesoules.jpg" preload="auto">
                <source src="/static/assets/Villa-A_Outdoors-1-min-movie.mp4" type="video/mp4">
            </video>

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.