Evolize inspected 5 public pages on stm.dk and detected 23 accessibility findings. The most widespread issue was "Hidden elements can still receive keyboard focus", detected on 5 inspected pages. The most affected inspected page was "/", where 19 findings were detected. The assessment identified findings mapped to 5 WCAG success criterions. The sections below prioritize the broadest issues and provide technical evidence for each detected finding.
02 · Start here
These findings combine the highest severity and broadest reach detected during this assessment.
Critical
Buttons have no accessible name
WCAG 4.1.2 (A) · 1 inspected page · 2 instances
Why this matters
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Recommended action
Add an accessible name to the button using the aria-label attribute or provide a text description of the button's purpose.
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Recommended action
Add an accessible name to the button, such as using the 'aria-label' attribute or providing a text label within the button element. For example: <button class="swiper-button-next" aria-label="Next slide"></button>
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Recommended action
Add an accessible name to the button element, either by including text within the button or by using the aria-label attribute to provide a text description of the button's purpose.
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Recommended action
To fix this issue, ensure that the element is removed from the tab order when it is not visible. This can be achieved by setting the 'tabindex' attribute to '-1' or by using a CSS rule to set 'display: none' or 'visibility: hidden' when the element is not intended to be interacted with.
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Why it matters
Interactive buttons expose no accessible name, so their purpose cannot be determined by assistive technology.
Recommended correction
Add an accessible name to the button element, either by including text within the button or by using the aria-label attribute to provide a text description of the button's purpose.
View 6 affected elements
Component · Ref NSSQ6N
Affected pagehttps://stm.dk/
Element.swiper-button-prev
Markup
<button class="swiper-button-prev"></button>
Component · Ref 9OOHR7
Affected pagehttps://stm.dk/
Element.swiper-autoplay
Markup
<button class="swiper-autoplay">
Component · Ref J224A2
Affected pagehttps://stm.dk/
Element.swiper-button-next
Markup
<button class="swiper-button-next"></button>
High
Hidden elements can still receive keyboard focus
WCAG 2.4.3 (A)100 instances5 inspected pages
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Why it matters
An element is not visible but remains in the tab order, so a sighted keyboard user loses track of focus when it lands there.
Recommended correction
To fix this issue, ensure that the element is removed from the tab order when it is not visible. This can be achieved by setting the 'tabindex' attribute to '-1' or by using a CSS rule to set 'display: none' or 'visibility: hidden' when the element is not intended to be interacted with.
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Why it matters
Text and background colours do not meet the minimum contrast ratio, reducing legibility.
Recommended correction
To fix this issue, increase the contrast between the text color and background color. You can do this by changing the CSS styles for the element with id 'CybotCookiebotDialogBodyContentText'. Consider using a color contrast analyzer tool to find a suitable color combination that meets the minimum contrast ratio thresholds.
View 26 affected elements
Component · Ref M6O8KE
Affected pagehttps://stm.dk/
Element#CybotCookiebotDialogBodyContentText
Accessible nameWe use first and third party cookies for web analytics, user experience optimisation, security, video and access to certain social media features. You are at all times capable of changing or revoking your consent by clicking the link “Cookies” at the bottom of the page. You are also able to read more about our use of cookies by clicking “Show details” below.
<a href="/statsministeren/fotoarkiv/nordisk-sommermoede-i-danmark/" class="pl-item__inner-link">
Nordisk sommermøde i Danmark
</a>
Medium
No skip link to main content
WCAG 2.4.1 (A)10 instances5 inspected pages
The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.
Why it matters
The page offers no bypass mechanism, so keyboard users must tab through the full navigation before reaching the main content on every page.
Recommended correction
Add a skip link to the main content area, allowing keyboard users to bypass the navigation on each page. This can be achieved by adding an anchor link with a visible or hidden text, such as 'Skip to main content', that links to the main content area.
View 10 affected elements
Component · Ref OGECPH
Affected pagehttps://stm.dk/
Elementhtml > body
Accessible nameConsentDetails[#IABV2SETTINGS#]AboutThis website uses cookiesWe use first and third party cookies for web analytics, user experience optimisation, security, video and access to certain social media features. You are at all times capable of changing or revoking your consent by clicking the link “Cookies” at the bottom of the page. You are also able to read more about our use of cookies by clicking “Show details” below. [#GPC_BANNER_ICON#][#GPC_TOAST_TEXT#]Consent SelectionNecessary Preferences Statistics Marketing Show detailsDetailsNecessary 3 Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.consent.cookiebot.euvideo.stm.dk2CookieConsent [x2]Stores the user's cookie consent state for the current domainMaximum Storage Duration: 1 yearType: HTTP Cookiestm.dk1TS#Used to ensure website security and fraud detection.Maximum Storage Duration: SessionType: HTTP CookiePreferences 0 Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.We do not use cookies of this type.Statistics 3 Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.video.stm.dk2ad_session_id [x2]This cookie is used to remember the visitor’s preferences such as language etc. across subpages on the website.Maximum Storage Duration: 1 dayType: HTTP Cookiewww.twentythree.com1startTimeRegisters the start time for website’s games. Maximum Storage Duration: SessionType: HTML Local StorageMarketing 0 Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.We do not use cookies of this type.Unclassified 1Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.stm.dk1MY_SESSIONPendingMaximum Storage Duration: SessionType: HTTP CookieCross-domain consent[#BULK_CONSENT_DOMAINS_COUNT#][#BULK_CONSENT_TITLE#]List of domains your consent applies to: [#BULK_CONSENT_DOMAINS#]Cookie declaration last updated on 8/14/26 by Cookiebot[#IABV2_TITLE#][#IABV2_BODY_INTRO#][#IABV2_BODY_LEGITIMATE_INTEREST_INTRO#][#IABV2_BODY_PREFERENCE_INTRO#][#IABV2_LABEL_PURPOSES#][#IABV2_BODY_PURPOSES_INTRO#][#IABV2_BODY_PURPOSES#][#IABV2_LABEL_FEATURES#][#IABV2_BODY_FEATURES_INTRO#][#IABV2_BODY_FEATURES#][#IABV2_LABEL_PARTNERS#][#IABV2_BODY_PARTNERS_INTRO#][#IABV2_BODY_PARTNERS#]About Do not sell or share my personal informationAllow all cookiesCustomizeAllow selectionUse necessary cookies only
/* IDENTITY GROUP */
:root {
--logo-width: 5rem;
}
/* NAVIGATION GROUP */
:root {
--header-background-color: #ffffff;
--header-text-color: #343434;
--header-active-state-color: #a00f07;
--nav-main-container-background-color: #ffffff;
--nav-main-container-text-color: #000000;
--nav-main-active-state-color: #a00f07;
--nav-main-border-top: 1px solid transparent;
--nav-main-border-bottom: 3px solid #A00f07;
--nav-main-top: 4.375rem;
}
/* FOOTER GROUP */
:root {
--footer-background-color: #ffffff;
}
/* COLORS GROUP */
:root {
/* Default colors */
--color-body-text: #343434;
--color-default-links: #a00f07;
/* A theme */
--color-a: #a00f07;
--color-a-dark: #69100b;
--color-a-light: #c94c45;
--color-a-text: #ffffff;
/* B theme */
--color-b: #017991;
--color-b-dark: #144b56;
--color-b-light: #ffffff;
--color-b-text: #ffffff;
/* C theme */
--color-c: #4c5861;
--color-c-dark: #7790a4;
--color-c-light: #92a6b6;
--color-c-text: #ffffff;
/* D theme */
--color-d: #4c5861;
--color-d-text: #ffffff;
/* E theme */
/* F theme */
/* G theme */
/* H theme */
}
/* TYPOGRAPHY GROUP */
@font-face {
font-family: "headings-font";
font-weight: 400;
src: url("/media/aazeeqpx/playfair-display-v19-latin-regular.woff2") format("woff2");
font-display: swap;
font-style: normal;
}
:root {
--headings-font-weight: 700;
}
:root {
}
/* MODULE DEFAULTS GROUP */
/* MODULE DEFAULTS GROUP: Shared module settings */
:root {
}
/* MODULE DEFAULTS GROUP: Charts */
:root {
}
/* MODULE DEFAULTS GROUP: Forms */
:root {
}
/* MODULE DEFAULTS GROUP: RTE */
:root {
--rte-generate-clickable-anchors: false;
}
/* LAYOUT GROUP */
:root {
--color-body-background: #f7f7f7;
}
window.themeSettings = {
rteGenerateClickableAnchorsDictionary: "Link til denne sektion",
dateFormat: "Short date (DA: 18.12.2024) (EN: 12/18/2024)",
docReader: {
cid: "",
showDocReader: false,
openDocumentDictionary: "Lyt til dette dokument med ReadSpeaker docReader",
listenLabelDictionary: "Lyt",
lang: "da",
},
links: {
openDocumentsInNewTab: false,
openExternalLinksInNewTab: false
}
}
Gå til indhold
Skift cookie indstillinger
Gå til forsiden
Kontakt
Presse
Ledige stillinger
English
Hvad søger du? - Indsæt søgeord for at søge på hjemmesiden.
Søg
Fold søgefelt ud
Menu
Statsministeriet
Statsministeriet - Flere links
…[truncated by Evolize: exceeded D1 value limit]
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Why it matters
Interactive controls are smaller than the 24×24px minimum target size, making them hard to activate reliably by touch.
Recommended correction
Increase the size of the touch target to at least 24x24 pixels to make it easier for users to tap on mobile devices. Consider adding padding or increasing the font size of the interactive element.
Evolize inspects publicly accessible website pages using automated browser-based testing and deterministic accessibility rules. Automated testing can identify many reproducible technical issues but cannot determine complete WCAG or legal compliance.
Publicly accessible surfaces only — no credentials, private systems, or source-code access.
Findings apply to the pages and states successfully inspected; automated analysis may not detect every issue.
Results reflect the site at the scan date and may have changed since.
Evolize provides digital risk intelligence and does not provide legal advice, certify compliance, or guarantee that litigation will not occur. Methodology · Security · Example assessment
07 · Continuous monitoring
This public report captures one assessment. Evolize monitoring rescans the website, detects new and recurring findings, tracks changes over time and verifies corrections.