Skip to content
https://auth.gr

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
39 landmarks
FIX
39 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
9 <nav> landmark(s) found
Warning::
4 of 9 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Skip to content navigation" SEARCH MAIN (missing!) ASIDE "Εργαλείο Προσβασιμότητας" 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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

D
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
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 500 ✗Page Title WordPress › Σφάλμα ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
9 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 9 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Heading Hierarchy
Action
28 headings, 1 skip(s)
REVIEW
28 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 ΓΝΩΣΗ ΚΑΙΝΟΤΟΜΙΑ ΠΟΛΙΤΙΣΜΟΣ
  • H2 ΚΑΛΩΣΟΡΙΣΕΣ ΣΤΟ ΑΡΙΣΤΟΤΕΛΕΙΟ ΠΑΝΕΠΙΣΤΗΜΙΟ
  • H2 Χαιρετισμός του Πρύτανη του Αριστοτελείου
  • H2 Καθηγητή Κυριάκου Αναστασιάδη
  • H3 Προπτυχιακές Σπουδές στο ΑΠΘ
  • H3 Μεταπτυχιακές Σπουδές στο ΑΠΘ
  • H3 ΤΑ ΝΕΑ ΤΟΥ ΑΠΘ
  • H3 ΑΠΘ ΣΕ ΑΡΙΘΜΟΥΣ
  • H3 ΕΚΔΗΛΩΣΕΙΣ
  • H3 ΕΡΕΥΝΑ
  • H3 103,47
  • H3 129,52
  • H3 91
  • H3 179
  • H3 4.278
  • H3 171
  • H3 889
  • H3 20
  • H3 15
  • H3 Η ΖΩΗ ΣΤΟ ΑΠΘ
  • H6 ΤΟ ΑΠΘ skipped
  • H6 ΣΗΜΑΝΤΙΚΑ
  • H6 ΧΡΗΣΙΜΑ
  • H6 ΑΚΟΛΟΥΘΗΣΤΕ ΜΑΣ
  • H6 ΤΟ ΑΠΘ
  • H6 ΣΗΜΑΝΤΙΚΑ
  • H6 ΧΡΗΣΙΜΑ
  • H6 ΑΚΟΛΟΥΘΗΣΤΕ ΜΑΣ

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

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 87/100 — 5 failing, 27 passed
REVIEW
87

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
22 Απριλίου 2026 Εθελοντική αιμοδοσία στο Αριστοτέλειο Πανεπιστήμιο στις 11-05… div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-loop-container
ΚΑΤΗΓΟΡΙΑ: ΕΚΔΗΛΩΣΕΙΣ Εκδήλωση «Μαραθώνιος Ανάγνωσης για τη Γαλλοφωνία», Κέντρ… div.e-con-inner > div.elementor-element > div.elementor-widget-container > div.elementor-loop-container
Παιδαγωγική Σχολή Σχολή Καλών Τεχνών Σχολή Κοινωνικών και Οικονομικών Επιστημ… div.elementor-element > div.elementor-element > div.elementor-widget-container > div.swiper

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ΤΟ ΑΠΘ div.elementor-element > div.elementor-element > div.elementor-widget-container > h6.elementor-heading-title

These are opportunities to improve keyboard navigation in your application.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Διαβάστε περισσότερα… div.elementor-element > div.elementor-widget-container > p > a

These are opportunities to improve the legibility of your content.

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.elementor-element > div.elementor-element > div.elementor-widget-container > a div.elementor-element > 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#innovation-forum > div.elementor-element > div.elementor-widget-container > a div#innovation-forum > 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

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[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
●`<frame>` or `<iframe>` elements have a title
●`<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.
●`[lang]` attributes have a valid value
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○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
○`<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
○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.
○`<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.
○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+
Alt Text Quality
All 46 images OK
PASS
All 46 images OK
Info::
19 decorative image(s) correctly marked
Info::
27 image(s) with good alt text
46 images 27 good alt text 19 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ckySwitchanalyticscheckboxEnable Analyticsaria-label
#search-e01e73bsearchSearchfor/id
#search-c92c6dbsearchSearchfor/id
#search-a361a5asearchSearchfor/id
#search-8333e8esearchSearchfor/id
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 ΓΝΩΣΗ20.12:13.0:1
#000000
#FAFAFA
Pass
h2 ΠΟΛΙΤΙΣΜΟΣ20.12:13.0:1
#000000
#FAFAFA
Pass
h2 ΚΑΛΩΣΟΡΙΣΕ…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Χαιρετισμό…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 του Αριστο…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Καθηγητή20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Κυριάκου Α…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Σπουδές στ…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Σπουδές στ…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 ΤΑ ΝΕΑ ΤΟΥ …20.12:13.0:1
#000000
#FAFAFA
Pass
h3 ΑΠΘ ΣΕ ΑΡΙΘ…20.12:13.0:1
#000000
#FAFAFA
Pass
h3 ΕΚΔΗΛΩΣΕΙΣ20.12:13.0:1
#000000
#FAFAFA
Pass
h3 ΕΡΕΥΝΑ20.12:13.0:1
#000000
#FAFAFA
Pass
h3 103,4720.12:13.0:1
#000000
#FAFAFA
Pass
h3 129,5220.12:13.0:1
#000000
#FAFAFA
Pass
h3 17920.12:13.0:1
#000000
#FAFAFA
Pass
h3 4.27820.12:13.0:1
#000000
#FAFAFA
Pass
h3 17120.12:13.0:1
#000000
#FAFAFA
Pass
h3 88920.12:13.0:1
#000000
#FAFAFA
Pass
h3 Η ΖΩΗ ΣΤΟ Α…20.12:13.0:1
#000000
#FAFAFA
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