Skip to content
https://muni.cz

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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::
4 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 4 <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
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <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.
Page Structure — as a screen reader sees it
BANNER header NAV "Výběr jazyka" MAIN CONTENTINFO footer

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

A
Heading Hierarchy
32 headings, 1 skip(s)
PASS
32 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Studijní programy
  • H2 Přijímačky a TSP
  • H2 Přečtěte si o výzkumu na MU
  • H2 Studijní programy
  • H2 Přijímačky a TSP
  • H2 Přečtěte si o výzkumu na MU
  • H1 Aktuálně
  • H3 Konference státní správy a neziskových organizací skipped
  • H3 22. dubna 202610:00 – 16:00
  • H4 Kumst, Údolní 19, Brno
  • H2 Dva dobrovolnické příběhy, které začaly na MU
  • H2 Brno Art Week se letos zaměří na „odolnost“
  • H2 O majálesový trůn za MU bojují Gabča a Richard
  • H2 Přírodovědecká fakulta posiluje mezinárodní spolupráci v Antarktidě i výzkumu vesmíru
  • H2 Nový pohled na segregaci ve školách: vzájemné ovlivňování chování ve třídě
  • H2 Objevte MUNI
  • H3 Budoucí studenti
  • H3 Studenti
  • H3 Veřejnost
  • H3 Společenská odpovědnost
  • H2 Fakulty a pracoviště
  • H2 Studujte na MUNI
  • H2 Pozvánky
  • H2 Výstava fotografií Ladislava Sitenského
  • H2 Slavnostní poklepání základního kamene MUNI SPORT PARKu
  • H2 MjUNI: Výuka na Univerzitním kampusu (MED a PHARM)
  • H2 Černobílý Černobyl? Kontexty jaderné havárie v průběhu čtyřiceti let
  • H2 Chci studovat
  • H2 Výzkum
  • H2 O univerzitě
  • H2 Kontakty
  • H2 Aktuálně

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

A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
16 image(s) with good alt text
16 images 16 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchtextHledej ...for/id
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Stránka nenalezena | Masarykova univerzita ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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
h1 Aktuálně20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Studijní programy20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Přijímačky a TSP20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Přečtěte si o v…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Studijní programy20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Přijímačky a TSP20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Přečtěte si o v…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Dva dobrovolnické p…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Brno Art Week se let…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 O majálesový trů…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Přírodovědecká f…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Nový pohled na segr…20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Objevte MUNI20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Studujte na MUNI20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Pozvánky20.12:13.0:1
#000000
#FAFAFA
Pass
h2 Kontakty20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Konference státní …20.12:13.0:1
#000000
#FAFAFA
Pass
h3 22. dubna 202620.12:13.0:1
#000000
#FAFAFA
Pass
h3 Budoucí studenti20.12:13.0:1
#000000
#FAFAFA
Pass
h3 Studenti20.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.

A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 22 passed
PASS
90

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
nav.menu-mobile > ul.menu-mobile__list > li.menu-mobile__item > a.menu-mobile__link nav.menu-mobile > ul.menu-mobile__list > li.menu-mobile__item > a.menu-mobile__link
div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle
div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle
div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle
div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle
div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle div.grid > div.grid__cell > div.footer__menu__title > a.footer__menu__title__toggle

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
Konference státní správy a neziskových organizací div.row-main > div.box-hero-header__content-inner > div.white > h3

These are opportunities to improve keyboard navigation in your application.

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
nav.menu-mobile > ul.menu-mobile__list > li.menu-mobile__item > a.menu-mobile__link

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.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[accesskey]` values are unique
●ARIA attributes are used as specified for the element's role
●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
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○Buttons have an accessible name
○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.
○No element has a `[tabindex]` value greater than 0
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback