Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Alt Text Quality

Action

5 of 35 images have issues

FIX

5 of 35 images have issues

5 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

5 image-in-link without alt text

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

30 decorative image(s) correctly marked

35 images 30 decorative 5 missing

Issue	Count
missing	5 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

Link & Button Quality

Action

6 issue(s) across 38 links and 9 buttons

FIX

6 issue(s) across 38 links and 9 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://blog.seznam.cz/en/?p=59442&preview=true&_thumbnail_id=59374; /

13 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://help.mapy.com/en/; https://www.seznam.cz/reklama/en/obsahovy-web/sluzba-firmy; https://licence.mapy.cz/?doc=mapy_pu&lang=en; https://ucet.seznam.cz/consents?lang=en; https://developer.mapy.cz/en/; https://www.facebook.com/mapy.com/; https://x.com/mapy_com; https://www.instagram.com/mapy_com; https://apps.apple.com/us/app/mapy-com-offline-gps-maps/id411411020?ppid=b9f3…; https://play.google.com/store/apps/details?id=cz.seznam.mapy&listing=outdoor_… (+3 more)

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.arrow-back-btn (#93 on page); button.clear-search (#97 on page); button.map-controls__resizer (#413 on page); button.icon (#427 on page)

23 link(s) with descriptive text

38 links

2 empty

0 generic text

13 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://mapy.com/en/?q=Travel%20tips&cat…	Travel tips	img no alt	Add alt attribute to the image
https://mapy.com/en/?q=Restaurants&cat=1	Restaurants	img no alt	Add alt attribute to the image
https://mapy.com/en/?q=Accommodations&ca…	Accommodations	img no alt	Add alt attribute to the image
https://mapy.com/en/?q=ATM&cat=1	ATM	img no alt	Add alt attribute to the image
https://blog.seznam.cz/en/?p=59442&previ…	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://mapy.com/nl/turisticka?x=11.3817…	Nederlands	img no alt	Add alt attribute to the image
https://mapy.com/bg/turisticka?x=11.3817…	български	img no alt	Add alt attribute to the image
https://mapy.com/da/turisticka?x=11.3817…	Dansk	img no alt	Add alt attribute to the image
https://mapy.com/sl/turisticka?x=11.3817…	Slovenščina	img no alt	Add alt attribute to the image
https://mapy.com/hu/turisticka?x=11.3817…	Magyar	img no alt	Add alt attribute to the image
https://mapy.com/es/turisticka?x=11.3817…	Español	img no alt	Add alt attribute to the image
https://mapy.com/fr/turisticka?x=11.3817…	Français	img no alt	Add alt attribute to the image
https://mapy.com/it/turisticka?x=11.3817…	Italiano	img no alt	Add alt attribute to the image
https://mapy.com/ru/turisticka?x=11.3817…	Pусский	img no alt	Add alt attribute to the image
https://mapy.com/uk/turisticka?x=11.3817…	Українська	img no alt	Add alt attribute to the image
https://mapy.com/pl/turisticka?x=11.3817…	Polski	img no alt	Add alt attribute to the image
https://mapy.com/de/turisticka?x=11.3817…	Deutsch	img no alt	Add alt attribute to the image
https://mapy.com/sk/turisticka?x=11.3817…	Slovenčina	img no alt	Add alt attribute to the image
https://mapy.com/cs/turisticka?x=11.3817…	Čeština	img no alt	Add alt attribute to the image
https://mapy.com/en/turisticka?x=11.3817…	English	img no alt	Add alt attribute to the image
https://help.mapy.com/en/	Help	new tab	Add '(opens in new tab)' to text
https://www.seznam.cz/reklama/en/obsahov…	Advertising	new tab	Add '(opens in new tab)' to text
https://licence.mapy.cz/?doc=mapy_pu&lan…	Terms and Licensing	new tab	Add '(opens in new tab)' to text
https://ucet.seznam.cz/consents?lang=en	Personalization settings	new tab	Add '(opens in new tab)' to text
https://developer.mapy.cz/en/	For developers	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/mapy.com/	Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/mapy_com	X	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/mapy_com	Instagram	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/us/app/mapy-com-o…	Apple Store	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	Google Play Store	new tab	Add '(opens in new tab)' to text
https://o-seznam.cz/	Seznam.cz, a.s.	new tab	Add '(opens in new tab)' to text
https://www.openstreetmap.org/copyright	OpenStreetMap	new tab	Add '(opens in new tab)' to text
https://licence.mapy.cz/?doc=mapy_attr&l…	others	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

28 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://blog.seznam.cz/en/?p=59442&preview=true&_thumbnail_id=59374; /

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://help.mapy.com/en/; https://www.seznam.cz/reklama/en/obsahovy-web/sluzba-firmy; https://licence.mapy.cz/?doc=mapy_pu&lang=en; https://ucet.seznam.cz/consents?lang=en; https://developer.mapy.cz/en/; https://www.facebook.com/mapy.com/; https://x.com/mapy_com; https://www.instagram.com/mapy_com; https://apps.apple.com/us/app/mapy-com-offline-gps-maps/id411411020?ppid=b9f3…; https://play.google.com/store/apps/details?id=cz.seznam.mapy&listing=outdoor_… (+3 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.arrow-back-btn (#93 on page); button.clear-search (#97 on page); button.map-controls__resizer (#413 on page); button.icon (#427 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-slyel2

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://mapy.cz/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://mapy.cz/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #1eae00

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Heading Hierarchy

1 headings

REVIEW

1 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 Categories

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

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 1 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 Categories	17.95:1	3.0:1	#000000	#EEEEE1	Pass
title Mapy.com	17.69:1	4.5:1	#000000	#E4EEE8	Pass
a More categories	15.21:1	4.5:1	#000000	#D6DFC4	Pass
span Travel tips	12.53:1	4.5:1	#000000	#B1D296	Pass
span Restaurants	17.16:1	4.5:1	#000000	#E5EBD3	Pass
span Accommodations	15.35:1	4.5:1	#000000	#D0E3B7	Pass
span ATM	7.75:1	4.5:1	#000000	#AC9A8B	Pass
a Log in	16.40:1	4.5:1	#000000	#DEE7CB	Pass
span and your search hist…	15.89:1	4.5:1	#000000	#DCE3CB	Pass
span Nederlands	10.70:1	4.5:1	#000000	#B3BD9F	Pass
span български	14.76:1	4.5:1	#000000	#CEDEB7	Pass
span Dansk	15.53:1	4.5:1	#000000	#D6E2C4	Pass
span Slovenščina	5.38:1	4.5:1	#000000	#6E8868	Pass
span Magyar	17.53:1	4.5:1	#000000	#EAECDC	Pass
span Español	11.36:1	4.5:1	#000000	#AEC69D	Pass
span Français	11.28:1	4.5:1	#000000	#B4C3A3	Pass
span Italiano	12.55:1	4.5:1	#000000	#C2CDA2	Pass
span Pусский	10.13:1	4.5:1	#000000	#9ABF7F	Pass
span Українська	9.88:1	4.5:1	#000000	#ABB699	Pass
span Polski	11.50:1	4.5:1	#000000	#B3C5AC	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.

Lighthouse Accessibility Audits

Score 85/100 — 3 failing, 21 passed

REVIEW

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#mapycz > div#block-map > div#layout-bar > button.icon `div#mapycz > div#block-map > div#layout-bar > button.icon`
div#mapycz > div#block-map > div#layout-bar > button.icon `div#mapycz > div#block-map > div#layout-bar > button.icon`
div#mapycz > div#block-map > div#layout-bar > button.icon `div#mapycz > div#block-map > div#layout-bar > button.icon`

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
Download Mapy.com `body.lang-en > div.android-app-promotion > div > a.button`
Not now `body.lang-en > div.android-app-promotion > div > button`

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

●`[accesskey]` values are unique

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●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 have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●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

○Elements with `role="dialog"` or `role="alertdialog"` 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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○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.

○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+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#input-search	text	Search	aria-label

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /css/print.2.80.90.css?s

Print Stylesheet ✓ Print Optimized

Print stylesheet /css/print.2.80.90.css?s ✓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.