Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 REVIEW 6 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>.

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

8 issue(s) across 38 links and 2 buttons

FIX

8 issue(s) across 38 links and 2 buttons

6 link(s) with no accessible text

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

Got: https://gdpr.eu/; https://research-and-innovation.ec.europa.eu/funding/funding-opportunities/fu…; https://gdpr.eu/gdpr-in-2020/; https://gdpr.eu/italy-fines-energy-company-for-multiple-gdpr-violations/; https://gdpr.eu/gdpr-vs-lgpd/; #

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://ec.europa.eu/commission/priorities/justice-and-fundamental-rights/dat… ("here"); https://proton.me/business/gdpr?ref=gdpreu ("Learn more")

2 link(s) open in new tab without warning

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

Got: http://www.facebook.com/sharer.php?u=https://gdpr.eu/; http://twitter.com/share?url=https://gdpr.eu/

28 link(s) with descriptive text

38 links

6 empty

2 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
http://www.facebook.com/sharer.php?u=htt…	Facebook	new tab	Add '(opens in new tab)' to text
http://twitter.com/share?url=https://gdp…	Twitter	new tab	Add '(opens in new tab)' to text
https://gdpr.eu/	(empty)	empty	Add link text or aria-label
https://research-and-innovation.ec.europ…	(empty)	empty	Add link text or aria-label
https://gdpr.eu/gdpr-in-2020/	(empty)	empty	Add link text or aria-label
https://gdpr.eu/italy-fines-energy-compa…	(empty)	empty	Add link text or aria-label
https://gdpr.eu/gdpr-vs-lgpd/	(empty)	empty	Add link text or aria-label
https://ec.europa.eu/commission/prioriti…	here	generic text	Replace with descriptive text
Before: here Suggested: 2018 Reform Eu Data Protection Rules En
#	(empty)	empty	Add link text or aria-label
https://proton.me/business/gdpr?ref=gdpr…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Gdpr?Ref=Gdpreu

30 links and buttons have descriptive text

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

https://gdpr.eu/; https://research-and-innovation.ec.europa.eu/funding/funding-opportunities/fu…; https://gdpr.eu/gdpr-in-2020/; https://gdpr.eu/italy-fines-energy-company-for-multiple-gdpr-violations/; https://gdpr.eu/gdpr-vs-lgpd/; #

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

Generic link text like 'click here' doesn't describe the destination.

https://ec.europa.eu/commission/priorities/justice-and-fundamental-rights/dat… ("here"); https://proton.me/business/gdpr?ref=gdpreu ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

http://www.facebook.com/sharer.php?u=https://gdpr.eu/; http://twitter.com/share?url=https://gdpr.eu/

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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: App

192x192 icon present

PWA Install Criteria Not Installable

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

Name App Icons 6 icon(s)

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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

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

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

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

Heading Hierarchy

20 headings, 2 skip(s)

REVIEW

20 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Complete guide to GDPR compliance
H4 GDPR Overview skipped
H5 What is GDPR, the EU’s new data protection law?
H5 Everything you need to know about the “Right to be forgotten”
H5 What are the GDPR Fines?
H4 GDPR Compliance
H5 Data protection and working remotely
H5 Cookies, the GDPR, and the ePrivacy Directive
H5 Everything you need to know about GDPR compliance
H4 News & Updates
H5 How the GDPR could change in 2020
H5 Italy fines Eni Gas e Luce €11.5 million for multiple GDPR violations
H5 What is the LGPD? Brazil’s version of the GDPR
H4 GDPR compliance checklist
H4 GDPR Forms and Templates
H6 About GDPR.EU skipped
H5 Getting Started
H5 Templates
H5 Technical Review
H5 About Us

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="s" id="search-form-69e5dec3249a9">; <input type="search" name="s" id="search-form-69e5dec324a7e">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-form-69e5dec3249a9	search	(Search...)	placeholder only
#search-form-69e5dec324a7e	search	(Search...)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Favicon & Branding

Action

20 icon(s) detected

REVIEW

20 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 9 fail WCAG AA

REVIEW

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

11 pass 9 fail WCAG AA 1 pass AA only

h1 Complete guide to GDPR compliance

1.83:1

#000000

#283A56

needs 3.0:1 (large text)

32px · above the fold · over background image/gradient

span Search

1.84:1

#000000

#283A59

needs 4.5:1 (normal text)

16px · above the fold

a Home

1.81:1

#000000

#283955

needs 4.5:1 (normal text)

16px · above the fold

a Checklist

1.76:1

#000000

#283754

needs 4.5:1 (normal text)

16px · above the fold

a FAQ

2.26:1

#000000

#3B485B

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a GDPR

1.93:1

#000000

#313D56

needs 4.5:1 (normal text)

16px · above the fold

a News & Updates

1.81:1

#000000

#283955

needs 4.5:1 (normal text)

16px · above the fold

p GDPR.eu is a resource for organizations …

2.24:1

#000000

#384667

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

p Here you’ll find a library of straight…

2.46:1

#000000

#3C4C6F

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Complete guide to GD…	1.83:1	3.0:1	#000000	#283A56	Fail
title General Data Protect…	17.62:1	4.5:1	#000000	#EBEBEB	Pass
span Facebook	16.67:1	4.5:1	#000000	#E5E5E5	Pass
span Twitter	16.67:1	4.5:1	#000000	#E5E5E5	Pass
span Search	5.57:1	4.5:1	#000000	#798498	Pass
span Search	1.84:1	4.5:1	#000000	#283A59	Fail
a Home	1.81:1	4.5:1	#000000	#283955	Fail
a Checklist	1.76:1	4.5:1	#000000	#283754	Fail
a FAQ	2.26:1	4.5:1	#000000	#3B485B	Fail
a GDPR	1.93:1	4.5:1	#000000	#313D56	Fail
a News & Updates	1.81:1	4.5:1	#000000	#283955	Fail
p GDPR.eu is a resourc…	2.24:1	4.5:1	#000000	#384667	Fail
p Here you’ll find a…	2.46:1	4.5:1	#000000	#3C4C6F	Fail
p achieve GDPR complia…	11.38:1	4.5:1	#000000	#B9BFCB	Pass
h4 GDPR Overview	21.00:1	3.0:1	#000000	#FFFFFF	Pass
p If you’re new to t…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a What is GDPR, the EU…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p What is the GDPR? Eu…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Everything you need …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Also known as the ri…	21.00:1	4.5: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.

Lighthouse Accessibility Audits

Score 82/100 — 4 failing, 15 passed

REVIEW

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#searchx > div.search-box > form.search-form > button.button `div#searchx > div.search-box > form.search-form > button.button`

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
header#header > div#social > div.container > a `header#header > div#social > div.container > a`
header#header > div#social > div.container > a `header#header > div#social > div.container > a`
nav#nav > div.container > nav#mainmenu > a#menu `nav#nav > div.container > nav#mainmenu > a#menu`
div.col-md-4 > div.news > div.news-post-box > a `div.col-md-4 > div.news > div.news-post-box > a`
div.col-md-4 > div.news > div.news-post-box > a `div.col-md-4 > div.news > div.news-post-box > a`
div.col-md-4 > div.news > div.news-post-box > a `div.col-md-4 > div.news > div.news-post-box > 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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GDPR Overview `div.row > div.col-md-4 > div.section-title > h4`
About GDPR.EU `div.container > div.post-author-details-box > div.post-author-details > h6`

These are opportunities to improve keyboard navigation in your application.

Best practices

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.no-svg `html.no-svg`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

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

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

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

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

○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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

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

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

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

○Image elements have `[alt]` attributes

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

○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

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

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

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 - GDPR.eu ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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