Skip to content
https://autoskolanemec.cz

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
7
REVIEW
3
PASS
14
INFO
0
Checks
24
14 PASS 3 REVIEW 7 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 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
Tap Target Adequacy
Action
19 tap target(s) too small or too close together
FIX
19 tap target(s) too small or too close together
Warning::
19 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.
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link detected
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
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 Stránka nenalezena ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 15 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 AUTOŠKOLA3.32:13.0:1
#000000
#BE1522
Pass
h1 NĚMEC Josef3.32:13.0:1
#000000
#BE1522
Pass
h2 O nás3.32:13.0:1
#000000
#BE1522
Pass
h2 Nabídka3.32:13.0:1
#000000
#BE1522
Pass
h2 Termíny zahájení3.32:13.0:1
#000000
#BE1522
Pass
h2 Školení řidičů3.32:13.0:1
#000000
#BE1522
Pass
h2 Ke stažení3.32:13.0:1
#000000
#BE1522
Pass
h2 Ceník3.32:13.0:1
#000000
#BE1522
Pass
h2 Kontakt3.32:13.0:1
#000000
#BE1522
Pass
h2 Užitečné Informac…3.32:13.0:1
#000000
#BE1522
Pass
h2 Fotogalerie3.32:13.0:1
#000000
#BE1522
Pass
h3 Kontaktní údaje3.32:13.0:1
#000000
#BE1522
Pass
h3 Sociální média3.32:13.0:1
#000000
#BE1522
Pass
h3 Úřední hodiny3.32:13.0:1
#000000
#BE1522
Pass
h3 Praktický výcvik3.32:13.0:1
#000000
#BE1522
Pass
title Domů17.78:14.5:1
#000000
#ECECEC
Pass
div Nastavení cookies17.78:14.5:1
#000000
#ECECEC
Pass
span Na našich webových…17.78:14.5:1
#000000
#ECECEC
Pass
a ODMÍTNOUT17.78:14.5:1
#000000
#ECECEC
Pass
a PŘIJMOUT17.78:14.5:1
#000000
#ECECEC
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 85/100 — 7 failing, 24 passed
REVIEW
85

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
PŘIJMOUT div.cc-grower > div.cc-window > div.cc-compliance > a.cc-btn
PŘIHLÁŠENÍ PROSÍM PROVÁDĚJTE POUZE TELEFONICKY ČI E-MAILEM div#mod-custom110 > p > strong > span

These are opportunities to improve the legibility of your content.

Names and labels

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.g-block > div#custom-1299-particle > div.container > iframe div.g-block > div#custom-1299-particle > div.container > 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.g-grid > div.g-block > div#logo-9608-particle > a.g-logo div.g-grid > div.g-block > div#logo-9608-particle > a.g-logo

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
Kontakt div.footer-wrap > div.footer-wrap-1 > div.footer-section > h4

These are opportunities to improve keyboard navigation in your application.

Best practices

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
div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > input#cookie_cat1 div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > input#cookie_cat1
Technické div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > a.cc-link
div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > input#cookie_cat2 div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > input#cookie_cat2
Funkční div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > a.cc-link
div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > input#cookie_cat3 div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > input#cookie_cat3
Analytické div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > a.cc-link
div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > input#cookie_cat4 div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > input#cookie_cat4
Marketingové div.cc-window > div.cc-checkboxes-container > div.cc-checkbox-container > a.cc-link
Domů div#g-mobilemenu-container > ul.g-toplevel > li.g-menu-item > a.g-menu-item-container
O nás div#g-mobilemenu-container > ul.g-toplevel > li.g-menu-item > a.g-menu-item-container
Nabídka div#g-mobilemenu-container > ul.g-toplevel > li.g-menu-item > a.g-menu-item-container
Termíny zahájení div#g-mobilemenu-container > ul.g-toplevel > li.g-menu-item > a.g-menu-item-container
Školení řidičů div#g-mobilemenu-container > ul.g-toplevel > li.g-menu-item > a.g-menu-item-container
Fotogalerie div#g-mobilemenu-container > ul.g-toplevel > li.g-menu-item > a.g-menu-item-container
Ceník div#g-mobilemenu-container > ul.g-toplevel > li.g-menu-item > a.g-menu-item-container
Ke stažení div#g-mobilemenu-container > ul.g-toplevel > li.g-menu-item > a.g-menu-item-container
Kontakt div#g-mobilemenu-container > ul.g-toplevel > li.g-menu-item > a.g-menu-item-container
Telefon: +420 602 119 011 div.nadpiskapHodiny > ul > li > a
Mail: nemec.as.cb@volny.cz div.nadpiskapHodiny > ul > li > a

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PŘIJMOUT div.cc-grower > div.cc-window > div.cc-compliance > a.cc-btn
PŘIJMOUT VŠE div.cc-grower > div.cc-window > div.cc-compliance > a.cc-btn
Zavřít div.cc-grower > div.cc-window > div.cc-compliance > a.cc-btn

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
08.09 2026 16:00        KURZ JE OBSAZEN A UZAVŘEN 12.11 2026 16:00        KURZ … div.col > div.com-content-article > div.com-content-article__body > table
○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
●`[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
●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
●Links are distinguishable without relying on color.
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`[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
○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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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.
A
Heading Hierarchy
17 headings, 1 skip(s)
PASS
17 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 AUTOŠKOLA NĚMEC Josef
  • H2 O nás
  • H2 Nabídka
  • H2 Termíny zahájení
  • H2 Školení řidičů
  • H2 Ke stažení
  • H2 Ceník
  • H2 Kontakt
  • H3 Kontaktní údaje
  • H4 Sídlo firmy
  • H2 Užitečné Informace
  • H3 Sociální média
  • H3 Úřední hodiny
  • H3 Praktický výcvik
  • H2 Fotogalerie
  • H4 Kontakt skipped
  • H4 Navigace

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+
Heading Text Quality
All 17 heading(s) have substantive, well-formed text
PASS
All 17 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
1 of 11 images have issues
PASS
1 of 11 images have issues
Warning::
1 image(s) with generic alt text
Info::
6 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
11 images 4 good alt text 6 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cookie_cat1checkboxTechnickéfor/id
#cookie_cat2checkboxFunkčnífor/id
#cookie_cat3checkboxAnalytickéfor/id
#cookie_cat4checkboxMarketingovéfor/id
A+
Form Input Types
4 form control(s) checked, no type mismatches
PASS
4 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 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 "cs-CZ"
PASS
Lang attribute set to "cs-CZ"
Info::
<html lang="cs-CZ"> is set and valid
Got: cs-CZ
A+
Tabindex Anti-Patterns
4 explicit tabindex attribute(s) checked, no anti-patterns
PASS
4 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d2619.0612892142217!2d14.4…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
Mobile-Readable Font Sizes
All 124 visible text node(s) render at >= 12 CSS pixels
PASS
All 124 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