Skip to content
https://krone.at

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 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
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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

D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
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)
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: #e3000f
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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <nav> element(s)
Back to Top
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.
B
Heading Hierarchy
1 headings
REVIEW
1 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Gelesen(ausgewählt)

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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title | krone.at Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA 2 pass AA only
i arrow_right
1.38:1
#000000
on
#222629
needs 4.5:1 (normal text)
16px · above the fold
i arrow_right
2.06:1
#000000
on
#474037
needs 4.5:1 (normal text)
16px · above the fold
a Profil
2.09:1
#000000
on
#4D4032
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Abonnement
3.38:1
#000000
on
#7F5845
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
i pin_drop
3.62:1
#000000
on
#6C672F
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
i arrow_right
1.87:1
#000000
on
#3B3B3B
needs 4.5:1 (normal text)
16px · mid-page
span Bundesland auswählen
1.99:1
#000000
on
#3F3F3F
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
li Niederösterreich
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

5 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
h2 Gelesen19.47:13.0:1
#000000
#F7F6F6
Pass
title Kronen Zeitung | Akt…19.59:14.5:1
#000000
#FDF7E3
Pass
i close21.00:14.5:1
#000000
#FFFFFF
Pass
span Schließen21.00:14.5:1
#000000
#FFFFFF
Pass
div Abonnieren21.00:14.5:1
#000000
#FFFFFF
Pass
i account_circle15.31:14.5:1
#000000
#DCDCDC
Pass
span Anmelden21.00:14.5:1
#000000
#FFFFFF
Pass
i arrow_right1.38:14.5:1
#000000
#222629
Fail
i arrow_right2.06:14.5:1
#000000
#474037
Fail
span Menü aufklappen5.69:14.5:1
#000000
#9B8069
Pass
a Profil2.09:14.5:1
#000000
#4D4032
Fail
a Abonnement3.38:14.5:1
#000000
#7F5845
Fail
a Einstellungen11.98:14.5:1
#000000
#D9C52F
Pass
a Abmelden8.39:14.5:1
#000000
#B5A52F
Pass
i pin_drop3.62:14.5:1
#000000
#6C672F
Fail
span Wien10.45:14.5:1
#000000
#F5A0A5
Pass
i arrow_right1.87:14.5:1
#000000
#3B3B3B
Fail
span Bundesland auswähle…1.99:14.5:1
#000000
#3F3F3F
Fail
li Wien6.66:14.5:1
#000000
#919191
Pass
li Niederösterreich3.66:14.5:1
#000000
#666666
Fail

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 — 5 failing, 27 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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Merkliste div.nd__block > div.nd__row > a.nd__bookmarks-link > span.nd__bookmarks-text
Benachrichtigungen div.nd__block > div.nd__row > a.nd__push-settings-link > span.nd__push-settings-text

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.box > div#krn_startseite_banner_ueber_fdt > div.tp-container-inner > iframe#offer_de88c7f81fe7c83dfd3f-0 div.box > div#krn_startseite_banner_ueber_fdt > div.tp-container-inner > iframe#offer_de88c7f81fe7c83dfd3f-0

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.

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

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
Go to slide 1 div.box > div.ss__outer > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 2 div.box > div.ss__outer > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 3 div.box > div.ss__outer > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 4 div.box > div.ss__outer > div.swiper-pagination > span.swiper-pagination-bullet
Go to slide 5 div.box > div.ss__outer > div.swiper-pagination > span.swiper-pagination-bullet

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
Krone PUR bestellen div.didomi-popup-container > div.didomi-popup-view > div#buttons > button#didomi-notice-disagree-button
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-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
Form elements have associated labels
Select elements have associated label elements.
`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.
`[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
Links are distinguishable without relying on color.
Links have a discernible name
No element has a `[tabindex]` value greater than 0
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
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
`<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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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
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.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
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.
A+
Alt Text Quality
All 229 images OK
PASS
All 229 images OK
Info::
28 decorative image(s) correctly marked
Info::
201 image(s) with good alt text
229 images 201 good alt text 28 decorative
All images have appropriate alt text.
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
#search-inputtextSuchefor/id
inputtextSuchfeldaria-label
nls-emailemailEmail Feldaria-label
inputcheckboxZwischen TV und Radio wechselnaria-label
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /css/kroneat-print.css?decache=7c622c469d4789a545a6568154375714f43cda731.0.34451
Print Stylesheet Print Optimized
Print stylesheet /css/kroneat-print.css?decache=7c622c469d4789a545a6568154375714f43cda731.0.34451 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.

Send Feedback