Skip to content
https://cuni.cz

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
5
PASS
1
INFO
0
Checks
13
1 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 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

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
Heading Hierarchy
Action
14 headings, 1 skip(s)
FIX
14 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Aktuálně na UK
  • H2 Nové kampusy Univerzity Karlovy
  • H4 Biocentrum Albertov skipped
  • H5 PřF UK, 1. LF UK, MFF UK
  • H4 MEPHARED 2
  • H5 FaF UK, LF HK UK
  • H4 Kampus Motol
  • H5 2. LF UK
  • H2 Kalendář
  • H3 Rektorát
  • H3 Podatelna
  • H3 (empty)
  • H3 Tiskový mluvčí
  • H3 (empty)

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Alt Text Quality
Action
31 of 34 images have issues
FIX
31 of 34 images have issues
Critical::
29 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
18 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
2 image(s) with generic alt text
Info::
3 decorative image(s) correctly marked
34 images 3 decorative 2 generic 29 missing
IssueCount
missing29 image(s)
generic2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-idr9k7
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 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 2 <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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 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="text" name="q" id="mo99e3ygssn2mmmeglc">; <input type="submit" id="mo99e3ygqfx5ibgf9nc">
2 controls
0 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#mo99e3ygssn2mmmeglctext(none)none
#mo99e3ygqfx5ibgf9ncsubmit(none)none

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

<input type="text" name="q" id="mo99e3ygssn2mmmeglc">; <input type="submit" id="mo99e3ygqfx5ibgf9nc">

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

C
Favicon & Branding
Action
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
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA
button Upravit mé předvolby
2.33:1
#000000
on
#224D68
needs 4.5:1 (normal text)
16px · top of page (header area)
a O Univerzitě Karlově
1.53:1
#000000
on
#05304B
needs 4.5:1 (normal text)
16px · above the fold
a Historie
1.47:1
#000000
on
#022D48
needs 4.5:1 (normal text)
16px · above the fold
a Nikdy nezapomeneme...
1.64:1
#000000
on
#0A3550
needs 4.5:1 (normal text)
16px · above the fold
a Nadační fond UK
1.64:1
#000000
on
#0A3550
needs 4.5:1 (normal text)
16px · above the fold
a Fakta a čísla
2.10:1
#000000
on
#1B4661
needs 4.5:1 (normal text)
16px · above the fold
a Fakulty a součásti
1.45:1
#000000
on
#012C47
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Aktuálně na UK18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Nové kampusy Univer…18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Kalendář18.76:13.0:1
#000000
#F2F2F2
Pass
h3 Rektorát18.76:13.0:1
#000000
#F2F2F2
Pass
h3 Podatelna18.76:13.0:1
#000000
#F2F2F2
Pass
h3 Tiskový mluvčí18.76:13.0:1
#000000
#F2F2F2
Pass
title Univerzita Karlova21.00:14.5:1
#000000
#FFFFFF
Pass
p Používáme soubory…21.00:14.5:1
#000000
#FFFFFF
Pass
p Tyto webové stránk…21.00:14.5:1
#000000
#FFFFFF
Pass
button Upravit mé předvol…2.33:14.5:1
#000000
#224D68
Fail
a O Univerzitě Karlov…1.53:14.5:1
#000000
#05304B
Fail
a Historie1.47:14.5:1
#000000
#022D48
Fail
a Nikdy nezapomeneme..…1.64:14.5:1
#000000
#0A3550
Fail
a Nadační fond UK1.64:14.5:1
#000000
#0A3550
Fail
a Fakta a čísla2.10:14.5:1
#000000
#1B4661
Fail
a Fakulty a součásti1.45:14.5:1
#000000
#012C47
Fail
a Kontakt18.76:14.5:1
#000000
#F2F2F2
Pass
a Veřejnost a média18.76:14.5:1
#000000
#F2F2F2
Pass
a Život na UK18.76:14.5:1
#000000
#F2F2F2
Pass
a Etika a rovné pří…18.76:14.5:1
#000000
#F2F2F2
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 81/100 — 5 failing, 20 passed
REVIEW
81

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.

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
11 div.picker > div.days > div.day-container > div.day
12 div.picker > div.days > div.day-container > div.day
18 div.picker > div.days > div.day-container > div.day
19 div.picker > div.days > div.day-container > div.day
25 div.picker > div.days > div.day-container > div.day
26 div.picker > div.days > div.day-container > div.day
uk@cuni.cz div.node-content > div.overflowHidden > p > a
Další kontakty zde div.node-content > div.overflowHidden > p > a
pr@cuni.cz div.node-content > div.overflowHidden > p > a
organizační struktuře div.node-content > div.overflowHidden > p > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.items > div.item > div.image > img div.items > div.item > div.image > img
div.items > div.item > div.image > img div.items > div.item > div.image > img
div.items > div.item > div.image > img div.items > div.item > div.image > img
div.items > div.item > div.image > img div.items > div.item > div.image > img
div.items > div.item > div.image > img div.items > div.item > div.image > img
div.items > div.item > div.image > img div.items > div.item > div.image > img
div.items > div.item > div.image > img div.items > div.item > div.image > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.row > div.new > a.img > img div.row > div.new > a.img > img
div.medailon-container > div#mo99bd06ec1r9nxexdg > div.medailon-image > img div.medailon-container > div#mo99bd06ec1r9nxexdg > div.medailon-image > img
div.medailon-container > div#mo99bd07e6jq2k1scos > div.medailon-image > img div.medailon-container > div#mo99bd07e6jq2k1scos > div.medailon-image > img
div.medailon-container > div#mo99bd07qg73avs2ijn > div.medailon-image > img div.medailon-container > div#mo99bd07qg73avs2ijn > div.medailon-image > img
div.homepage > div.colorized-block > div.overlay > img div.homepage > div.colorized-block > div.overlay > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-md-6 > div.ratio > iframe div.row > div.col-md-6 > div.ratio > iframe
div.row > div.col-md-6 > div.ratio > iframe div.row > div.col-md-6 > div.ratio > iframe

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.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.news > div.row > div.new > a.img div.news > div.row > div.new > a.img
div.row > div.col-md-6 > div.ratio > a div.row > div.col-md-6 > div.ratio > a
div.row > div.col-md-6 > div.ratio > a div.row > div.col-md-6 > div.ratio > a
div.col-md-4 > p > span > a div.col-md-4 > p > span > a
div.col-md-4 > p > span > a div.col-md-4 > p > span > a
div.col-md-4 > p > span > a div.col-md-4 > p > span > a
div.footer-links > div.row > div.col-12 > a.ico div.footer-links > div.row > div.col-12 > a.ico
div.footer-links > div.row > div.col-12 > a.ico div.footer-links > div.row > div.col-12 > a.ico
div.footer-links > div.row > div.col-12 > a.ico div.footer-links > div.row > div.col-12 > a.ico
div.footer-links > div.row > div.col-12 > a.ico div.footer-links > div.row > div.col-12 > a.ico
div.footer-links > div.row > div.col-12 > a.ico div.footer-links > div.row > div.col-12 > a.ico

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.

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
Biocentrum Albertov div#mo99bd06ec1r9nxexdg > div.medailon-text > div.medailon-title > h4

These are opportunities to improve keyboard navigation in your application.

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
Buttons have an accessible name
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
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
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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
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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
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.
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sablona/dist/css/print.css?v=2026.04.16.17
Print Stylesheet Print Optimized
Print stylesheet /sablona/dist/css/print.css?v=2026.04.16.17 Inline @media print Not detected
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback