Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

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

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Link & Button Quality

4 issue(s) across 98 links and 7 buttons

REVIEW

4 issue(s) across 98 links and 7 buttons

4 link(s) with generic text

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

Got: https://globalprivacycontrol.org/#download ("here"); https://globalprivacycontrol.org/orgs ("here"); https://global-privacy-control.vercel.app/ ("here"); https://w3c.github.io/gpc/ ("here")

2 link(s) open in new tab without warning

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

Got: https://twitter.com/globalprivctrl; https://github.com/w3c/gpc

92 link(s) with descriptive text

98 links

0 empty

4 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://twitter.com/globalprivctrl	Follow @globalprivctrl on Twit…	new tab	Add '(opens in new tab)' to text
https://globalprivacycontrol.org/#downlo…	here	generic text	Replace with descriptive text
Before: here Suggested: #Download
https://globalprivacycontrol.org/orgs	here	generic text	Replace with descriptive text
Before: here Suggested: Orgs
https://global-privacy-control.vercel.ap…	here	generic text	Replace with descriptive text
Before: here Suggested: Home page
https://w3c.github.io/gpc/	here	generic text	Replace with descriptive text
Before: here Suggested: Gpc
https://github.com/w3c/gpc	W3C Github	new tab	Add '(opens in new tab)' to text

99 links and buttons have descriptive text

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

https://globalprivacycontrol.org/#download ("here"); https://globalprivacycontrol.org/orgs ("here"); https://global-privacy-control.vercel.app/ ("here"); https://w3c.github.io/gpc/ ("here")

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.

https://twitter.com/globalprivctrl; https://github.com/w3c/gpc

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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: This page could not be found ✓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

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Global Privacy Control

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Global Privacy Control ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name Global Privacy Control Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 2 pass AA only

title Global Privacy Control — Take Control …

1.39:1

#000000

#172A24

needs 4.5:1 (normal text)

16px · top of page (header area)

span Home

1.39:1

#000000

#172A24

needs 4.5:1 (normal text)

16px · top of page (header area)

a About

1.39:1

#000000

#172A24

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Take control of your…	7.07:1	3.0:1	#000000	#62A28D	Pass
h1 Get Involved	5.91:1	3.0:1	#000000	#45967C	Pass
h2 Send the Signal	5.91:1	3.0:1	#000000	#45967C	Pass
h2 Exercise Your Rights	5.91:1	3.0:1	#000000	#45967C	Pass
h2 GPC lets users signa…	5.91:1	3.0:1	#000000	#45967C	Pass
h2 Join over 150 millio…	5.91:1	3.0:1	#000000	#45967C	Pass
h2 Founding Organizatio…	5.91:1	3.0:1	#000000	#45967C	Pass
h2 Featured Press & Ann…	5.91:1	3.0:1	#000000	#45967C	Pass
h2 Frequently Asked Que…	5.91:1	3.0:1	#000000	#45967C	Pass
h3 What is the Global P…	5.91:1	3.0:1	#000000	#45967C	Pass
h3 Who is supporting th…	5.91:1	3.0:1	#000000	#45967C	Pass
h3 I’m a web user. Ho…	5.91:1	3.0:1	#000000	#45967C	Pass
h3 I’m a publisher, d…	5.91:1	3.0:1	#000000	#45967C	Pass
h3 I’m a policymaker.…	5.91:1	3.0:1	#000000	#45967C	Pass
h3 How can I get involv…	5.91:1	3.0:1	#000000	#45967C	Pass
title Global Privacy Contr…	1.39:1	4.5:1	#000000	#172A24	Fail
span Home	1.39:1	4.5:1	#000000	#172A24	Fail
a About	1.39:1	4.5:1	#000000	#172A24	Fail
a Spec	6.43:1	4.5:1	#000000	#499D82	Pass
a For Users	6.98:1	4.5:1	#000000	#5AA28B	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.

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

Heading Hierarchy

16 headings

PASS

16 headings

Multiple H1 headings (2 found)

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

H1 Take control of your privacy.
H2 Turn On GPC
H2 Send the Signal
H2 Exercise Your Rights
H2 GPC lets users signal their desired privacy, just by browsing.
H2 Join over 150 million users.
H2 Founding Organizations
H2 Featured Press & Announcements
H2 Frequently Asked Questions
H3 What is the Global Privacy Control (GPC)?
H3 Who is supporting the development of GPC?
H3 I’m a web user. How can I use GPC to signal my privacy preferences to websites?
H3 I’m a publisher, developer, or other service. How can I support GPC?
H3 I’m a policymaker. How can I support GPC or learn more about how it could apply in my jurisdiction?
H3 How can I get involved in developing the proposed specification?
H1 Get Involved duplicate H1

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+

Alt Text Quality

1 of 38 images have issues

PASS

1 of 38 images have issues

1 image(s) with generic alt text

37 image(s) with good alt text

38 images 37 good alt text 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 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.

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
VIEW FULL SPEC `div.row > div.col-12 > div > a.d-block`
TEST AGAINST THE REFERENCE SERVER `div.row > div.col-12 > div > a.d-block`
GDPR Articles 7 & 21 `p.home-module__1-uu2W__finePrint > small > a.font-weight-bold > u`
VIEW ALL DOWNLOADS `div.row > div.col-12 > div.d-flex > a.home-module__1-uu2W__bottomButton`
VIEW ALL ORGANIZATIONS `section#orgs > div.container > div.d-flex > a.home-module__1-uu2W__bottomButton`
GLOBAL PRIVACY CONTROL `li > a > span > span`
THE WASHINGTON POST `li > a > span > span`
WIRED `li > a > span > span`
TECHCRUNCH `li > a > span > span`
VIEW MORE PRESS `section.home-module__1-uu2W__section > div#press > div.d-flex > a.home-module__1-uu2W__bottomButton`
What is the Global Privacy Control (GPC)? `section#WhatIsGPC > header.faq-list-module__JNrOkq__header > a.px-4 > h3`
VIEW ALL FAQs `section.home-module__1-uu2W__section > div#faq > div.d-flex > a.home-module__1-uu2W__bottomButton`
This site is hosted by GitHub and is subject to its Privacy Policy and Terms of… `div.container > div.row > div.col > p.mb-0`
Content on this site is licensed under a Creative Commons Attribution 4.0 Inter… `div.container > div.row > div.col > p.mb-0`

These are opportunities to improve the legibility of your content.

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

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●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

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

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