Skip to content
https://sachsen.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 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 2 <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
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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Die angeforderte Seite existiert leider nicht. - sachsen.de ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Schnelleinstieg der Portalthemen
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sachsen gestaltet Zukunft
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Dresdner Forum für Internationale Polit…
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Gründerinnenpreis 2026
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 So geht sächsisch.
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mach was Wichtiges
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Aktuelles
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ministerpräsident Michael Kretschmer
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sächsische Staatsregierung
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Aus dem Kabinett
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Virtueller Rundgang durch die Staatskanz…
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sächsischer Bürgerpreis 2025
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Arbeiten im Öffentlichen Dienst Sachsen
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Politik in Bildern
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Amt24 - zu Hause aufs Amt
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Digitale Publikationen auf issuu
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sachsen in Berlin
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Landesrecht
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Einheitlicher Ansprechpartner - Point of…
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Herausgeber
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Schnelleinstieg der …1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Sachsen gestaltet Zu…1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Dresdner Forum für …1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Gründerinnenpreis 2…1.93:13.0:1
#000000
#3D3D3D
Fail
h2 So geht sächsisch.1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Mach was Wichtiges1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Aktuelles1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Ministerpräsident M…1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Sächsische Staatsre…1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Aus dem Kabinett1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Virtueller Rundgang …1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Sächsischer Bürger…1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Arbeiten im Öffentl…1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Politik in Bildern1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Amt24 - zu Hause auf…1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Digitale Publikation…1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Sachsen in Berlin1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Landesrecht1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Einheitlicher Anspre…1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Herausgeber1.93:13.0:1
#000000
#3D3D3D
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 84/100 — 4 failing, 27 passed
REVIEW
84

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mittwoch Wählen Sie eine Stadt: Dresden vormittags 10° leicht bewölkt 5% Risiko… div.row > main#main-content > div.wetter > div#accordion-content-wetter-3915
Herausgeber Sächsische Staatskanzlei Archivstraße 1 01097 Dresden Telefon:  +… body.portal-index > footer#footer > div.footer-content > div#accordion-footer

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Mittwoch div.wetter > div#accordion-content-wetter-3915 > div#wetter-day-3915-1 > div#heading-content-wetter-3915-1
Donnerstag div.wetter > div#accordion-content-wetter-3915 > div#wetter-day-3915-2 > div#heading-content-wetter-3915-2
Freitag div.wetter > div#accordion-content-wetter-3915 > div#wetter-day-3915-3 > div#heading-content-wetter-3915-3

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Bild in sozialen Medien teilen div.box-media > div.gallery > div.gallery-fullscreen > div#_auto-slider-98

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.rsSlide > article#highlight-slide-6593 > div.rsSlideBackdrop > img div.rsSlide > article#highlight-slide-6593 > div.rsSlideBackdrop > img
div.rsSlide > article#highlight-slide-6585 > div.rsSlideBackdrop > img div.rsSlide > article#highlight-slide-6585 > div.rsSlideBackdrop > img
div.rsSlide > article#highlight-slide-6589 > div.rsSlideBackdrop > img div.rsSlide > article#highlight-slide-6589 > div.rsSlideBackdrop > img
div.rsSlide > article#highlight-slide-5313 > div.rsSlideBackdrop > img div.rsSlide > article#highlight-slide-5313 > div.rsSlideBackdrop > img
div.rsSlide > article#highlight-slide-6341 > div.rsSlideBackdrop > img div.rsSlide > article#highlight-slide-6341 > div.rsSlideBackdrop > img

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
●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
●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
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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.
○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
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <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 "a-glohea" 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+
Heading Hierarchy
34 headings
PASS
34 headings
Info::
Single H1 present
  • H3 Der Freistaat Sachsen
  • H1 ✕ Portal: sachsen.de
  • H2 Schnelleinstieg der Portalthemen
  • H2 Sachsen gestaltet Zukunft
  • H3 Die Sächsische Staatsregierung bringt den Abbau von Bürokratie voran
  • H2 Dresdner Forum für Internationale Politik
  • H3 5. Mai 2026, 19:15 Uhr Frauenkirche Dresden
  • H2 Gründerinnenpreis 2026
  • H3 Bewerben Sie sich jetzt!
  • H2 So geht sächsisch.
  • H3 Die Kampagne des Freistaates Sachsen
  • H2 Mach was Wichtiges
  • H3 Arbeiten im Öffentlichen Dienst Sachsen
  • H2 Aktuelles
  • H3 Terminvorschau des Ministerpräsidenten
  • H2 Ministerpräsident Michael Kretschmer
  • H2 Sächsische Staatsregierung
  • H2 Aus dem Kabinett
  • H2 Virtueller Rundgang durch die Staatskanzlei
  • H2 Sächsischer Bürgerpreis 2025
  • H2 Arbeiten im Öffentlichen Dienst Sachsen
  • H2 Politik in Bildern
  • H2 Amt24 - zu Hause aufs Amt
  • H3 Publikationen
  • H4 Möglichkeiten demokratischer Mitwirkung in Sachsen
  • H4 Sächsische Staatskanzlei
  • H2 Digitale Publikationen auf issuu
  • H2 Sachsen in Berlin
  • H2 Landesrecht
  • H2 Einheitlicher Ansprechpartner - Point of Single Contact
  • H2 Herausgeber
  • H2 Service
  • H2 Verwandte Portale
  • H2 Seite empfehlen
A+
Alt Text Quality
All 19 images OK
PASS
All 19 images OK
Info::
2 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
19 images 17 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#glohea-searchtextSuchbegrifffor/id
#amt24_6180_begrifftextWas?for/id
#search_request_search_texttextSuchbegriff eingebenfor/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://www.styleguide.sachsen.de/dist/2.26.3/css/print.css
Print Stylesheet ✓ Print Optimized
Print stylesheet https://www.styleguide.sachsen.de/dist/2.26.3/css/print.css ✓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