Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

4 landmarks

FIX

4 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

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

No contentinfo (footer) landmark

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

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

Link & Button Quality

Action

40 issue(s) across 57 links and 6 buttons

FIX

40 issue(s) across 57 links and 6 buttons

34 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; #; #; #; #; #; https://rivella.ch; https://simmentalerbier.ch/; #; https://www.lateltin.com/ (+24 more)

4 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://portnerag.ch/wp-content/uploads/2026/04/Festplatzpreise_Portner_26041…; https://www.instagram.com/portnerag; https://www.facebook.com/PortnerAG/; https://portnerag.ch/datenschutz/

6 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.pswp__button (#1015 on page); button.pswp__button (#1016 on page); button.pswp__button (#1017 on page); button.pswp__button (#1018 on page); button.pswp__button (#1025 on page); button.pswp__button (#1026 on page)

19 link(s) with descriptive text

57 links

34 empty

0 generic text

4 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://portnerag.ch/wp-content/uploads/…	Preisliste 2026	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://rivella.ch	(empty)	empty	Add link text or aria-label
https://simmentalerbier.ch/	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://www.lateltin.com/	(empty)	empty	Add link text or aria-label
https://diwisa.ch/	(empty)	empty	Add link text or aria-label
https://www.moehl.ch/de/	(empty)	empty	Add link text or aria-label
https://felsenau.ch/	(empty)	empty	Add link text or aria-label
https://www.rugenbraeu.ch	(empty)	empty	Add link text or aria-label
https://www.feldschloesschen.ch/	(empty)	empty	Add link text or aria-label
https://www.schenk-wine.ch/de	(empty)	empty	Add link text or aria-label
https://www.appenzellerbier.ch/de/home.h…	(empty)	empty	Add link text or aria-label
https://de.coca-cola.ch/	(empty)	empty	Add link text or aria-label
https://www.doppelleuboxer.ch/	(empty)	empty	Add link text or aria-label
https://www.swissalpineherbs.ch/	(empty)	empty	Add link text or aria-label
https://www.bataillard.ch/	(empty)	empty	Add link text or aria-label
https://www.appenzeller.com/	(empty)	empty	Add link text or aria-label
https://www.eggerbier.ch/	(empty)	empty	Add link text or aria-label
https://rivella.ch	(empty)	empty	Add link text or aria-label
https://simmentalerbier.ch/	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://www.lateltin.com/	(empty)	empty	Add link text or aria-label
https://diwisa.ch/	(empty)	empty	Add link text or aria-label
https://www.moehl.ch/de/	(empty)	empty	Add link text or aria-label
https://felsenau.ch/	(empty)	empty	Add link text or aria-label
https://www.rugenbraeu.ch	(empty)	empty	Add link text or aria-label
https://www.feldschloesschen.ch/	(empty)	empty	Add link text or aria-label
https://www.schenk-wine.ch/de	(empty)	empty	Add link text or aria-label
https://www.instagram.com/portnerag	icon-social_instagram_square	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/PortnerAG/	icon-social_facebook_circle	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://portnerag.ch/datenschutz/	Privatsphären Policy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

19 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; #; #; #; #; #; https://rivella.ch; https://simmentalerbier.ch/; #; https://www.lateltin.com/ (+24 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://portnerag.ch/wp-content/uploads/2026/04/Festplatzpreise_Portner_26041…; https://www.instagram.com/portnerag; https://www.facebook.com/PortnerAG/; https://portnerag.ch/datenschutz/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.pswp__button (#1015 on page); button.pswp__button (#1016 on page); button.pswp__button (#1017 on page); button.pswp__button (#1018 on page); button.pswp__button (#1025 on page); button.pswp__button (#1026 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

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.

Lighthouse Accessibility Audits

Action

Score 68/100 — 7 failing, 17 passed

FIX

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.

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
Ich Akzeptiere `div.be-gdpr-cookie-notice-bar > div.be-gdpr-cookie-notice-wrap > div.be-gdpr-cookie-notice-actions > div.be-gdpr-cookie-notice-button`

These are opportunities to improve the legibility of your content.

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
li.current > div.be-slide-bg-holder > div.be-slide-bg > img `li.current > div.be-slide-bg-holder > div.be-slide-bg > img`
li > div.be-slide-bg-holder > div.be-slide-bg > img `li > div.be-slide-bg-holder > div.be-slide-bg > img`
li > div.be-slide-bg-holder > div.be-slide-bg > img `li > div.be-slide-bg-holder > div.be-slide-bg > img`
li > div.be-slide-bg-holder > div.be-slide-bg > img `li > div.be-slide-bg-holder > div.be-slide-bg > img`
li.current > div.be-slide-bg-holder > div.be-slide-bg > img `li.current > div.be-slide-bg-holder > div.be-slide-bg > img`
li > div.be-slide-bg-holder > div.be-slide-bg > img `li > div.be-slide-bg-holder > div.be-slide-bg > img`
li.current > div.be-slide-bg-holder > div.be-slide-bg > img `li.current > div.be-slide-bg-holder > div.be-slide-bg > img`
li > div.be-slide-bg-holder > div.be-slide-bg > img `li > div.be-slide-bg-holder > div.be-slide-bg > img`
li > div.be-slide-bg-holder > div.be-slide-bg > img `li > div.be-slide-bg-holder > div.be-slide-bg > img`
li > div.be-slide-bg-holder > div.be-slide-bg > img `li > div.be-slide-bg-holder > div.be-slide-bg > img`
li > div.be-slide-bg-holder > div.be-slide-bg > img `li > div.be-slide-bg-holder > div.be-slide-bg > img`
li > div.be-slide-bg-holder > div.be-slide-bg > img `li > div.be-slide-bg-holder > div.be-slide-bg > img`

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.tatsu-column-pad > div.component > nav.component-nav > a.prev `div.tatsu-column-pad > div.component > nav.component-nav > a.prev`
div.tatsu-column-pad > div.component > nav.component-nav > a.next `div.tatsu-column-pad > div.component > nav.component-nav > a.next`
div.tatsu-column-pad > div.component > nav.component-nav > a.prev `div.tatsu-column-pad > div.component > nav.component-nav > a.prev`
div.tatsu-column-pad > div.component > nav.component-nav > a.next `div.tatsu-column-pad > div.component > nav.component-nav > a.next`
div.tatsu-column-pad > div.component > nav.component-nav > a.prev `div.tatsu-column-pad > div.component > nav.component-nav > a.prev`
div.tatsu-column-pad > div.component > nav.component-nav > a.next `div.tatsu-column-pad > div.component > nav.component-nav > a.next`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > a`
div.owl-stage > div.owl-item > li.carousel-item > a `div.owl-stage > div.owl-item > li.carousel-item > 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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.tatsu-column-pad-wrap > div.tatsu-column-pad > div.carousel-wrap > ul.be-owl-carousel `div.tatsu-column-pad-wrap > div.tatsu-column-pad > div.carousel-wrap > ul.be-owl-carousel`

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`
div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item `div.owl-stage-outer > div.owl-stage > div.owl-item > li.carousel-item`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

These items highlight common accessibility best practices.

○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>`

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

○`[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]`s are contained by their required parent element

○`[role]` values are valid

○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

○Buttons have an accessible name

○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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○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

○Tables have different content in the summary attribute and `<caption>`.

○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.

Alt Text Quality

Action

12 of 44 images have issues

REVIEW

12 of 44 images have issues

12 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

27 decorative image(s) correctly marked

5 image(s) with good alt text

44 images 5 good alt text 27 decorative 12 missing

Issue	Count
missing	12 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

Mobile-Readable Font Sizes

98% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

98% of visible text renders at >= 12 CSS px (1 below threshold)

1 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.7px ("Copyright Portner AG 2025 | Alle Rechte ...").

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA

h3 Mission

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Deine Vorteile auf einen Blick

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Anfrage

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Partner

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 Mission	1.00:1	3.0:1	#000000	#000000	Fail
h3 Deine Vorteile auf e…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Anfrage	1.00:1	3.0:1	#000000	#000000	Fail
h3 Partner	1.00:1	3.0:1	#000000	#000000	Fail
title Portner AG - Abholma…	15.59:1	4.5:1	#000000	#FFDD00	Pass
a Home	15.59:1	4.5:1	#000000	#FFDD00	Pass
a Kontakt	15.59:1	4.5:1	#000000	#FFDD00	Pass
a Home	16.34:1	4.5:1	#000000	#F8E558	Pass
a Kontakt	18.32:1	4.5:1	#000000	#EDF2DB	Pass
strong Portner AG	18.32:1	3.0:1	#000000	#EDF2DB	Pass
span Getränkeservice \| A…	18.32:1	4.5:1	#000000	#EDF2DB	Pass
span Unsere Öffnungszeit…	18.32:1	4.5:1	#000000	#EDF2DB	Pass
strong Getränkeabholmarkt:	18.32:1	3.0:1	#000000	#EDF2DB	Pass
strong Mo – Fr	18.32:1	3.0:1	#000000	#EDF2DB	Pass
span 08:00 – 12:15 Uhr …	18.32:1	4.5:1	#000000	#EDF2DB	Pass
strong Samstag	18.32:1	3.0:1	#000000	#EDF2DB	Pass
span 08:00 – 16:00 Uhr …	18.32:1	4.5:1	#000000	#EDF2DB	Pass
strong Büro / Telefon:	18.32:1	3.0:1	#000000	#EDF2DB	Pass
strong Mo – Fr	18.32:1	3.0:1	#000000	#EDF2DB	Pass
span 08:00 – 11:00 Uhr …	18.32:1	4.5:1	#000000	#EDF2DB	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+

Heading Hierarchy

25 headings

PASS

25 headings

Single H1 present

1 empty heading(s)

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

H1 Portner AG
H2 Getränkeservice | Abholmarkt | Getränkelieferung in der Umgebung Riggisberg, Bern und Thun
H3 Unsere Öffnungszeiten
H3 Aktuelles & Infos
H4 Frohe Auffahrt
H4 Festanfragen
H3 Mission
H4 Durch unsere jahrelange Erfahrung machen wir dein Fest zum Erfolg!
H4 Abholmarkt
H5 Grosse Auswahl an Getränken & Festmaterial zu top Preisen
H4 Lieferdienst & Festmaterial
H5 Geburtstagsparty, Hochzeit oder Firmenevent: Wir sind dein Partner in Sachen Festmaterial!
H4 Geschenke und Wein
H5 Individuell für dich und deine Liebsten zusammengestellt
H5 (empty)
H3 Deine Vorteile auf einen Blick
H4 Mengenberechnung
H4 Liefer- und Pikettdienst
H4 Unterstützung
H4 Mitarbeiter:innen
H4 Artikel
H4 Pallettenplätze
H3 Anfrage
H3 Partner
H3 Info/Links

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+

Heading Text Quality

All 25 heading(s) have substantive, well-formed text

PASS

All 25 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Method
input	checkbox	none
input	checkbox	none
input	checkbox	none

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

3 form control(s) checked, no input-semantic issues

PASS

3 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "de-CH"

PASS

Lang attribute set to "de-CH"

<html lang="de-CH"> is set and valid

Got: de-CH

A+

Tabindex Anti-Patterns

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Portner AG ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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