Skip to content
https://srf.ch

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
1
PASS
7
INFO
0
Checks
13
7 PASS 1 REVIEW 5 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: SRF – Schweizer Radio und Fernsehen
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name SRF – Schweizer Radio und Fernsehen ✓192×192 icon ✗512×512 icon ✓Start URL ✗Display Mode browser ✗
Name SRF – Schweizer Radio und Fernsehen Display Mode browser 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: [object object]
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::
4 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 4 <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
Favicon & Branding
5 icon(s) detected
REVIEW
5 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::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "masthead-portals-label" MAIN 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+
Heading Hierarchy
40 headings
PASS
40 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 SRF Home
  • H2 Header
  • H3 Rubriken
  • H3 Hauptmenü/Suche
  • H3 Rubriken
  • H3 Video & Audio
  • H2 Live TV
  • H3 SRF 1 Live
  • H3 SRF 2 Live
  • H3 SRF Info Live
  • H2 Radio-Livestreams
  • H3 Radio SRF 1 Live
  • H3 Radio SRF 2 Live
  • H3 Radio SRF 3 Live
  • H3 Radio SRF 4 Live
  • H3 Radio SRF Musikwelle Live
  • H3 Radio SRF Virus Live
  • H2 Inhalt
  • H3 Gesprächsstoff to go
  • H3 Mensch im Fokus
  • H3 Hintergrund
  • H3 Besser leben
  • H3 Entertainment
  • H3 Bildstark
  • H3 SRF Archiv: Über eine Million Videos und Audios zugänglich
  • H3 «Shaolin Challenge» – Neue Dokuserie auf Play SRF
  • H3 Filme, Serien und Doks: Was soll ich heute streamen?
  • H3 Beliebte Podcasts
  • H3 Podcast-Episoden, die sich lohnen
  • H3 SRF-Inhalte für Kinder
  • H3 «dialog»: Hirnfutter für die ganze Schweiz
  • H3 Rätoromanische Reportagen
  • H2 Footer
  • H3 Suche
  • H3 Hauptnavigation
  • H3 Metanavigation
  • H3 Suche
  • H3 SRG-Login
  • H3 Hauptnavigation
  • H2 (empty)

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Alt Text Quality
All 83 images OK
PASS
All 83 images OK
Info::
82 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
83 images 1 good alt text 82 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtextSuche, zeigt beim Tippen Resultate annone
qtextSuche, zeigt beim Tippen Resultate annone
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 – Seite nicht gefunden! - SRF ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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
h1 SRF Home20.81:13.0:1
#000000
#FEFEFD
Pass
h2 Header19.23:13.0:1
#000000
#F5F5F2
Pass
h2 Live TV19.23:13.0:1
#000000
#F5F5F2
Pass
h2 Radio-Livestreams19.23:13.0:1
#000000
#F5F5F2
Pass
h2 Inhalt19.23:13.0:1
#000000
#F5F5F2
Pass
h2 Footer19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Rubriken19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Hauptmenü/Suche19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Rubriken19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Video & Audio19.23:13.0:1
#000000
#F5F5F2
Pass
h3 SRF 1 Live19.23:13.0:1
#000000
#F5F5F2
Pass
h3 SRF 2 Live19.23:13.0:1
#000000
#F5F5F2
Pass
h3 SRF Info Live19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Radio SRF 1 Live19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Radio SRF 2 Live19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Radio SRF 3 Live19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Radio SRF 4 Live19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Radio SRF Musikwelle…19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Radio SRF Virus Live19.23:13.0:1
#000000
#F5F5F2
Pass
h3 Gesprächsstoff to g…19.23:13.0:1
#000000
#F5F5F2
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 100/100 — 0 failing, 31 passed
PASS
100

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.

○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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
●`[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
●Elements with the `role=text` attribute do not have focusable descendents.
●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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[role]`s are contained by their required parent element
○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
○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.
○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