Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 4 REVIEW 3 FIX

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: #ffffff

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Link & Button Quality

Action

7 issue(s) across 47 links and 15 buttons

REVIEW

7 issue(s) across 47 links and 15 buttons

1 link(s) with no accessible text

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

Got: #vice

3 link(s) open in new tab without warning

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

Got: https://moje.amista.cz/; https://www.akatcr.cz/; https://moje.amista.cz/

6 button(s) with no accessible text

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

Got: button.pswp__button (#536 on page); button.pswp__button (#537 on page); button.pswp__button (#538 on page); button.pswp__button (#539 on page); button.pswp__button (#546 on page); button.pswp__button (#547 on page)

43 link(s) with descriptive text

47 links

1 empty

0 generic text

3 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://moje.amista.cz/	Moje AMISTA	new tab	Add '(opens in new tab)' to text
#vice	(empty)	empty	Add link text or aria-label
https://www.akatcr.cz/	AKAT ÄŚR	new tab	Add '(opens in new tab)' to text
https://moje.amista.cz/	Moje AMISTA	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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

52 links and buttons have descriptive text

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

#vice

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://moje.amista.cz/; https://www.akatcr.cz/; https://moje.amista.cz/

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.pswp__button (#536 on page); button.pswp__button (#537 on page); button.pswp__button (#538 on page); button.pswp__button (#539 on page); button.pswp__button (#546 on page); button.pswp__button (#547 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

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Nenalezeno (404) - AMISTA ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

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 Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

Heading Hierarchy

17 headings

PASS

17 headings

Multiple H1 headings (5 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Fondy kvalifikovaných investorů
H2 Rozšíření licence od ČNB
H3 O váš fond se postaráme. V plném rozsahu a s veškerou péčí
H3 Strukturování investičních fondů
H3 Zakládání fondů
H3 Administrace fondů
H3 Obhospodařování fondů
H3 Související fondové služby
H3 Poradenství
H2 Založili jsme první fond FKI v ČR
H2 Svou důvěru v nás vložilomnoho úspěšných investorů
H2 Za schůzku s námi nic nedáte. Překoná vaše očekávání.
H3 Zaměstnáváme nejlepší odborníky na správu fondů kvalifikovaných investorů
H1 Informace o změně depozitáře duplicate H1
H1 AMISTA investiční společnost rozšiřuje představenstvo a posiluje vedení duplicate H1
H1 Novým investičním ředitelem AMISTA IS je Mgr. Jiří Frankič duplicate H1
H1 Novým generálním ředitelem investiční společnosti AMISTA je Tomáš Vinkler duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Heading Text Quality

All 17 heading(s) have substantive, well-formed text

PASS

All 17 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 8 images OK

PASS

All 8 images OK

8 image(s) with good alt text

8 images 8 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#o-header-status	checkbox	Menu	for/id
input	checkbox		none
input	checkbox		none

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "cs"

PASS

Lang attribute set to "cs"

<html lang="cs"> is set and valid

Got: cs

A+

Tabindex Anti-Patterns

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 109 visible text node(s) render at >= 12 CSS pixels

PASS

All 109 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

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)

Element	Ratio	Required	FG	BG	Result
h1 kvalifikovaných inv…	15.79:1	3.0:1	#000000	#ECDBE1	Pass
h1 Informace o změně …	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h1 AMISTA investiční …	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h1 Novým investičním…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h1 Novým generálním …	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h2 Rozšíření licenc…	17.43:1	3.0:1	#000000	#E9EAEB	Pass
h2 Založili jsme prvn�…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h2 Svou důvěru v ná…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h2 mnoho	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h2 Za schůzku s nám…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 O váš fond se	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 V plném rozsahu a�…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Strukturování inve…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Zakládání fondů	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Administrace fondů	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Obhospodařování f…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Související fondov…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Poradenství	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Zaměstnáváme nejl…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
title AMISTA \| Specialista…	15.05:1	4.5:1	#000000	#DADADD	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 96/100 — 1 failing, 24 passed

PASS

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

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.row > div.col-auto > div.a-animate-fade > a.o-hero__down `div.row > div.col-auto > div.a-animate-fade > a.o-hero__down`

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

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

●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

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

●Heading elements appear in a sequentially-descending order

●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

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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.