Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 6 REVIEW 3 FIX

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗

Icons 2 icon(s)

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 ✗

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

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

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

7 issue(s) across 8 links and 0 buttons

REVIEW

7 issue(s) across 8 links and 0 buttons

7 link(s) with no accessible text

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

Got: https://www.porsche.com/netherlands/nl/models/911; https://www.porsche.com/netherlands/nl/models/718; https://www.porsche.com/netherlands/nl/models/taycan; https://www.porsche.com/netherlands/nl/models/panamera; https://www.porsche.com/netherlands/nl/models/macan; https://www.porsche.com/netherlands/nl/models/cayenne; https://shop.porsche.com/nl/nl-NL?int_ref=pcom-netherlands/nl&int_medium=banner&int_id=home-component-banner-categories

1 link(s) with descriptive text

8 links

7 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.porsche.com/netherlands/nl/m…	(empty)	empty	Add link text or aria-label
https://www.porsche.com/netherlands/nl/m…	(empty)	empty	Add link text or aria-label
https://www.porsche.com/netherlands/nl/m…	(empty)	empty	Add link text or aria-label
https://www.porsche.com/netherlands/nl/m…	(empty)	empty	Add link text or aria-label
https://www.porsche.com/netherlands/nl/m…	(empty)	empty	Add link text or aria-label
https://www.porsche.com/netherlands/nl/m…	(empty)	empty	Add link text or aria-label
https://shop.porsche.com/nl/nl-NL?int_re…	(empty)	empty	Add link text or aria-label

1 links and buttons have descriptive text

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

https://www.porsche.com/netherlands/nl/models/911; https://www.porsche.com/netherlands/nl/models/718; https://www.porsche.com/netherlands/nl/models/taycan; https://www.porsche.com/netherlands/nl/models/panamera; https://www.porsche.com/netherlands/nl/models/macan; https://www.porsche.com/netherlands/nl/models/cayenne; https://shop.porsche.com/nl/nl-NL?int_ref=pcom-netherlands/nl&int_medium=banner&int_id=home-component-banner-categories

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Porsche ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 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 Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #fff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

h1 Anticipation revving up.

1.02:1

#000000

#030306

needs 3.0:1 (large text)

32px · top of page (header area)

h2 Vind uw nieuwe en gebruikte Porsche bij …

1.02:1

#000000

#030305

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ontdek de Porsche Lifestyle

1.02:1

#000000

#030305

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ontdek

1.02:1

#000000

#030305

needs 3.0:1 (large text)

24px · bottom of viewport

title Porsche Nederland | Officiële website

1.02:1

#000000

#030306

needs 4.5:1 (normal text)

16px · top of page (header area)

p-text 6dagen : 17uur : 37min : 48sec

1.02:1

#000000

#030306

needs 4.5:1 (normal text)

16px · top of page (header area)

p-text Experience the world premiere now

1.02:1

#000000

#030305

needs 4.5:1 (normal text)

16px · top of page (header area)

p-link Discover more

1.02:1

#000000

#030305

needs 4.5:1 (normal text)

16px · above the fold

p Cayenne Turbo Electric: Elektrisch energ…

1.02:1

#000000

#030305

needs 4.5:1 (normal text)

16px · above the fold

span Uw Porsche reis begint nu.

1.02:1

#000000

#030305

needs 4.5:1 (normal text)

16px · above the fold

p-text Benzine

1.02:1

#000000

#030405

needs 4.5:1 (normal text)

16px · above the fold

p-text Iconische tweedeurs sportwagen met achte…

1.02:1

#000000

#030405

needs 4.5:1 (normal text)

16px · above the fold

span Ontdek

1.02:1

#000000

#030305

needs 4.5:1 (normal text)

16px · above the fold

p-text Benzine

1.04:1

#000000

#070708

needs 4.5:1 (normal text)

16px · above the fold

p-text Middenmotor 2-zits sportwagen.

1.04:1

#000000

#070708

needs 4.5:1 (normal text)

16px · above the fold

span Ontdek

1.04:1

#000000

#070709

needs 4.5:1 (normal text)

16px · mid-page

p-text Elektrisch

1.06:1

#000000

#090A0A

needs 4.5:1 (normal text)

16px · mid-page

p-text 4-deurs, 4/5-zits, elektrische sportwage…

1.05:1

#000000

#080809

needs 4.5:1 (normal text)

16px · mid-page

span Ontdek

1.04:1

#000000

#060608

needs 4.5:1 (normal text)

16px · mid-page

p-text Hybride

1.03:1

#000000

#050507

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Anticipation revving…	1.02:1	3.0:1	#000000	#030306	Fail
h2 Vind uw nieuwe en ge…	1.02:1	3.0:1	#000000	#030305	Fail
h2 Ontdek de Porsche Li…	1.02:1	3.0:1	#000000	#030305	Fail
h2 Ontdek	1.02:1	3.0:1	#000000	#030305	Fail
title Porsche Nederland \| …	1.02:1	4.5:1	#000000	#030306	Fail
p-text 6dagen : 17uur : 37m…	1.02:1	4.5:1	#000000	#030306	Fail
p-text Experience the world…	1.02:1	4.5:1	#000000	#030305	Fail
p-link Discover more	1.02:1	4.5:1	#000000	#030305	Fail
p Cayenne Turbo Electr…	1.02:1	4.5:1	#000000	#030305	Fail
span Uw Porsche reis begi…	1.02:1	4.5:1	#000000	#030305	Fail
p-text Benzine	1.02:1	4.5:1	#000000	#030405	Fail
p-text Iconische tweedeurs …	1.02:1	4.5:1	#000000	#030405	Fail
span Ontdek	1.02:1	4.5:1	#000000	#030305	Fail
p-text Benzine	1.04:1	4.5:1	#000000	#070708	Fail
p-text Middenmotor 2-zits s…	1.04:1	4.5:1	#000000	#070708	Fail
span Ontdek	1.04:1	4.5:1	#000000	#070709	Fail
p-text Elektrisch	1.06:1	4.5:1	#000000	#090A0A	Fail
p-text 4-deurs, 4/5-zits, e…	1.05:1	4.5:1	#000000	#080809	Fail
span Ontdek	1.04:1	4.5:1	#000000	#060608	Fail
p-text Hybride	1.03:1	4.5:1	#000000	#050507	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.

A+

Heading Hierarchy

5 headings

PASS

5 headings

Single H1 present

H1 Anticipation revving up.
H2 Uw Porsche reis begint nu.
H2 Vind uw nieuwe en gebruikte Porsche bij uw Porsche Centrum.
H2 Ontdek de Porsche Lifestyle
H2 Ontdek

A+

Alt Text Quality

All 20 images OK

PASS

All 20 images OK

1 decorative image(s) correctly marked

19 image(s) with good alt text

20 images 19 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 23 passed

PASS

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
land of regio wijzigen `div.right-icons > div.icon > phn-country-selector-button.sc-phn-level-0-icons > phn-p-link-pure.sc-phn-country-selector-button`

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

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
a.root `a.root`

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

●Image elements have `[alt]` attributes

●`[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.

●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

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

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

○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

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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

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

○Elements with visible text labels have matching accessible names.

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

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