Skip to content
https://bayern.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
Alt Text Quality
Action
5 of 84 images have issues
FIX
5 of 84 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
5 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
30 decorative image(s) correctly marked
Info::
48 image(s) with good alt text
84 images 48 good alt text 30 decorative 5 missing
IssueCount
missing5 image(s)
too long1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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.
C
Form Accessibility
Action
5 of 7 controls have issues
REVIEW
5 of 7 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="customSwitch193006firMZoQqa5">; <input type="checkbox" id="customSwitch193006firMZoQqa52">; <input type="checkbox" id="customSwitch193000CMJIbCihiA">; <input type="checkbox" id="customSwitch193000CMJIbCihiA2">; <input type="checkbox">
Info::
2 control(s) properly labeled
7 controls
2 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
sbsearchSuchbegriff eingebenaria-label
#emailfeldtextIhre E-Mail-Adressefor/id
#customSwitch193006firMZoQqa52checkbox(none)none
#customSwitch193000CMJIbCihiAcheckbox(none)none
#customSwitch193000CMJIbCihiA2checkbox(none)none
#customSwitch193006firMZoQqa5checkbox(none)none
inputcheckbox(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="checkbox" id="customSwitch193006firMZoQqa5">; <input type="checkbox" id="customSwitch193006firMZoQqa52">; <input type="checkbox" id="customSwitch193000CMJIbCihiA">; <input type="checkbox" id="customSwitch193000CMJIbCihiA2">; <input type="checkbox">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 27 passed
REVIEW
88

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main#maincontent > section.newsletter-subscribe > div.container > div#news-result main#maincontent > section.newsletter-subscribe > div.container > div#news-result

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div#bavaria-in > div.owl-dots > button.owl-dot div.container > div#bavaria-in > div.owl-dots > button.owl-dot
div.container > div#bavaria-in > div.owl-dots > button.owl-dot div.container > div#bavaria-in > div.owl-dots > button.owl-dot
div.container > div#bavaria-in > div.owl-dots > button.owl-dot div.container > div#bavaria-in > div.owl-dots > button.owl-dot

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.article-img > div > div.article-image > a div.article-img > div > div.article-image > a
div.masonry-brick > div.masonry-content > div.media-image > a div.masonry-brick > div.masonry-content > div.media-image > a
div.masonry-brick > div.masonry-content > div.media-image > a div.masonry-brick > div.masonry-content > div.media-image > a
div.masonry-brick > div.masonry-content > div.media-image > a div.masonry-brick > div.masonry-content > div.media-image > a
div.masonry-brick > div.masonry-content > div.media-image > a div.masonry-brick > div.masonry-content > div.media-image > a

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.

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
Jetzt aktivieren div.article-video > div.article-img-overlaytitle > div.article-video-overlay > div.article-img-text
Jetzt aktivieren div.article-video > div.article-img-overlaytitle > div.article-video-overlay > div.article-img-text
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain 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 are distinguishable without relying on color.
●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
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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
○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
○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.
○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
Landmark Structure
10 landmarks
PASS
10 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 "Top-Navigation" 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
35 headings
PASS
35 headings
Info::
Single H1 present
  • H1 Offizielles Landesportal der Bayerischen Staatsregierung: Aktuelle Meldungen, Informationen zum Freistaat Bayern, Politikthemen.
  • H2 Kabinettssitzung am 21. April 2026
  • H2 Bayerische Rettungsmedaille und Christophorus-Medaille 2026
  • H2 Olympiaempfang 2026
  • H2 Amazon Deutschland: Eröffnung neuer Hauptsitz in München
  • H2 Gespräch mit Rennrodel-Bundestrainer Patric Leitner
  • H2 Zentralasien hielt Erfolge für den Freistaat bereit
  • H2 Bayern in Zahlen
  • H2 Presse
  • H3 Bayerisches Staatsministerium für Familie, Arbeit und Soziales
  • H3 Bayerische Staatskanzlei
  • H3 Bayerisches Staatsministerium für Unterricht und Kultus
  • H3 Bayerisches Staatsministerium für Unterricht und Kultus
  • H3 Bayerische Staatskanzlei
  • H3 Bayerische Staatskanzlei
  • H3 Bayerisches Staatsministerium für Wohnen, Bau und Verkehr
  • H3 Bayerisches Staatsministerium für Familie, Arbeit und Soziales
  • H3 Bayerische Staatskanzlei
  • H3 Bayerisches Staatsministerium für Unterricht und Kultus
  • H3 Bayerisches Staatsministerium für Unterricht und Kultus
  • H3 Bayerische Staatskanzlei
  • H3 Bayerische Staatskanzlei
  • H3 Bayerisches Staatsministerium für Wohnen, Bau und Verkehr
  • H3 Bayerisches Staatsministerium für Familie, Arbeit und Soziales
  • H2 Bayern in
  • H2 Social Media
  • H3 Video in Gebärdensprache: Pressekonferenz nach der Kabinettssitzung (21.04.2026) – Bayern
  • H3 62. Sitzung der „Denkfabrik Legal Tech“ am 17. April 2026 – Bayern
  • H3 bayern.de
  • H3 bayern.de
  • H3 bayern.de
  • H3 bayern.de
  • H2 Newsletter bestellen!
  • H2 BAYERN | DIREKT:
  • H2 Lightbox-Element
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 Seite nicht gefunden – Bayerisches Landesportal ✓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 Offizielles Landespo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bayern in Zahlen21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Presse21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bayern in21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Social Media21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Lightbox-Element21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerisches Staatsmi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerische Staatskan…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerisches Staatsmi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerisches Staatsmi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerische Staatskan…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerische Staatskan…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerisches Staatsmi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerisches Staatsmi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerische Staatskan…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerisches Staatsmi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerisches Staatsmi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerische Staatskan…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerische Staatskan…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bayerisches Staatsmi…21.00:13.0:1
#000000
#FFFFFF
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.

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

Send Feedback