Skip to content
https://www.orthopedic-store.gr

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
75
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
D
Heading Hierarchy
Action
56 headings, 2 skip(s)
FIX
56 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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 Το προϊόν προστέθηκε με επιτυχία στο καλάθι αγορών σας
  • H2 Υπάρχουν 0 αντικείμενα στο καλάθι σας. Υπάρχει ένα προϊόν στο καλάθι σας.
  • H5 Αμαξίδιο Μεταφορας MULTI-XTR skipped
  • H5 Αερόστρωμα Κατάκλισης Κυψελωτό
  • H5 Συσκευή Λεμφικού Μασάζ- Πρεσσοθεραπείας...
  • H5 Κηδεμόνας Σκολίωσης-Κύφωσης τύπου Boston
  • H5 Σύστημα Ανάβασης Σκάλας Liftkar PT S 130
  • H5 Συσκευή Λεμφικού Μασάζ-Πρεσσοθεραπείας Άνω...
  • H5 Σύστημα Ανάβασης Σκάλας LIFTKAR PTR 130
  • H5 Σύστημα Ανάβασης Σκάλας Liftkar PT...
  • H5 Σύστημα Ανάβασης Σκάλας Liftkar PT S 130
  • H5 Παιδικό Ηλεκτροκίνητο Αμαξίδιο SCRUBBY
  • H5 Ηλεκτρικό Αμαξίδιο Meyra iTravel Carbon
  • H5 Σύστημα Ανάβασης Σκάλας LIFTKAR PTR 130
  • H5 Ηλεκτρικό Αμαξίδιο Meyra iTravel 1054
  • H5 Ηλεκτροκίνητο Αδιπλούμενο Αμαξίδιο BBR...
  • H5 Χειροκίνητο Αμαξίδιο Ορθοστάτης HI-LO M...
  • H5 Ηλεκτροκίνητο & αναδιπλούμενο αμαξίδιο...
  • H5 Ηλεκτροκίνητο Αναπηρικό Αμαξίδιο...
  • H5 Πτυσσόμενο Ηλεκτροκίνητο Αμαξίδιο TINY
  • H5 Ηλεκτροκίνητο Αναπηρικό Αμαξίδιο...
  • H5 Ποδήλατο Τετραπληγίας Κάτω Άκρων...
  • H5 Παιδικό Χειροκίνητο Αμαξίδιο CORZO...
  • H5 Αμαξίδιο Αλουμινίου Ειδικού Τύπου MEYRA...
  • H5 Πτυσσόμενο Ηλεκτροκίνητο Αμαξίδιο EASY WAY...
  • H5 Ηλεκτροκίνητο Αναπηρικό Αμαξίδιο με...
  • H5 ΝΕΟ Ηλεκτροκίνητο Πτυσσόμενο Αμαξίδιο...
  • H5 Αμαξίδιο Ηλεκτροκίνητο Πτυσσόμενο YUWELL
  • H5 Πλήρες Πακέτο Κατοίκον Νοσηλείας
  • H5 Παιδικό Χειροκίνητο Αμαξίδιο DIXIE PLUS
  • H5 Παιδικό Αμαξίδιο MAMALU RED
  • H5 Αναπηρικό Αμαξίδιο BREEZY Style Standard...
  • H5 Νέος Ηλεκτρικός Γερανός Μεταφοράς Ασθενών...
  • H5 Συσκευή Λεμφικού Μασάζ-Πρεσσοθεραπείας...
  • H5 Συσκευή Λεμφικού Μασάζ-Πρεσσοθεραπείας...
  • H5 Συσκευή Λεμφικού Μασάζ-Πρεσσοθεραπείας Άνω...
  • H5 Συσκευή Λεμφικού Μασάζ- Πρεσσοθεραπείας...
  • H5 Συσκευή Λεμφικού Μασάζ- Πρεσσοθεραπείας...
  • H5 Ηλεκτρικός Γερανός Ανύψωσης Ασθενών LIFTY...
  • H5 Νέος Ηλεκτρικός Γερανός Μεταφοράς Ασθενών...
  • H5 Συσκευή Λεμφικού Μασάζ-Πρεσσοθεραπείας...
  • H5 Αναπηρικό Αμαξίδιο ECONOMY TRANSIT Μαύρο...
  • H5 Αναπηρικό αμαξίδιο Wheel Economy Πλάτος...
  • H5 Νέο Αδιάβροχο Αμαξίδιο Μπάνιου COMMODE CHAIR
  • H5 Πελματογράφημα και Κατασκευή Πελμάτων
  • H5 Περιπατητήρας Πτυσσόμενος με Βοήθεια στο...
  • H5 Μαξιλάρι Ανατομικό memory foam
  • H5 Μαξιλάρι Ανατομικό Visco
  • H3 Αποστολές σε ολόκληρη την Ελλάδα
  • H3 Υποστήριξη πελατών
  • H3 Ασφαλείς συναλλαγές
  • H2 Ορθοπεδικά και ιατρικά είδη στις καλύτερες τιμές.
  • H4 Πληροφορίες Καταστήματος skipped
  • H4 Πληροφορίες
  • H4 Ο λογαριασμός μου
  • H4 Aκολουθήστε μας

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

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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::
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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

B
Alt Text Quality
26 of 90 images have issues
REVIEW
26 of 90 images have issues
Warning::
26 image(s) with generic alt text
Info::
1 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
61 image(s) with good alt text
90 images 61 good alt text 2 decorative 26 generic
IssueCount
generic26 image(s)
too long1 image(s)
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 error - www.orthopedic-store.gr ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Ορθοπεδικά - ιατρικά ε…
1.14:1
#000000
on
#141414
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Σύνδεση
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area)

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Το προϊόν π…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
h3 Ασφαλείς σ…21.00:13.0:1
#000000
#FFFFFF
Pass
title Ορθοπεδικά…1.14:14.5:1
#000000
#141414
Fail
a Σύνδεση1.66:14.5:1
#000000
#333333
Fail
a Επικοινωνή…9.36:14.5:1
#000000
#ADADAD
Pass
span Καλέστε μα…21.00:14.5:1
#000000
#FFFFFF
Pass
strong 210 7782835 6955-787…21.00:13.0:1
#000000
#FFFFFF
Pass
span Αναζήτηση21.00:14.5:1
#000000
#FFFFFF
Pass
b Καλάθι:21.00:13.0: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
p Κανένα προ…21.00:14.5:1
#000000
#FFFFFF
Pass
span To be determined21.00:14.5:1
#000000
#FFFFFF
Pass
span Αποστολή21.00:14.5:1
#000000
#FFFFFF
Pass
span 0,00€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

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.

B
Lighthouse Accessibility Audits
Score 82/100 — 4 failing, 21 passed
REVIEW
82

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div#search_block_top > form#searchbox > button.btn div.row > div#search_block_top > form#searchbox > button.btn

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.left-block > div.product-image-container > div.quick-view-wrapper-mobile > a.quick-view-mobile div.left-block > div.product-image-container > div.quick-view-wrapper-mobile > a.quick-view-mobile
div#htmlcontent_home > ul.htmlcontent-home > li.htmlcontent-item-4 > a.item-link div#htmlcontent_home > ul.htmlcontent-home > li.htmlcontent-item-4 > a.item-link
section#social_block > ul > li.youtube > a._blank section#social_block > ul > li.youtube > a._blank
section#social_block > ul > li.google-plus > a._blank section#social_block > ul > li.google-plus > a._blank
section#social_block > ul > li.instagram > a._blank section#social_block > ul > li.instagram > a._blank

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.

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
div.row > div#search_block_top > form#searchbox > input#search_query_top div.row > div#search_block_top > form#searchbox > input#search_query_top

These are opportunities to improve the legibility of your content.

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

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]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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.
○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.
○Identical links have the same purpose.
○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 Text Quality
All 56 heading(s) have substantive, well-formed text
PASS
All 56 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search_query" id="search_query_top">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search_query_toptext(Αναζήτηση)placeholder only

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

<input type="text" name="search_query" id="search_query_top">

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

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 "search_query" should use type="search" (currently type="text")
Field name "search_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
1 form control(s) checked, no input-semantic issues
PASS
1 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 "el-gr"
PASS
Lang attribute set to "el-gr"
Info::
<html lang="el-gr"> is set and valid
Got: el-gr
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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 26 visible text node(s) render at >= 12 CSS pixels
PASS
All 26 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback