Skip to content
https://gnupg.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
49
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Alt Text Quality
Action
2 of 4 images have issues
FIX
2 of 4 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
1 image(s) with good alt text
4 images 1 good alt text 2 missing
IssueCount
missing2 image(s)
too long1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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::
1 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 1 <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
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN CONTENTINFO (missing!)

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

B
Heading Hierarchy
26 headings
REVIEW
26 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 The GNU Privacy Guard
  • H2 Reconquer your privacy
  • H2 News
  • H3 Security advisory T8211 for Libgcrypt   important
  • H3 Libgcrypt 1.12 is the new stable branch (2026-01-29)
  • H3 Security advisory T8044 for GnuPG and Gpg4win   important
  • H3 Debian packages for 2.5.16 are available (2026-01-06)
  • H3 GnuPG 2.5.16 released (2025-12-30)
  • H3 GnuPG 2.5.14 released (2025-11-19)
  • H3 GnuPG 2.5.13 and gpg4win 5.0.0-beta395 released (2025-10-22)
  • H3 GnuPG 2.5.12 released (2025-09-02)
  • H3 New GnuPG merchandise available (2025-09-01)
  • H3 GnuPG 2.5.9 with Debian packages released (2025-07-14)
  • H3 GnuPG 2.5.8 released (2025-05-20)
  • H3 GnuPG 2.5.6 and Gpg4win 5.0.0-Beta190 released (2025-05-09)
  • H3 GnuPG 2.5.5 and Gpg4win 5.0.0-beta145 released (2025-03-10)
  • H3 GnuPG 2.5.2 and Gpg4win 5.0.0-Beta32 released (2024-12-06)
  • H3 GnuPG 2.4.7 and Gpg4win 4.4.0 released (2024-11-27)
  • H3 GnuPG 2.4.6 released (2024-10-29)
  • H3 GnuPG 2.5.1 released with FIPS-203 support (2024-09-12)
  • H3 Our FTP server has been discontinued (2024-08-20)
  • H3 GnuPG 2.5.0 released for public testing (2024-07-05)
  • H3 Libgcrypt 1.11 is the new stable branch (2024-06-19)
  • H3 GnuPG 2.4.5 and Gpg4win 4.3.1 released (2024-03-12)
  • H3 Security advisory for smartcard keys with backup   important
  • H3 GnuPG 2.4.4 released (2024-01-25)

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Lighthouse Accessibility Audits
Action
Score 70/100 — 4 failing, 12 passed
REVIEW
70

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
Home nav > ul > li > span.topmenuitem
Donate nav > ul > li > span.topmenuitem
Software nav > ul > li > span.topmenuitem
Download nav > ul > li > span.topmenuitem
Documentation nav > ul > li > span.topmenuitem
Blog nav > ul > li > a
RFC4880 div#content > div#text-1 > p > a
frontend applications div#content > div#text-1 > p > a
libraries div#content > div#text-1 > p > a
Free Software div#content > div#text-1 > p > a
GNU General Public License div#content > div#text-1 > p > a
download div#content > div#text-1 > p > a
Gpg4win div#content > div#text-1 > p > a
Email Self-Defense div.pure-u-1 > div#text-2 > p > a
Why Some Criticisms Matters More Than Others div#text-3 > ul > li > a
Cleartext Signatures Considered Harmful div#text-3 > ul > li > a
New GnuPG Repositories for Debian, Ubuntu, and Devuan: Stable and Development B… div#text-3 > ul > li > a
all news div.pure-u-1 > div#text-3 > p > a
important div.pure-u-1 > h3#sec-3-1 > span.tag > span.important
Read more div.pure-u-1 > div#text-3-1 > p > a
more div.pure-u-1 > div#text-3-2 > p > a
important div.pure-u-1 > h3#sec-3-3 > span.tag > span.important
Read more div.pure-u-1 > div#text-3-3 > p > a
Debian div.pure-u-1 > div#text-3-4 > p > a
Devuan div.pure-u-1 > div#text-3-4 > p > a
Ubuntu div.pure-u-1 > div#text-3-4 > p > a
repos.gnupg.org div.pure-u-1 > div#text-3-4 > p > a
Read more div.pure-u-1 > div#text-3-5 > p > a
repos.gnupg.org div.pure-u-1 > div#text-3-6 > p > a
Read more div.pure-u-1 > div#text-3-6 > p > a
Gpg4win 5.0 div.pure-u-1 > div#text-3-7 > p > a
Read more div.pure-u-1 > div#text-3-7 > p > a
Read more div.pure-u-1 > div#text-3-8 > p > a
find merchandise div.pure-u-1 > div#text-3-9 > p > a
Debian div.pure-u-1 > div#text-3-10 > p > a
Devuan div.pure-u-1 > div#text-3-10 > p > a
Ubuntu div.pure-u-1 > div#text-3-10 > p > a
Gpg4win div.pure-u-1 > div#text-3-10 > p > a
Read more div.pure-u-1 > div#text-3-10 > p > a
Read more div.pure-u-1 > div#text-3-11 > p > a
Gpg4win 5.0 div.pure-u-1 > div#text-3-12 > p > a
Read more div.pure-u-1 > div#text-3-12 > p > a
Gpg4win 5.0 div.pure-u-1 > div#text-3-13 > p > a
Read more div.pure-u-1 > div#text-3-13 > p > a
Read more div.pure-u-1 > div#text-3-14 > p > a
Read more div.pure-u-1 > div#text-3-15 > p > a
Read more div.pure-u-1 > div#text-3-16 > p > a
Read more div.pure-u-1 > div#text-3-17 > p > a
https://gnupg.org/ftp/ div.pure-u-1 > div#text-3-18 > p > a
Read more div.pure-u-1 > div#text-3-19 > p > a
more div.pure-u-1 > div#text-3-20 > p > a
more div.pure-u-1 > div#text-3-21 > p > a
important div.pure-u-1 > h3#sec-3-22 > span.tag > span.important
https://gnupg.org/blog/20240125-smartcard-backup-key.html div.pure-u-1 > div#text-3-22 > p > a
more div.pure-u-1 > div#text-3-23 > p > a
Privacy Policy div#nav_bottom > ul > li > a
Imprint div#nav_bottom > ul > li > a
Archive div#nav_bottom > ul > li > a
Sitemap div#nav_bottom > ul > li > a
Blog div#nav_bottom > ul > li > a
Files div#nav_bottom > ul > li > a
Creative Commons Attribution-ShareAlike 3.0 Unported License div#wrapper > div#footer > div#cpyright > a
copying div#wrapper > div#footer > div#cpyright > a
source div#wrapper > div#footer > div#cpyright > a

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
div#wrapper > div#header > a.logo > img div#wrapper > div#header > a.logo > img
div#footer > div.footerbox > a > img div#footer > div.footerbox > a > 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
body > div#wrapper > div#header > a.logo body > div#wrapper > div#header > a.logo

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cleartext Signatures Considered Harmful div#text-3 > ul > li > a
Blog div#nav_bottom > ul > li > a
Files div#nav_bottom > ul > li > a

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>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●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
○Deprecated ARIA roles were not used
○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
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<frame>` or `<iframe>` elements have a title
○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.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
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 The GNU Privacy Guar…18.57:13.0:1
#000000
#F0F0FC
Pass
h2 Reconquer your priva…18.57:13.0:1
#000000
#F0F0FC
Pass
h2 News18.57:13.0:1
#000000
#F0F0FC
Pass
h3 Security advisory T8…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 Libgcrypt 1.12 is th…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 Security advisory T8…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 Debian packages for …18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.16 release…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.14 release…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.13 and gpg…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.12 release…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 New GnuPG merchandis…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.9 with Deb…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.8 released…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.6 and Gpg4…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.5 and Gpg4…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.2 and Gpg4…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.4.7 and Gpg4…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.4.6 released…18.57:13.0:1
#000000
#F0F0FC
Pass
h3 GnuPG 2.5.1 released…18.57:13.0:1
#000000
#F0F0FC
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