Skip to content
https://Yellowizard.gr

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
D
Form Accessibility
Action
4 of 8 controls have issues
FIX
4 of 8 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="s">
Info::
4 control(s) properly labeled
8 controls
4 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optincheckboxΛειτουργικάfor/id
#cmplz-preferences-optincheckboxPreferencesfor/id
#cmplz-statistics-optincheckboxΣτατιστικάfor/id
#cmplz-marketing-optincheckboxΜάρκετινγκfor/id
stext(Type here..)placeholder only
stext(Search...)placeholder only
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">

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

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

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

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

F
404 Error Page
Action
HTTP 500, custom page
FIX
HTTP 500, custom page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 500 ✗Page Title Database Error ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://Yellowizard.gr/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://Yellowizard.gr/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: rgb(255, 222, 16)
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 ModePartial Dark Mode
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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
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
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
1 <nav> landmark(s) 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 NAV MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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
Tap Target Adequacy
Action
7 tap target(s) too small or too close together
REVIEW
7 tap target(s) too small or too close together
Warning::
7 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 25 passed
REVIEW
84

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ntotsikastours – Online Booking Printzio – Eshop Leonidas Pralines – Eshop Sand… div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > div.elementor-loop-container

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 6 div.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 7 div.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet

These items highlight common accessibility best practices.

○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
●`[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
●`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
●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
●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
●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
○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
○Form elements have associated labels
○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.
○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.
A
Heading Hierarchy
44 headings
PASS
44 headings
Warning::
Multiple H1 headings (10 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Κατασκευή ιστοσελίδων - Θεσσαλονίκη
  • H2 Digital Agency στη Θεσσαλονίκη
  • H3 Πρόσφατα έργα
  • H1 Ntotsikastours – Online Booking duplicate H1
  • H1 Printzio – Eshop duplicate H1
  • H1 Leonidas Pralines – Eshop duplicate H1
  • H1 Sandalmania – Eshop duplicate H1
  • H1 Athomer – Website duplicate H1
  • H1 Vasileiadis Marine Eshop duplicate H1
  • H1 Lemassage – Online Booking duplicate H1
  • H1 Limaver – Website duplicate H1
  • H1 Ikoplast – Website duplicate H1
  • H2 ΚΑΤΑΣΚΕΥΗ ΙΣΤΟΣΕΛΙΔΩΝ - ΚΑΤΑΣΚΕΥΗ ESHOP - ΘΕΣΣΑΛΟΝΙΚΗ
  • H3 Υπηρεσίες
  • H4 YELLOWIZARD - ΥΨΗΛΗ ΤΕΧΝΟΓΝΩΣΙΑ ΣΕ ΚΑΘΕ ΕΠΙΠΕΔΟ MARKETING
  • H2 Κατασκευή ιστοσελίδων
  • H2 Κατασκευή eshop
  • H2 S.E.O.
  • H2 Διαχείριση social media
  • H2 Διαφημιστικές καμπάνιες
  • H2 Email Marketing
  • H2 Graphic Design
  • H2 Branding
  • H3 Κλείστε ένα άμεσο ραντεβού μαζί μας!
  • H3 Πως δουλεύουμε
  • H4 4 ΒΗΜΑΤΑ
  • H5 1
  • H6 Ανάλυση αναγκών και στόχων
  • H5 2
  • H6 Σχεδιασμός στρατηγικής
  • H5 3
  • H6 Υλοποίηση ενεργειών
  • H5 4
  • H6 Ανάλυση και αναφορά απόδοσης
  • H4 ΚΑΤΑΣΚΕΥΗ ΙΣΤΟΣΕΛΙΔΩΝ - ESHOP
  • H3 Οδηγούμε την επιχείρησή σας σε σταθερή τροχιά ανόδου.
  • H4 ΣΕ ΤΙ ΔΙΑΦΕΡΟΥΜΕ
  • H4 4 λόγοι για να επικοινωνήσεις μαζί μας.
  • H4 ΜΕΛΕΤΑΜΕ ΣΕ ΒΑΘΟΣ
  • H4 ΕΠΙΤΥΓΧΑΝΟΥΜΕ ΤΟΥΣ ΣΤΟΧΟΥΣ
  • H4 ΕΞΟΙΚΟΝΟΜΟΥΜΕ BUDGET
  • H4 ΕΙΜΑΣΤΕ ΔΙΠΛΑ ΣΤΟΝ ΠΕΛΑΤΗ
  • H3 Γράφουν για εμάς
  • H4 Μας εμπιστεύτηκαν

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Info::
3 heading(s) are too short (≤2 characters) to convey meaning
Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H5: "1" - H5: "2" - H5: "3"
Got: 3 ≤2-char heading(s)
Info::
10 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 10 all-caps heading(s)
A+
Alt Text Quality
1 of 117 images have issues
PASS
1 of 117 images have issues
Warning::
1 image(s) with filename as alt text
Info::
5 decorative image(s) correctly marked
Info::
111 image(s) with good alt text
117 images 111 good alt text 5 decorative 1 generic
IssueCount
filename1 image(s)
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 "s" should use type="search" (currently type="text")
Field name "s" 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-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
3 explicit tabindex attribute(s) checked, no anti-patterns
PASS
3 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 136 visible text node(s) render at >= 12 CSS pixels
PASS
All 136 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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Digital Agency στ…15.71:13.0:1
#000000
#FFDE10
Pass
h2 ΚΑΤΑΣΚΕΥΗ …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Κατασκευή …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Κατασκευή e…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 S.E.O.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Διαχείριση…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Email Marketing21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Graphic Design21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Branding21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Υπηρεσίες21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Κλείστε έν…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Οδηγούμε τ…21.00:13.0:1
#000000
#FFFFFF
Pass
title YelloWizard: Κατ…21.00:14.5:1
#000000
#FFFFFF
Pass
span Αρχική21.00:14.5:1
#000000
#FFFFFF
Pass
span Υπηρεσίες21.00:14.5:1
#000000
#FFFFFF
Pass
span Κατασκευή …21.00:14.5:1
#000000
#FFFFFF
Pass
span Κατασκευή e…21.00:14.5:1
#000000
#FFFFFF
Pass
span Διαχείριση…21.00:14.5:1
#000000
#FFFFFF
Pass
span Διαφημιστι…21.00:14.5:1
#000000
#FFFFFF
Pass
span S.E.O.21.00:14.5:1
#000000
#FFFFFF
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback