Skip to content
https://blick.ch

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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.
C
Landmark Structure
Action
28 landmarks
REVIEW
28 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) ASIDE 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

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

B
Heading Hierarchy
21 headings
REVIEW
21 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Videos
  • H2 Sport
  • H2 Meistgelesen bei Blick+
  • H2 Blick Bites
  • H2 Promotion mit Box
  • H2 Wettbewerbe
  • H2 Das Beste von Bilanz.ch
  • H2 Schweiz
  • H2 Ausland
  • H2 Heiss diskutiert
  • H2 People
  • H2 Politik
  • H2 Meinung
  • H2 Wirtschaft
  • H2 Wein
  • H2 Gesellschaft
  • H2 Digital
  • H2 Community
  • H2 Leben
  • H2 Mobil
  • H2 Spiele & Rätsel

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

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color var(--is-light-theme, #ffffff) var(--is-dark-theme, #ffffff) ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+
Alt Text Quality
All 149 images OK
PASS
All 149 images OK
Info::
149 image(s) with good alt text
149 images 149 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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)
ElementRatioRequiredFGBGResult
h2 Videos19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Sport19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Meistgelesen bei Bli…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Blick Bites19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Promotion mit Box19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Wettbewerbe19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Das Beste von Bilanz…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Schweiz19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Ausland19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Heiss diskutiert19.26:13.0:1
#000000
#F5F5F5
Pass
h2 People19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Politik19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Meinung19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Wirtschaft19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Wein19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Gesellschaft19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Digital19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Community19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Leben19.26:13.0:1
#000000
#F5F5F5
Pass
h2 Mobil19.26:13.0:1
#000000
#F5F5F5
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 92/100 — 2 failing, 24 passed
PASS
92

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
Heisse «Segnung» eines Hauses div.Swiper__StyledItemsContainer-sc-d81e0497-0 > div.VideosCarousel__SwiperSlide-sc-e9ca1312-4 > a.Blink__StyledNextLink-sc-daa3c157-1 > div.Catchword__StyledCatchword-sc-a4ca0f06-0
Während Konzert div.Swiper__StyledItemsContainer-sc-d81e0497-0 > div.VideosCarousel__SwiperSlide-sc-e9ca1312-4 > a.Blink__StyledNextLink-sc-daa3c157-1 > div.Catchword__StyledCatchword-sc-a4ca0f06-0
Wieder gibts keine Strafe div.Swiper__StyledItemsContainer-sc-d81e0497-0 > div.VideosCarousel__SwiperSlide-sc-e9ca1312-4 > a.Blink__StyledNextLink-sc-daa3c157-1 > div.Catchword__StyledCatchword-sc-a4ca0f06-0
Chinesischer Park entlarvt div.Swiper__StyledItemsContainer-sc-d81e0497-0 > div.VideosCarousel__SwiperSlide-sc-e9ca1312-4 > a.Blink__StyledNextLink-sc-daa3c157-1 > div.Catchword__StyledCatchword-sc-a4ca0f06-0
Harter Check gegen Kopf div.Swiper__StyledItemsContainer-sc-d81e0497-0 > div.VideosCarousel__SwiperSlide-sc-e9ca1312-4 > a.Blink__StyledNextLink-sc-daa3c157-1 > div.Catchword__StyledCatchword-sc-a4ca0f06-0
Er spielte für beide Teams div.Swiper__StyledItemsContainer-sc-d81e0497-0 > div.VideosCarousel__SwiperSlide-sc-e9ca1312-4 > a.Blink__StyledNextLink-sc-daa3c157-1 > div.Catchword__StyledCatchword-sc-a4ca0f06-0

These are opportunities to improve the legibility of your content.

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.FirstRow__StyledFirstRow-sc-4bfcba28-0 > div.FirstRow__MainContainer-sc-4bfcba28-1 > div.FirstRow__RightButtonsContainer-sc-4bfcba28-4 > a.Blink__StyledNextLink-sc-daa3c157-1 div.FirstRow__StyledFirstRow-sc-4bfcba28-0 > div.FirstRow__MainContainer-sc-4bfcba28-1 > div.FirstRow__RightButtonsContainer-sc-4bfcba28-4 > a.Blink__StyledNextLink-sc-daa3c157-1
div.FirstRow__StyledFirstRow-sc-4bfcba28-0 > div.FirstRow__MainContainer-sc-4bfcba28-1 > div.FirstRow__RightButtonsContainer-sc-4bfcba28-4 > a.Blink__StyledNextLink-sc-daa3c157-1 div.FirstRow__StyledFirstRow-sc-4bfcba28-0 > div.FirstRow__MainContainer-sc-4bfcba28-1 > div.FirstRow__RightButtonsContainer-sc-4bfcba28-4 > a.Blink__StyledNextLink-sc-daa3c157-1
div.FooterComponent__StyledFooterContentWrapper-sc-a0a2eec4-1 > div.FooterComponent__StyledTextWrapper-sc-a0a2eec4-3 > div.StoreIcons__Wrapper-sc-8c7a2c6a-0 > a.Blink__StyledNextLink-sc-daa3c157-1 div.FooterComponent__StyledFooterContentWrapper-sc-a0a2eec4-1 > div.FooterComponent__StyledTextWrapper-sc-a0a2eec4-3 > div.StoreIcons__Wrapper-sc-8c7a2c6a-0 > a.Blink__StyledNextLink-sc-daa3c157-1

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.
●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
●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
●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.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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.
○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.
○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