Skip to content
https://www.proton.me

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
2
REVIEW
6
PASS
5
INFO
0
Checks
13
5 PASS 6 REVIEW 2 FIX
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::
2 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 2 <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
17 landmarks
REVIEW
17 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header NAV MAIN ASIDE "tab-title-_r85R_0_0" CONTENTINFO footer

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Proton ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Proton
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Proton ✓192×192 icon ✓512×512 icon ✓Start URL https://proton.me/ ✓Display Mode ✗
Name Proton Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light
Info::
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
Info::
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 light ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

A+
Heading Hierarchy
38 headings
PASS
38 headings
Info::
Single H1 present
  • H1 A better internet starts with privacy and freedom
  • H2 Communicate and browse. Privately.
  • H3 Proton Mail and Calendar
  • H3 Proton VPN
  • H4 No trackers. No distractions. Just your email.
  • H4 Stay protected online, wherever you go.
  • H4 Ultra-fast gaming, anywhere in the world.
  • H4 Organize your schedule privately.
  • H2 Store, share, collaborate. Securely.
  • H3 Proton Drive
  • H3 Proton Docs
  • H3 Proton Sheets
  • H2 Defend your digital life from hackers. Effortlessly.
  • H3 Proton Pass
  • H3 Proton Authenticator
  • H2 Host and join confidential meetings
  • H3 Proton Meet
  • H2 Powerful AI that respects your privacy.
  • H3 Lumo by Proton
  • H2 Protect your business with easy-to-use encrypted solutions.
  • H3 Proton for Business
  • H2 With Proton, your data belongs to you, not tech companies, governments, or hackers.
  • H3 Fundamentally different
  • H3 Privacy for a better world
  • H2 Over 100 million people and businesses have signed up for Proton
  • H3 End-to-end encryption
  • H3 Swiss privacy
  • H3 Security made easy
  • H3 Open source and audited
  • H3 One account, any device
  • H3 Free forever
  • H2 Our story begins at CERN, where the web was born
  • H2 Built by the community, for the community
  • H2 Choose an internet where your privacy comes first
  • H3 Products
  • H3 Privacy
  • H3 Company
  • H3 Connect
A+
Alt Text Quality
1 of 72 images have issues
PASS
1 of 72 images have issues
Warning::
1 image(s) with generic alt text
Info::
42 decorative image(s) correctly marked
Info::
29 image(s) with good alt text
72 images 29 good alt text 42 decorative 1 generic
IssueCount
generic1 image(s)
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
h1 A better internet st…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Communicate and brow…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Store, share, collab…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Defend your digital …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Host and join confid…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Powerful AI that res…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Protect your busines…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 With Proton, your da…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Over 100 million peo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our story begins at …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built by the communi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Choose an internet w…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proton Mail and Cale…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proton VPN21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proton Drive21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proton Docs21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proton Sheets21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proton Pass21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proton Authenticator21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Proton Meet21.00:13.0: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.

A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 26 passed
PASS
96

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.

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
Privacy Policy div.space-y-6 > ul.text-xs > li.sm:mr-2 > a.text-body
Terms & conditions div.space-y-6 > ul.text-xs > li.sm:mr-2 > a.text-body
Transparency report div.space-y-6 > ul.text-xs > li.sm:mr-2 > a.text-body

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>`
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●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
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●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 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.
○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.
○`<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.

Send Feedback