Skip to content
https://schalke04.de

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
8
REVIEW
3
PASS
13
INFO
0
Checks
24
13 PASS 3 REVIEW 8 FIX
D
Landmark Structure
Action
8 landmarks
FIX
8 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 MAIN (missing!) CONTENTINFO footer

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
Mobile Keyboard & Autofill
Action
6/6 eligible field(s) missing autocomplete or inputmode
FIX
6/6 eligible field(s) missing autocomplete or inputmode
Warning::
3 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email, current-password.
Got: <input type="email" name="email" id="field-email-account">, <input type="password" name="password" id="field-password-account">, <input type="email" name="email" id="field-newsletter-email">
Warning::
3 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: search, email.
Got: <input type="search" name="search" id="field-search">, <input type="email" name="email" id="field-email-account">, <input type="email" name="email" id="field-newsletter-email">
D
Tabindex Anti-Patterns
Action
0 positive, 16 -1-on-focusable
FIX
0 positive, 16 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
D
Iframe Accessibility
Action
6/6 iframe(s) missing title; 0 placeholder(s)
FIX
6/6 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://partner.schalke04.de/partner/s04-shop/cw_45_2026_Adventskalender_billbo…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://partner.schalke04.de/partner/s04-shop/cw_45_2026_Adventskalender_billbo…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://partner.schalke04.de/partner/s04-shop/cw_45_2026_Adventskalender_billbo…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://partner.schalke04.de/partner/sky/cw_42_2026_lb2/billboard-desktop.htm")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://partner.schalke04.de/partner/sky/cw_42_2026_lb2/billboard-desktop.htm")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://partner.schalke04.de/partner/sky/cw_42_2026_lb2/billboard-mobile.htm")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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: #ffffff
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
Form Input Quality
2 input-semantic issue(s) across 6 form control(s)
REVIEW
2 input-semantic issue(s) across 6 form control(s)
Info::
1 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="password">.
Info::
2 login form field(s) missing `autocomplete=username` (or `email`)
On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="email">, <input type="email" name="email">.
C
Favicon & Branding
Action
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::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 80/100 — 7 failing, 30 passed
REVIEW
80

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
1 div.stage-container > div.stage-slider > ul.slick-dots > li#slick-slide10

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
1 2 3 4 5 div.col-xl-16 > div.stage-container > div.stage-slider > ul.slick-dots

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 div.stage-container > div.stage-slider > ul.slick-dots > li#slick-slide10

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Aus vielen Anteilen wird gemeinsame Stärke: Jetzt Anteile an der Auf Schalke eG… div.stage-container > div.stage-slider > div.slick-list > div.slick-track
Soufiane El-Faouzi trainiert wieder mit der Mannschaft PERSONAL 4.11.26 O… div.module > div.card-deck > div.slick-list > div.slick-track

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Installieren body#top > div.smartbanner > a.smartbanner__button > span.smartbanner__button__label

These are opportunities to improve the legibility of your content.

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.col-xl-24 > div > div.module > iframe#campaign-717981-sm div.col-xl-24 > div > div.module > iframe#campaign-717981-sm
div.col-xl-24 > div > div.module > iframe#campaign-711647-sm div.col-xl-24 > div > div.module > iframe#campaign-711647-sm

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
Menu div.container-fluid > div.header-top-bar > div.header-mobile-navigation-indicator > button.btn
○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]`s are contained by their required parent element
●`[role]` values are valid
●`[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
●ARIA toggle fields have accessible names
●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.
●`[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
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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 `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
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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
Heading Hierarchy
51 headings
PASS
51 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 FC Gelsenkirchen-Schalke 04 e.V.
  • H2 Suche
  • H2 Login
  • H1 FC Gelsenkirchen-Schalke 04 e.V. duplicate H1
  • H2 Aus vielen Anteilen wird gemeinsame Stärke: Jetzt Anteile an der Auf Schalke eG zeichnen!
  • H2 Nullvier Knappen auf Länderspielreise
  • H2 Youri Mulder: Wir haben Haltung gezeigt
  • H2 Trotz zahlreicher guter Chancen: S04 unterliegt knapp in Hoffenheim
  • H2 Die Extended Version der Sky Original Doku „Mythos Schalke“
  • H2 Aus vielen Anteilen wird gemeinsame Stärke: Jetzt Anteile an der Auf Schalke eG zeichnen!
  • H2 Nullvier Knappen auf Länderspielreise
  • H2 Newscenter
  • H3 Kevin Müller: Wir müssen Widerstände brechen und überwinden
  • H3 DurchGEklickt: #TSGS04 in Bildern
  • H3 Deutlicher Erfolg: S04-Frauen schlagen den MSV Duisburg mit 4:0
  • H3 Timo Becker fällt wegen Fuß-Verletzung aus
  • H2 Dritte Ticket-Verkaufsphase der Saison: Alle wichtigen Informationen
  • H2 Spieltage 12 bis 18 zeitgenau angesetzt
  • H2 Soufiane El-Faouzi trainiert wieder mit der Mannschaft
  • H2 Olympia-Bronze-Duo für Schalke: Vanessa Voigt und Philipp Nawrath bilden Team Deutschland 2
  • H2 Kooperationsvereinbarung endet: Schalke 04 stärkt vereinseigene Betreuung der Fanclubs
  • H2 Wichtiger denn je: Demokratische Initiative startet Banneraktion
  • H2 Dritte Ticket-Verkaufsphase der Saison: Alle wichtigen Informationen
  • H2 Spieltage 12 bis 18 zeitgenau angesetzt
  • H2 Soufiane El-Faouzi trainiert wieder mit der Mannschaft
  • H2 Olympia-Bronze-Duo für Schalke: Vanessa Voigt und Philipp Nawrath bilden Team Deutschland 2
  • H2 Kooperationsvereinbarung endet: Schalke 04 stärkt vereinseigene Betreuung der Fanclubs
  • H2 Wichtiger denn je: Demokratische Initiative startet Banneraktion
  • H2 Dritte Ticket-Verkaufsphase der Saison: Alle wichtigen Informationen
  • H2 Spieltage 12 bis 18 zeitgenau angesetzt
  • H2 S04TV
  • H2 FANBELANGE
  • H2 BARRIEREFREIHEIT
  • H2 MUSEUM & ARENA-TOUREN
  • H2 KONTAKT & SERVICE
  • H2 Fanshop
  • H2 SCHALKE 04 APP
  • H2 TICKETBÖRSE
  • H2 MITFAHRBÖRSE
  • H2 KNAPPEN-KOMMENTAR
  • H2 Tausend Freunde, die zusammen­stehn.
  • H2 KNAPPENKIDS
  • H2 FUSSBALLSCHULE
  • H2 NACHHALTIGKEIT
  • H2 SCHALKE HILFT!
  • H2 Werde jetzt Mitglied
  • H2 KNAPPENSCHMIEDE
  • H2 FRAUEN
  • H2 TRADITIONSELF
  • H2 SPORTABTEILUNGEN
  • H2 Jetzt den S04-Newsletter abonnieren

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
17 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 17 all-caps heading(s)
A+
Alt Text Quality
All 66 images OK
PASS
All 66 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
3 decorative image(s) correctly marked
Info::
61 image(s) with good alt text
66 images 61 good alt text 3 decorative
IssueCount
too long2 image(s)
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#field-searchsearchSuchwortfor/id
#field-email-accountemailE-Mailfor/id
#field-password-accountpasswordPasswortfor/id
#field-newsletter-agecheckboxnone
#field-newsletter-privacycheckboxnone
#field-newsletter-emailemailE-Mail-Adressefor/id
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Document Language
Lang attribute set to "de-DE"
PASS
Lang attribute set to "de-DE"
Info::
<html lang="de-DE"> is set and valid
Got: de-DE
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 4 visible text node(s) render at >= 12 CSS pixels
PASS
All 4 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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 FC Gelsenkirchen-Schalke 04 e.V. ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
A+
Mobile UX Depth
3 mobile-depth signal(s) detected
PASS
3 mobile-depth signal(s) detected
Info::
iOS smart-banner opt-in present (`apple-itunes-app`)
The page declares a companion iOS app via `<meta name="apple-itunes-app" content="app-id=...">`. iOS Safari shows a smart banner offering to open the page in the app, with an unobtrusive 'X' to dismiss. Recommended when you have a published companion app.
Info::
Android smart-banner opt-in present (`google-play-app`)
The page declares a companion Android app via `<meta name="google-play-app" content="app-id=...">` (or `google-play-id`). Combined with Chrome's intent: protocol or App Links, this lets supporting browsers offer to open the page in the app.
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
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
h2 Suche21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Login21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aus vielen Anteilen …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nullvier Knappen auf…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Youri Mulder: Wir ha…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trotz zahlreicher gu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Die Extended Version…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aus vielen Anteilen …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nullvier Knappen auf…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dritte Ticket-Verkau…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Spieltage 12 bis 18 …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Soufiane El-Faouzi t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Olympia-Bronze-Duo f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Kooperationsvereinba…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Wichtiger denn je: D…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dritte Ticket-Verkau…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Spieltage 12 bis 18 …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Soufiane El-Faouzi t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Olympia-Bronze-Duo f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Kooperationsvereinba…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