Skip to content
https://znaki.fm

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
3
REVIEW
5
PASS
5
INFO
0
Checks
13
5 PASS 5 REVIEW 3 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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
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 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.

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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <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
Heading Hierarchy
38 headings
REVIEW
38 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H5 Choose your country & language
  • H6 Ireland
  • H6 Spain
  • H6 Netherland
  • H6 Belgium
  • H6 Sweden
  • H6 Czech
  • H6 Slovakia
  • H6 Finland
  • H6 Hrvatska
  • H6 България
  • H6 Danmark
  • H6 România
  • H6 Bosna i Hercegovina
  • H6 Norge
  • H6 Srbija
  • H6 Shqipëria
  • H6 Македонија
  • H6 Lëtzebuerg
  • H6 Беларусь
  • H6 Қазақстан
  • H6 العالم العربي
  • H6 United Kingdom
  • H6 Poland
  • H6 Ελλάδα
  • H6 Argentina
  • H6 International
  • H6 Italia
  • H6 Portugal
  • H6 Slovenija
  • H6 Österreich
  • H6 Brasil
  • H6 France
  • H6 Schweiz
  • H6 Deutschland
  • H6 Hungary
  • H6 日本
  • H6 Ukraine

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

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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 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'>.
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Znaki
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Znaki ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Znaki Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA
a Companies
2.29:1
#000000
on
#484846
needs 4.5:1 (normal text)
16px · top of page (header area)
a Places
2.19:1
#000000
on
#454543
needs 4.5:1 (normal text)
16px · above the fold
a Currencies
1.37:1
#000000
on
#212622
needs 4.5:1 (normal text)
16px · above the fold
a UK | English
1.76:1
#000000
on
#373737
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Companies
1.17:1
#000000
on
#171716
needs 4.5:1 (normal text)
16px · above the fold
a Events
1.85:1
#000000
on
#3A3A3E
needs 4.5:1 (normal text)
16px · above the fold
a Persons
1.66:1
#000000
on
#3B3035
needs 4.5:1 (normal text)
16px · above the fold
a Places
1.28:1
#000000
on
#192026
needs 4.5:1 (normal text)
16px · above the fold
button More…
1.03:1
#000000
on
#050505
needs 4.5:1 (normal text)
16px · above the fold
a Events
1.16:1
#000000
on
#181513
needs 4.5:1 (normal text)
16px · above the fold
b Isle of Wight Festival
1.06:1
#000000
on
#0B0909
needs 3.0:1 (large text)
16px · mid-page
a Companies
1.02:1
#000000
on
#040403
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
title All news - the lates…21.00:14.5:1
#000000
#FFFFFF
Pass
a Persons21.00:14.5:1
#000000
#FFFFFF
Pass
a Events10.43:14.5:1
#000000
#B6B7B5
Pass
a Companies2.29:14.5:1
#000000
#484846
Fail
a Places2.19:14.5:1
#000000
#454543
Fail
a Currencies1.37:14.5:1
#000000
#212622
Fail
a UK | English1.76:14.5:1
#000000
#373737
Fail
a Companies1.17:14.5:1
#000000
#171716
Fail
a Events1.85:14.5:1
#000000
#3A3A3E
Fail
a Persons1.66:14.5:1
#000000
#3B3035
Fail
a Places1.28:14.5:1
#000000
#192026
Fail
button More…1.03:14.5:1
#000000
#050505
Fail
a Events1.16:14.5:1
#000000
#181513
Fail
b Isle of Wight Festiv…1.06:13.0:1
#000000
#0B0909
Fail
a Companies1.02:14.5:1
#000000
#040403
Fail
b The Snuts20.81:13.0:1
#000000
#FEFEFD
Pass
a Persons20.44:14.5:1
#000000
#FCFCFA
Pass
b Prue Leith20.62:13.0:1
#000000
#FDFDFB
Pass
a Places19.95:14.5:1
#000000
#F9F9F9
Pass
b Folly Farm Adventure…7.03:13.0:1
#000000
#9E929A
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
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 ASIDE CONTENTINFO footer

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+
Alt Text Quality
All 71 images OK
PASS
All 71 images OK
Info::
71 image(s) with good alt text
71 images 71 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailemail(email@domain.com)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="email" name="email">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 20 passed
PASS
96

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
Use of the materials is permitted by providing a link (hyperlink for online pub… body#app > footer.c-footer > div.c-footer__regulations > p
Znaki footer.c-footer > div.c-footer__regulations > p > a.u-color--shade-5

These are opportunities to improve the legibility of your content.

○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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.
●ARIA attributes are used as specified for the element's role
●`[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.
●Links have a discernible name
●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.
●Document has a main landmark.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○Heading elements appear in a sequentially-descending order
○`<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.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback